-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use even numbers for path ID #331
Conversation
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.
Thanks a lot for this new PR!
I totally support it, try to help fix a few typo issue.
Co-authored-by: Yanmei Liu <healing4d@gmail.com>
Co-authored-by: Yanmei Liu <healing4d@gmail.com>
Co-authored-by: Yanmei Liu <healing4d@gmail.com>
Co-authored-by: Yanmei Liu <healing4d@gmail.com>
Thanks for the fixes, @Yanmei-Liu |
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.
So I suppose then that receiving a MAX_PATHS with a Maximum Paths value of 0 leads to a connection error. A bit too bad, but I can live with that.
A small suggestion to make the example clearer, otherwise this looks good to me.
Co-authored-by: Quentin De Coninck <quentin.deconinck@uclouvain.be>
Do we generally have consensus for the even/odd split? Or do we need to confirm this on the list/in the interim before we merge? As I just wrote in PR #329 I don't think we fully have consensus yet if we want to specify the server-initiated paths part in this doc or separately. However, I think think we can already merge this PR and keep discussing in PR #329. |
Closing this PR after the 6/4/2024 interim. |
This PR specifies using even number path identifiers. It anticipates the possibility of using the odd numbered identifiers for server-initiated paths, but does not specify how to do that. As a result, it is much simpler than PR #329.
Close #328