-
Notifications
You must be signed in to change notification settings - Fork 41
Change Subscription ID to Request ID, add to all requests #905
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
Conversation
This is more wire efficient and less ambiguous Fixes: #804
Co-authored-by: ianswett <[email protected]>
Co-authored-by: ianswett <[email protected]>
draft-ietf-moq-transport.md
Outdated
| requests, and supports the endpoint's ability to limit the concurrency and | ||
| frequency of requests. There are independent Request IDs for each endpoint. The | ||
| client's Request ID starts at 0 and are even and the server's Request ID starts | ||
| at 1 and are odd. The Request ID increments by 2 with ANNOUNCE, FETCH, |
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.
There is probably a reason for this client/server separation that is very smart, but I can't see what it is.
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.
It's not strictly necessary (subscribe ID does not do this) but it reduces confusion, so that Request ID=X is unambiguous.
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.
need a bit of clarification this count is scoped within a connection ... if a new connection was formed, counts would start over
This is an expansion/alternate to #898 that also addresses #903
Fixes: #804
Fixes: #903
Related to #350