Skip to content

moq-lite-05: restore Publisher Max Latency, min-of-two expiration, drop compression#45

Merged
kixelated merged 1 commit into
mainfrom
claude/inspiring-herschel-08c804
Jun 30, 2026
Merged

moq-lite-05: restore Publisher Max Latency, min-of-two expiration, drop compression#45
kixelated merged 1 commit into
mainfrom
claude/inspiring-herschel-08c804

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Summary

Three changes to draft-lcurley-moq-lite.md, all under the in-progress moq-lite-05 changelog:

Restore Publisher Max Latency

Added back to TRACK_INFO (immutable per-track property) with maximum cache-retention semantics — an upper bound on how long the publisher caches a non-latest group, the inverse of an HTTP Cache-Control: max-age guarantee. Subscribers MUST NOT assume an older group is still available even within the bound. Since Max Latency is two-sided again, the Subscriber prefix is restored on the subscriber field (SUBSCRIBE / SUBSCRIBE_UPDATE).

Note: the previous Publisher Cache field (before removal in #34) was a minimum guarantee — this is deliberately the opposite, matching the name and mirroring Subscriber Max Latency as an upper bound on staleness.

Minimum-of-two expiration

A group's age is now measured two ways and it expires once either exceeds Max Latency (its effective lifetime is the minimum of the two):

  • Timestamp age — media-time delta (relay-stable, jitter-immune).
  • Wall-clock age — arrival/queue-time delta.

The two backstop each other: a publisher can't keep stale groups alive with fresh-looking timestamps (wall-clock evicts anyway), and a delivery burst (e.g. catching up at subscription start) doesn't reset age (timestamp age evicts the media-old ones). Empty groups still fall back to wall-clock only.

Drop compression

Reverted the ANNOUNCE_BROADCAST DEFLATE compression added in #44 — it now lives in the standalone draft-lcurley-moq-namespace-compression.md extension. Removed the Compressed Payload wrapper, the compression section, the Announce-Stream compression-context prose, and the now-unused RFC1951 / RFC7692 references. No compress/deflate text remains in the draft.

Validation

make draft-lcurley-moq-lite.txt passes (kramdown-rfc + xml2rfc OK).

🤖 Generated with Claude Code

…op compression

- Add `Publisher Max Latency` to TRACK_INFO as a maximum cache-retention
  bound (the inverse of an HTTP Cache-Control: max-age guarantee), and
  restore the `Subscriber` prefix now that Max Latency is two-sided again.
- Expire a group once *either* its timestamp age or its wall-clock arrival
  age exceeds Max Latency (shorter lifetime wins), so manipulated timestamps
  and delivery bursts are both bounded.
- Revert the ANNOUNCE_BROADCAST DEFLATE compression added in #44 (it lives
  in the namespace-compression extension draft); drop the now-unused RFC1951
  and RFC7692 references.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @kixelated, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a2925473-b080-4b2b-8d0c-26f6f2e80143

📥 Commits

Reviewing files that changed from the base of the PR and between 23b75c4 and 2fe3f03.

📒 Files selected for processing (1)
  • draft-lcurley-moq-lite.md

Walkthrough

The draft splits the single Max Latency track preference into two distinct fields: Subscriber Max Latency (delivery-time staleness bound for non-latest groups, carried in SUBSCRIBE and SUBSCRIBE_UPDATE) and Publisher Max Latency (cache retention bound, carried in TRACK_INFO). The Expiration section is rewritten so that expiration triggers when either timestamp-based age or wall-clock-based age exceeds the applicable bound, with added handling for zero-frame groups. The Frame timestamp description is updated to name both inputs to expiration. The ANNOUNCE_BROADCAST encoding is reorganized and the entire Compressed ANNOUNCE_BROADCAST Payloads subsection (DEFLATE context, sync-flush, and decompression failure rules) is removed, along with the RFC1951 and RFC7692 normative references. The changelog for moq-lite-05 is updated accordingly.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the three main changes: latency fields, expiration semantics, and compression removal.
Description check ✅ Passed The description is directly aligned with the changeset and explains the same three draft updates in sufficient detail.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch claude/inspiring-herschel-08c804

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@kixelated kixelated merged commit cdb701c into main Jun 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant