PATH_STANDBY PATH_AVAILABLE Sequence number spaces

[gloinul]

Section 8.3:
A variable-length integer specifying the sequence number assigned for this PATH_STANDBY frame. The sequence number space is shared with the PATH_AVAILABLE frame and the sequence number MUST be monotonically increasing generated by the sender of the PATH_STANDBY frame in the same connection. The receiver of the PATH_STANDBY frame needs to use and compare the sequence numbers separately for each Destination Connection ID Sequence Number.

So are sequnce number spaces per CID? But shared across the PATH_STANDBY and PATH_AVAILABLE

[mirjak]

No one number space but you only compare to the number that you previously received for the same CID.

E.g. you received

SEQ=1 CID=1
SEQ=2 CID=2
SEQ=4 CID=1
SEQ=3 CID=2

That means you have to update both paths and not throw away the frame with SEQ=3

[mirjak]

I think this issue is still true but you use now one sequence number space for all path IDs (instead of CIDs). I guess we could also define a separate sequence number path for each path ID now that the path IDs are stable, however, I don't think that makes a real difference.

However, I guess we should clarify this in the draft?