Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

send PATH_ABANDON after time-out on another path #287

Merged
merged 2 commits into from
Nov 14, 2023
Merged

send PATH_ABANDON after time-out on another path #287

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
213b047
send PATH_ABANDON after time-out on another path
mirjak Nov 3, 2023
4002235
Update draft-ietf-quic-multipath.md
Yanmei-Liu Nov 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions draft-ietf-quic-multipath.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -441,6 +441,8 @@ any packet on this path anymore.
PATH_ABANDON frames can be sent on any path,
not only the path that is intended to be closed. Thus, a path can
be abandoned even if connectivity on that path is already broken.
Respectively, if there is still an active path, it is RECOMMENDED to
send an PATH_ABANDON frame after an idle time on another path.
Yanmei-Liu marked this conversation as resolved.
Show resolved Hide resolved

If a PATH_ABANDON frame is received for the only active path of a QUIC
connection, the receiving peer SHOULD send a CONNECTION_CLOSE frame
Expand Down