Does the connection id need to be in a consistent location? #293
Labels
-transport
design
An issue that affects the design of the protocol; resolution requires consensus.
has-consensus
An issue that the Chairs have determined has consensus, by canvassing the mailing list.
@martinthomson created a header proposal that provides a fixed 8 byte connection id in a fixed location.
We need to decide if this is a requirement or a nice to have.
I haven't found any environments it needed to be in a fixed location for all packets, as long as it's easy to determine where it will be from the first byte of the packet.
The text was updated successfully, but these errors were encountered: