Skip to content

Clarify catalog group first object and joining fetch behavior #113

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

Open
gwendalsimon wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Clarify catalog group first object and joining fetch behavior #113

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f76e9e6
Clarify catalog group first object and joining fetch behavior
Feb 7, 2026
2c72f95
Update draft-ietf-moq-msf.md
gwendalsimon Feb 13, 2026
3299e3d
Update draft-ietf-moq-msf.md
gwendalsimon Feb 13, 2026
79a34c3
Update draft-ietf-moq-msf.md
gwendalsimon Feb 13, 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
13 changes: 12 additions & 1 deletion draft-ietf-moq-msf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,11 +171,21 @@ The catalog track MUST have a case-sensitive Track Name of "catalog".

A catalog object MAY be independent of other catalog objects or it MAY represent
a delta update of a prior catalog object. The first catalog object published
within a new group MUST be independent. A catalog object SHOULD be
within a new group MUST be independent and MUST provide a complete catalog that
does not require any prior catalog object for interpretation. This object MAY
aggregate the effects of prior delta updates and MAY start a new catalog
instance. Any catalog objects that precede the first object of the latest group MUST be
ignored.

A catalog object SHOULD be
published only when the availability of tracks changes.

Each catalog update MUST be mapped to an MOQT Object.

Subscribers accessing the catalog MUST use SUBSCRIBE with a Joining FETCH
(offset = 0) in order to obtain the latest complete catalog along with all subsequent catalog objects, including
delta updates, that follow.


## Catalog Fields

Expand Down Expand Up @@ -546,6 +556,7 @@ The following rules are to be followed in constructing and processing delta upda
which MUST NOT be modified after being declared. To modify any attribute, a new
track with a different Namespace|Name tuple is created by Adding or Cloning and then
the old track is removed.
* Producers that publish frequent delta updates SHOULD periodically publish a new independent catalog in a new MOQT Group in order to bound the amount of delta processing required for joining subscribers.


## Catalog Examples
Expand Down