From 8ddac829279ee949ad338f6ab3b46f9fd99b4e6c Mon Sep 17 00:00:00 2001 From: mirjak Date: Fri, 20 Dec 2024 14:34:50 +0100 Subject: [PATCH] always recommend to send path_abandon on another path I created this PR based on the discussion in (the now-closed) PR #473. This is a slight change of the normative recommendation as it generally recommends to send the PATH_ABANDON on another path. I understood that this is what we want to recommend but if not, we cannot also not apply this PR. Please comment! --- draft-ietf-quic-multipath.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/draft-ietf-quic-multipath.md b/draft-ietf-quic-multipath.md index 0b3ada1a..25e65ea8 100644 --- a/draft-ietf-quic-multipath.md +++ b/draft-ietf-quic-multipath.md @@ -551,10 +551,10 @@ After a path is abandoned, the Path ID MUST NOT be reused for new paths, as the Path ID is part of the nonce calculation {{multipath-aead}}. PATH_ABANDON frames can be sent on any path, -not only the path that is intended to be closed. Thus, -even if connectivity on that path is already broken -but there is still another usable path, it is RECOMMENDED to -send the PATH_ABANDON frames on another path. +not only the path that is intended to be closed. +It is RECOMMENDED to send the PATH_ABANDON frames on another path, +especially if connectivity on the to-be-abandoned path +is expected to be broken. If a PATH_ABANDON frame is received for the only open path of a QUIC connection, the receiving peer SHOULD send a CONNECTION_CLOSE frame