fix(blog): remove retired QUIC 0-RTT claim from why-now - #242
Merged
Merged
Conversation
The transport section claimed decdn uses QUIC 0-RTT on cdn/probe/v1 and cdn/dht/v1 and "collapses discovery to one-way RTT." That is not how decdn works: every connection completes a full TLS 1.3 handshake. The cold-start cost is bounded by concurrent probing (a ~500ms collection window with early exit) plus connection reuse and QUIC stream multiplexing, per ADR 001/005. Rewrite the bullet to describe the actual mechanism and state explicitly that decdn does not use 0-RTT. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying website with
|
| Latest commit: |
f857339
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d44756e3.website-70y.pages.dev |
| Branch Preview URL: | https://blog-remove-0rtt.website-70y.pages.dev |
There was a problem hiding this comment.
🟢 Approval recommended
The change is a targeted prose correction, with only a minor grammar nit noted in the updated bullet.
Pull request overview
Updates the “Why Now” blog post’s transport section to remove an incorrect claim about using QUIC 0-RTT, replacing it with an accurate explanation of decdn’s latency characteristics (concurrent probing, bounded collection window, and connection reuse/stream multiplexing).
Changes:
- Rewrites the QUIC bullet to describe concurrent probe fan-out and early-exit collection behavior.
- Explicitly states that decdn completes a full TLS 1.3 handshake and does not use 0-RTT.
File summaries
| File | Description |
|---|---|
| content/blog/01-why-now.mdx | Replaces the retired 0-RTT claim with prose describing concurrent probing + connection reuse over QUIC/TLS 1.3. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comma after the introductory "For a CDN," and "once enough reply" -> "once enough replies arrive" to fix the subject/number mismatch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
why-nowtransport section claims decdn uses QUIC 0-RTT ("sends application data in the first packet… collapses discovery to one-way RTT… we use 0-RTT oncdn/probe/v1andcdn/dht/v1"). That is not how decdn works.Per the canonical design: every connection completes a full TLS 1.3 handshake — decdn deliberately does not use 0-RTT. Cold-start latency is bounded instead by concurrent probing (a ~500 ms probe-collection window with early exit) plus connection reuse and QUIC stream multiplexing (ADR 001 §Probe response collection, ADR 005 §Connection Management). There is also no
ADR 015.This rewrites the bullet to describe the real mechanism and says explicitly that decdn does not use 0-RTT. Prose-only change to one published post.
The matching internal draft is corrected in decdn/internal#130.
Follow-up (not in this PR)
0-RTT /
ADR 015also still appears inwebsite/docs/overview/design-decisions.mdx(the design-decisions table) and in severaldecdn/internalfundraising materials (one-pagers, presskit,Product/client-cujs.md) already tracked as "needs ADR reconciliation." Happy to sweep those separately if you want.🤖 Generated with Claude Code