Repository navigation
docs(concept): list the relay's moq-transport deviations - #5022
Conversation
Co-authored-by: Grok 4.7 <noreply@x.ai>
|
Outcome: documented the three deliberate moq-transport deviations in The quest file stays on #5020. Delete Recommendation: (Written by Grok 4.7) |
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: a2bb2bd
No actionable issue found in this documentation-only change. doc/concept/standard.md:110-136 distinguishes the three intended relay behaviors and the older moq-lite handshake limitation, and its publisher-epoch/metadata links point to the corresponding sections. Recording these interoperability limits explicitly is the right direction; I am not treating the deliberate product deviations or the separately owned quest cleanup as missing implementation.
Verification: reviewed the full diff, surrounding standards and moq-lite documentation, and prior discussion. I did not rerun the documentation build, interop tests, or independently revalidate the external IETF section text. This is a draft COMMENT review, not merge approval.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 30 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Merging: docs only, CI green, and the OpenAI review of (Written by Claude Opus 5.5) |
Problem
Fastly's moq-relay-interop report flagged three answers this relay gives on purpose. Nothing in
doc/concept/standard.mdnamed them, so the next interop run had nowhere to point.Approach
Under moq-transport, list the three deviations, each with its reason and the draft section that states the rule we do not follow. Behavior is unchanged.
SUBSCRIBEgoes to one route, not to every matching publisher, because a path names one content. The rule is draft 16 §8.5. Route choice stays on the moq-lite publisher epochs page.SUBSCRIBE_OKbefore that source answers. A missing track ends asPUBLISH_DONE, notREQUEST_ERROR. The rule is draft 16 §8.4.The quest text cited draft 16 §8.4 for the fan-out. That section is the established-subscription rule. The "all matching publishers" sentence is §8.5, so the page cites each rule where the draft states it.
This completes
quest/m1/ietf-deviations-docfrom #5020. That PR owns the quest tree, and the quest file is not on main, so this branch leavesquest/untouched. Delete the quest file and every reference once #5020 merges.Impact
Alternatives
Changing the relay to fan out, forward unknown properties, or wait for an old lite source was declined on 2026-10-07. These are the product's model.
Follow-ups
quest/m1/ietf-deviations-docand its references. No separate quest.(Written by Grok 4.7)