From 3d473f1f6050cf9f2ff88b4b4a773a7f857af467 Mon Sep 17 00:00:00 2001 From: mirjak Date: Tue, 3 Dec 2024 18:28:33 +0100 Subject: [PATCH] retransmit path_abandon on another path fixes #470 --- draft-ietf-quic-multipath.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/draft-ietf-quic-multipath.md b/draft-ietf-quic-multipath.md index 347caa0f..dafd4745 100644 --- a/draft-ietf-quic-multipath.md +++ b/draft-ietf-quic-multipath.md @@ -552,6 +552,9 @@ 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. +For example if the PATH_ABANDON frame itself got lost on the to be abandoned path, +this might be a sign that the path is not usable anymore and +retransmission on another path would address this concern. 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