Skip to content

Commit

Permalink
[+] add more guidance on when to use PATH_ACK frames
Browse files Browse the repository at this point in the history
  • Loading branch information
Yanmei-Liu committed Oct 2, 2024
1 parent 031ddd7 commit 1b0322b
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion draft-ietf-quic-multipath.md
Original file line number Diff line number Diff line change
Expand Up @@ -319,7 +319,11 @@ Path ID 0.
After the handshake concluded if negotiation of multipath support succeeded,
endpoints SHOULD use PATH_ACK frames instead of ACK frames,
also for acknowledging so far unacknowledged 0-RTT packets, using
Path ID 0. Similarly after a successful handshake, endpoints SHOULD also use
Path ID 0. Further more, endpoints SHOULD use PATH_ACK frames in all 1-RTT packets after
the successful negotiation for multipath. If endpoints receive ACK frame
after a succesful negotiation resulting from packet out-of-order arrival,
endpoints could consider it as used for initial PATH ID 0 without causing connection error.
Similarly after a successful handshake, endpoints SHOULD also use
the PATH_NEW_CONNECTION_ID frame to provide new connection IDs for Path ID 0 and,
respectively, the PATH_RETIRE_CONNECTION_ID frame to retire connection IDs for
Path ID 0.
Expand Down

0 comments on commit 1b0322b

Please sign in to comment.