Skip to content

Include enumerations in extensible protocol elements #1799

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.

Sign up for GitHub

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

Merged
ianswett merged 4 commits into from
Jul 6, 2026
Merged

Include enumerations in extensible protocol elements #1799

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
21be81f
Include enumerations in extensible protocol elements
afrind Jun 30, 2026
9c49724
Merge branch 'main' into extensible-enums
afrind Jul 6, 2026
5e106da
Apply suggestions from code review
afrind Jul 6, 2026
fa4b0f5
Merge branch 'main' into extensible-enums
ianswett Jul 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-moq-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -970,7 +970,7 @@ specific to the underlying transport protocol usage (see {{session}}).

Endpoints use the exchange of Setup messages to negotiate MOQT extensions.
Extensions can define new Message types, new Parameters, new Properties,
or new framing for Streams and Datagrams.
new Parameter values, or new framing for Streams and Datagrams.

The client and server MUST include all Setup Options {{setup-options}}
required for the negotiated MOQT version in SETUP.
Expand Down
Loading