Consider the Flow Info to indicate direct peering

[vanrein]

According to Section 6 of RFC 2460 and more specifically Appendix A, the experimental facilitation of a Flow Label is meant to keep flows on the same path. For 6bed4, such a choice is possible.

When set to 0, the Flow Label is considered absent and no flow consistency is expected. To manage the flow as a consistent stream, the Flow Label is to be pseudo-random but non-zero. This may be used by a 6bed4peer to choose direct delivery for the data involved. Standards are not up to par with this, so it would be a "software extension" on top of the official specification.

The socket API shares the Flow Label in the sin6_flowinfo field of struct sockaddr_in6 so it can be set when binding or connecting a socket, and when inspecting the local or remote socket address.

Since the transmitted field is 20 bits, and programmers be what they are, there may be no stopping to "initial" code setup with the hexadecimale value 6bed4 in this field :-)

[vanrein]

The purpose of the Flow Label is actually to keep media streams together (in order, and with constant delay times, both in a best-effort form) and that is precisely what 6bed4 is supposed to be good at. It was designed to provide smooth media flows directly between peers.