From 9e1d5db348262fab522e0c794698031157aa67d7 Mon Sep 17 00:00:00 2001 From: martinduke Date: Fri, 27 Mar 2020 11:33:02 -0700 Subject: [PATCH] Update draft-ietf-quic-transport.md Co-Authored-By: ianswett --- draft-ietf-quic-transport.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 11bf62ee01..13ac604597 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1069,13 +1069,9 @@ to cease using the connection IDs when requested can result in connection failures, as the issuing endpoint might be unable to continue using the connection IDs with the active connection. -An endpoint MAY elect to only send or retransmit RETIRE_CONNECTION_ID frames -with sequence numbers greater than or equal to the highest Retire Prior To field -received minus its advertised active_connection_id_limit. This bounds the -necessary state at the endpoint. For example, if an endpoint receives a Retire -Prior To field of 7 and has an advertised active_connection_id_limit of 4, it -may cease sending any RETIRE_CONNECTION_ID frame with sequence number less than -3. +An endpoint MAY elect to limit the number of outstanding RETIRE_CONNECTION_ID frames +to bound the necessary state. In order to allow a peer to retire all previously issued +connection IDs, this limit SHOULD be at least the active_connection_id_limit. Peers SHOULD NOT issue updates of the Retire Prior To field before receiving RETIRE_CONNECTION_ID frames for the previous update of Retire Prior