Skip to content

moq-lite-05: define broadcast Epoch as a timestamp#36

Merged
kixelated merged 1 commit into
mainfrom
claude/revert-epoch-change-xr2cvt
Jun 21, 2026
Merged

moq-lite-05: define broadcast Epoch as a timestamp#36
kixelated merged 1 commit into
mainfrom
claude/revert-epoch-change-xr2cvt

Conversation

@kixelated

@kixelated kixelated commented Jun 21, 2026

Copy link
Copy Markdown
Collaborator

Redefines the broadcast Epoch field (added in #35) from an opaque, application-defined value to a concrete timestamp.

Change

The Epoch in ANNOUNCE_BROADCAST is now defined as the time the origin publisher created the broadcast instance, expressed in seconds since 2020-01-01T00:00:00Z.

  • A 2020 reference point (rather than the Unix epoch) keeps current timestamps within a 4-byte varint instead of needing 8.
  • Larger still means newer, so the conflict-resolution and tiebreaker semantics are unchanged.
  • 0 still means the publisher does not assign an Epoch.

Updated the Broadcast-section overview, the Epoch field description, and the moq-lite-05 changelog bullet accordingly. The draft validates via kramdown-rfc.

🤖 Generated with Claude Code

Define the ANNOUNCE_BROADCAST Epoch as the time the origin publisher
created the broadcast instance, in seconds since 2020-01-01T00:00:00Z.
The 2020 reference point (rather than the Unix epoch) keeps current
timestamps within a 4-byte varint. Replaces the previous opaque,
application-defined value.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011meTAeUxiib7Ns2vd6Vzg5
@kixelated kixelated force-pushed the claude/revert-epoch-change-xr2cvt branch from a4de94a to ecb58fe Compare June 21, 2026 01:27
@kixelated kixelated changed the title moq-lite-05: revert broadcast Epoch addition moq-lite-05: define broadcast Epoch as a timestamp Jun 21, 2026
@coderabbitai

coderabbitai Bot commented Jun 21, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@kixelated, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 57 minutes and 43 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9cde47d9-0ae4-4e01-9892-b2cdf4cc4b15

📥 Commits

Reviewing files that changed from the base of the PR and between a4de94a and ecb58fe.

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

Walkthrough

The pull request removes the Epoch concept entirely from the MoQ-lite draft specification. This affects four areas: the Broadcast concept section (prose describing Epoch as a broadcast ordering mechanism), the subscriber conflict-resolution guidance (using Epoch to prefer newer advertisements across multiple paths), the ANNOUNCE_BROADCAST wire format (removing the Epoch (i) field, its semantic description, relay forwarding rules, and the section anchor), and the path tiebreaker text (now citing total path length as the sole tiebreaker). The moq-lite-05 changelog entry recording the original Epoch addition is also deleted.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: reverting the broadcast Epoch addition from version 05 of the MOQ Lite specification.
Description check ✅ Passed The description is directly related to the changeset, providing detailed information about what was removed (Epoch-related content) and what was preserved (ANNOUNCE message renames).
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch claude/revert-epoch-change-xr2cvt

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 and usage tips.

@kixelated kixelated merged commit 0ef3524 into main Jun 21, 2026
2 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.

2 participants