From 514c27376b79839373d12a3f99723810b905479b Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 7 Oct 2026 11:53:22 -0700 Subject: [PATCH 1/2] claim quest/m1/ietf-deviations-doc From a2bb2bd942a9d02997ab059914f762c02b3c5b13 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 7 Oct 2026 12:04:45 -0700 Subject: [PATCH 2/2] docs(concept): list the relay's moq-transport deviations Co-authored-by: Grok 4.7 --- doc/concept/standard.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/doc/concept/standard.md b/doc/concept/standard.md index 9b4730a7953..d911b7f4f85 100644 --- a/doc/concept/standard.md +++ b/doc/concept/standard.md @@ -107,6 +107,33 @@ before a `SUBSCRIBE_NAMESPACE` is caught up, and [moq-e2ee](/draft/moq-e2ee) is not a transport extension: it encrypts application payloads so relays still forward named tracks they cannot read. +### Deliberate deviations + +These three answers differ from the draft on purpose. They are the +product's model, not bugs, and the relay does not change them. + +- **One publisher per path.** A broadcast path names one piece of content, so a + `SUBSCRIBE` goes to one route, not to every publisher whose namespace matches. + [Draft 16 §8.5](https://www.ietf.org/archive/id/draft-ietf-moq-transport-16.html#section-8.5) + requires the relay to send that `SUBSCRIBE` to all matching publishers. See + [publisher epochs](/concept/moq-lite#publisher-epochs) for how that one route + is chosen. +- **Unknown object properties are dropped.** + [Draft 18 §2.5](https://www.ietf.org/archive/id/draft-ietf-moq-transport-18.html#section-2.5) + says a relay that does not understand a property still forwards and caches + it. The model keeps a payload and a timestamp, and + [leaves other per-object metadata out](/concept/moq-lite#what-moq-lite-leaves-out), + so a property it does not understand stops at the session that delivered it. +- **`SUBSCRIBE_OK` before an old source answers.** moq-lite 01 through 04 have + no track stream, so the relay cannot learn from that source whether the track + exists before answering. A moq-transport subscriber gets `SUBSCRIBE_OK` + before the source answers, and a missing track ends as `PUBLISH_DONE`, not + `REQUEST_ERROR`. + [Draft 16 §8.4](https://www.ietf.org/archive/id/draft-ietf-moq-transport-16.html#section-8.4) + requires an established upstream subscription before `SUBSCRIBE_OK`. From + moq-lite 05 the track stream answers first, and a missing track is refused + before `SUBSCRIBE_OK`. + ## MSF The MoQ Streaming Format is a catalog, playing the role HLS playlists and SDP