Skip to content

Commit

Permalink
always recommend to send path_abandon on another path
Browse files Browse the repository at this point in the history
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!
  • Loading branch information
mirjak authored Dec 20, 2024
1 parent b02e889 commit 8ddac82
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions draft-ietf-quic-multipath.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 8ddac82

Please sign in to comment.