-
Notifications
You must be signed in to change notification settings - Fork 20
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.
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
Add clarification for PATHS_BLOCKED frame. #463
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Quentin De Coninck <[email protected]>
…o dev/fix-461 Conflicts: draft-ietf-quic-multipath.md
Is it PATHS_BLOCKED or PATH_BLOCKED? The text in the PR doesn't match the text immediately preceding it. |
draft-ietf-quic-multipath.md
Outdated
@@ -1346,7 +1346,11 @@ MAX_PATH_ID frames that do not increase the path limit MUST be ignored. | |||
|
|||
A sender SHOULD send a PATHS_BLOCKED frame (type=0x15228c0d) when | |||
it wishes to open a path but is unable to do so due to the maximum path identifier | |||
limit set by its peer; | |||
limit set by its peer. | |||
Note that PATH_BLOCKED frame is informational. Sending a PATH_BLOCKED frame does not |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These should both say PATHS_BLOCKED rather than PATH_BLOCKED
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch! Updated.
Fix issue #461.
Generally the PATH_BLOCKED frame is informational and doesn't change the state of the peer.