Wade Simmons be77501f14 header: show the lane field in the version 1 header diagram ...

The lane byte was described in prose wedged between the first and second
rows of the table, which both broke up the diagram and left the wire layout
still claiming a single Reserved (uint16). Make it a field: widen the table
to fit Reserved (uint8) and Lane (uint8) with their types, and move the
explanation below the whole diagram.

The prose now covers what the picture can't: lane 0 is what a lanes-unaware
sender and every non-lane packet carry, so the field is compatible in both
directions; the remaining 8 bits stay reserved and zero; the H struct still
stores the pair as one Reserved field, so callers reach the low byte through
H.Lane and EncodeLane; and lane is part of the AEAD's associated data, so it
cannot be altered in flight.

2026-09-03 14:25:01 -04:00

..

header_test.go

multiport: make a lane a session on the tunnel, not a tunnel

2026-09-02 14:48:17 -04:00

header.go

header: show the lane field in the version 1 header diagram

2026-09-03 14:25:01 -04:00