Add two more specific error codes for path abandon frame #466
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gloinul
reviewed
Nov 13, 2024
Conflicts: draft-ietf-quic-multipath.md
mirjak
reviewed
Nov 28, 2024
mirjak
reviewed
Nov 28, 2024
Co-authored-by: mirjak <mirja.kuehlewind@ericsson.com>
Co-authored-by: mirjak <mirja.kuehlewind@ericsson.com>
gloinul
reviewed
Nov 29, 2024
| the lack of a connection ID for this path. | ||
| This may occur when the peer initiates a new path | ||
| but has not provided a corresponding connection ID for the path ID | ||
| (or the packet containing the connection IDs has not arrived yet). |
There was a problem hiding this comment.
Should this error position itself in relation to the PATH_CID_BLOCKED in #468. Commonly a endpoint would first send PATH_CID_BLOCKED to indicate the lack of CID, and eventually it might decide to close the path using PATH_ABANDON with the NO_CID_AVAILABLE error code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To fix issue #414, according to the discussion during IETF 121.