Skip to content

Conversation

@afrind
Copy link
Collaborator

@afrind afrind commented Apr 2, 2025

This is an expansion/alternate to #898 that also addresses #903

Fixes: #804
Fixes: #903

Related to #350

@afrind afrind added the Design Issues or PRs that change how MoQ works including the wire format. label Apr 2, 2025
@afrind afrind requested a review from gloinul April 3, 2025 15:48
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,
Copy link
Contributor

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator

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

@afrind afrind merged commit 14cd4f0 into main Apr 19, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Design Issues or PRs that change how MoQ works including the wire format.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prevent Rapid Reset style attacks Correlation of control messages

9 participants