From f76e9e63539a6c59aaa08a5a3176e6ffea24c402 Mon Sep 17 00:00:00 2001 From: Gwendal Date: Sat, 7 Feb 2026 22:27:06 +0100 Subject: [PATCH 1/4] Clarify catalog group first object and joining fetch behavior --- draft-ietf-moq-msf.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/draft-ietf-moq-msf.md b/draft-ietf-moq-msf.md index 06a914d..c82d642 100644 --- a/draft-ietf-moq-msf.md +++ b/draft-ietf-moq-msf.md @@ -171,11 +171,22 @@ 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 a 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 (carried in the +first object of the latest group) and all subsequent catalog objects, including +delta updates, that follow. + ## Catalog Fields @@ -546,6 +557,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 (i.e., an aggregated full catalog), in order to bound the amount of delta processing required for joining subscribers. ## Catalog Examples From 2c72f95a1c22e7701c45d993af781bdd3dfbd681 Mon Sep 17 00:00:00 2001 From: Gwendal Simon Date: Fri, 13 Feb 2026 16:03:54 +0100 Subject: [PATCH 2/4] Update draft-ietf-moq-msf.md Co-authored-by: Will Law <2762250+wilaw@users.noreply.github.com> --- draft-ietf-moq-msf.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-moq-msf.md b/draft-ietf-moq-msf.md index c82d642..c546481 100644 --- a/draft-ietf-moq-msf.md +++ b/draft-ietf-moq-msf.md @@ -174,7 +174,7 @@ a delta update of a prior catalog object. The first catalog object published 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 a group MUST be +instance. Any catalog objects that precede the first object of the latest group MUST be ignored. A catalog object SHOULD be From 3299e3df8f09d0a25d837ba094c6b23c2ee09ee6 Mon Sep 17 00:00:00 2001 From: Gwendal Simon Date: Fri, 13 Feb 2026 16:04:05 +0100 Subject: [PATCH 3/4] Update draft-ietf-moq-msf.md Co-authored-by: Will Law <2762250+wilaw@users.noreply.github.com> --- draft-ietf-moq-msf.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-moq-msf.md b/draft-ietf-moq-msf.md index c546481..bcf14e6 100644 --- a/draft-ietf-moq-msf.md +++ b/draft-ietf-moq-msf.md @@ -557,7 +557,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 (i.e., an aggregated full catalog), in order to bound the amount of delta processing required for joining subscribers. +* 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 From 79a34c33ccd071ebbee96efc77ca551001245778 Mon Sep 17 00:00:00 2001 From: Gwendal Simon Date: Fri, 13 Feb 2026 16:04:25 +0100 Subject: [PATCH 4/4] Update draft-ietf-moq-msf.md Co-authored-by: Will Law <2762250+wilaw@users.noreply.github.com> --- draft-ietf-moq-msf.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/draft-ietf-moq-msf.md b/draft-ietf-moq-msf.md index bcf14e6..8482309 100644 --- a/draft-ietf-moq-msf.md +++ b/draft-ietf-moq-msf.md @@ -183,8 +183,7 @@ 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 (carried in the -first object of the latest group) and all subsequent catalog objects, including +(offset = 0) in order to obtain the latest complete catalog along with all subsequent catalog objects, including delta updates, that follow.