quicwg / multipath

In-progress version of draft-ietf-quic-multipath
Other
48 stars 17 forks source link

Remove things on NEW/RETIRE_CID that have been normatively specified … #361

Closed mirjak closed 1 month ago

mirjak commented 1 month ago

…in RFC9000

mirjak commented 1 month ago

@huitema "retire prio to" is specified in RFC9000:

The Retire Prior To field applies to connection IDs established during connection setup and the preferred_address transport parameter; see Section 5.1.2. The value in the Retire Prior To field MUST be less than or equal to the value in the Sequence Number field. Receiving a value in the Retire Prior To field that is greater than that in the Sequence Number field MUST be treated as a connection error of type FRAME_ENCODING_ERROR.

Once a sender indicates a Retire Prior To value, smaller values sent in subsequent NEW_CONNECTION_ID frames have no effect. A receiver MUST ignore any Retire Prior To fields that do not increase the largest received Retire Prior To value.

An endpoint that receives a NEW_CONNECTION_ID frame with a sequence number smaller than the Retire Prior To field of a previously received NEW_CONNECTION_ID frame MUST send a corresponding RETIRE_CONNECTION_ID frame that retires the newly received connection ID, unless it has already done so for that sequence number.

The only thing that changes is that the MP_ frames are used und that the sequence numbers are per path. This is explained in the text. What else do you think needs to be specified?

mirjak commented 1 month ago

@huitema I merged this PR. Please open an issue if you think there is something more that needs to be specified about the "retire prior to" field!

huitema commented 1 month ago

See issue #368.