From 2c0d5d9ef8682e0579bd1b801b3b181d5e68df36 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 14 Nov 2018 08:33:44 +1100 Subject: [PATCH] Discard, but don't retire, excess connection IDs --- draft-ietf-quic-transport.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index b88199aa8a..253e1a6d1b 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -938,9 +938,9 @@ the connection ID via a RETIRE_CONNECTION_ID frame ({{frame-retire-connection-id}}). Endpoints store received connection IDs for future use. An endpoint that -receives excessive connection IDs MAY discard those it cannot store. An -endpoint that issues connection IDs cannot expect its peer to store and use all -issued connection IDs. +receives excessive connection IDs MAY discard those it cannot store without +sending a RETIRE_CONNECTION_ID frame. An endpoint that issues connection IDs +cannot expect its peer to store and use all issued connection IDs. An endpoint SHOULD ensure that its peer has a sufficient number of available and unused connection IDs. While each endpoint independently chooses how many