Skip to content

using the same path ID, also for PATH_RESPONSE #573

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

using the same path ID, also for PATH_RESPONSE #573

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions draft-ietf-quic-multipath.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -325,11 +325,12 @@ or how multiple open paths are used for sending.

## Path Initiation and Validation {#path-initiation}


To open a new path, an endpoint MUST use a new connection ID associated
with an unused path ID.
When sending a PATH_RESPONSE frame, an endpoint MUST use a connection ID associated to
the same path ID as used in the packet that contained the PATH_CHALLENGE frame.
with an unused path ID. When sending packets on the same path, an endpoint
MUST use a connection ID associated to the same path ID as used in the packet
received by the server. If an endpoint receives a PATH_CHALLENGE, the
PATH_RESPONSE MUST be sent on the same path as the packet that contained
the PATH_CHALLENGE frame.
Comment on lines +331 to +333
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it the case that you need to send these packets? Should that follow the "MUST validate" clause in the next paragraph instead?


A client that wants to use an
additional path MUST validate the peer's address before sending any data packets
Expand Down
Loading