moq-lite-05: keep datagrams and Group Streams separate, no conversion

[kixelated]

Makes datagrams a fully independent delivery mode in §6.4, with no magic conversion between datagrams and Group Streams.

Changes

• Oversized datagrams are dropped, not converted. A publisher MUST NOT send a datagram body >1200 bytes, and a receiver MUST silently drop one that exceeds it. Removed the old "Payloads that would not fit MUST be sent as a Group Stream instead." A group whose frame doesn't fit is simply not eligible for datagram delivery and is delivered as a Group Stream like any other group — explicitly noted as not a conversion.
• No datagram→stream fallback on stream-only bindings. Bindings 3/4 (Qmux over TCP/TLS and WebSocket) still forbid emitting datagrams, but the "MUST fall back to Group Streams" wording is replaced: groups are delivered normally via Group Streams, with no conversion of a datagram into a stream.
• Changelog updated under moq-lite-05.

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

🤖 Generated with Claude Code

[sourcery-ai]

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

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 reviews.

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 92f63775-642f-4d2a-8211-74f2b904ab03

📥 Commits

Reviewing files that changed from the base of the PR and between f9ad1d4 and b0a2327.

📒 Files selected for processing (1)

• draft-lcurley-moq-lite.md

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/blissful-wright-488e20

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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