Explicit linkages for ODCID/OCID TP #3149
Conversation
MikeBishop
added
editorial
|
Note that #3120 may want to change the phrasing of the ODCID field, depending on which PR lands first. |
| a Retry packet. | ||
| sent by the client. This transport parameter is only sent by a server. This | ||
| is the same value sent in the "Original Destination Connection ID" field of a | ||
| Retry packet (see {{packet-retry}}). A server MUST include the |
There was a problem hiding this comment.
Note that David's proposal for integrity protection of the Retry packet changes this text to point to the original Initial sent by the client. You should probably do the same.
There was a problem hiding this comment.
Can you point to the specific text you're looking at?
David's text in #3120:
value of the Destination Connection ID from the Initial packet that this Retry is in response to.
Text here:
value of the Destination Connection ID field from the first Initial packet sent by the client
These seem to indicate the same Initial packet.
There was a problem hiding this comment.
I might have misremembered, sorry. In #3120, the text I was concerned about was
If the server sends a Retry packet, it MUST include the Destination Connection ID field from the client's first Initial packet in the transport parameter.
But you didn't touch that.
| a Retry packet. | ||
| sent by the client. This transport parameter is only sent by a server. This | ||
| is the same value sent in the "Original Destination Connection ID" field of a | ||
| Retry packet (see {{packet-retry}}). A server MUST include the |
There was a problem hiding this comment.
I might have misremembered, sorry. In #3120, the text I was concerned about was
If the server sends a Retry packet, it MUST include the Destination Connection ID field from the client's first Initial packet in the transport parameter.
But you didn't touch that.
Fixes #2926.