change(https-tls): RFC 10024 standardises hybrid post-quantum key agreement - #176
Draft
jdevalk wants to merge 1 commit into
Draft
change(https-tls): RFC 10024 standardises hybrid post-quantum key agreement#176jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
…eement RFC 10024 (August 2026, Proposed Standard) puts X25519MLKEM768, SecP256r1MLKEM768 and SecP384r1MLKEM1024 on the standards track for TLS 1.3, obsoleting the draft Kyber768 code points. The RFC marks X25519MLKEM768 Recommended and describes it as widely deployed. The page previously said post-quantum key exchange "is being specified" for TLS 1.3 — that is no longer true. It now asks for hybrid PQ key agreement in the cipher checklist and separates the confidentiality migration (server config, defends against capture-now-decrypt-later) from the authentication migration (post-quantum certificates, on CA and root-programme timelines). Dropped the MDN TLS overview from sources: it was not cited inline and the list was already over the 2-4 guidance in CLAUDE.md. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
9b8e652
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://35345ce1.specification-website.pages.dev |
| Branch Preview URL: | https://change-pq-hybrid-tls-2026-08.specification-website.pages.dev |
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
1 participant
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.
What changed
HTTPS and TLS now covers hybrid post-quantum key agreement:
X25519MLKEM768on TLS 1.3.Common mistakesline and aVerificationline.CLAUDE.md.2026-08-12-pq-hybrid-tls.md(changed).Why now
RFC 10024 was published 10 August 2026 (Proposed Standard). It defines
X25519MLKEM768,SecP256r1MLKEM768andSecP384r1MLKEM1024, and obsoletes the pre-standardX25519Kyber768Draft00/SecP256r1Kyber768Draft00code points. The page's existing wording predates it and is now wrong.Adoption
Not thin. The RFC itself says
X25519MLKEM768is "widely deployed" and "often serves as the most practical choice" — browsers and large CDNs shipped it ahead of publication. This is a change to an existingrequiredpage, not a new page, so the adoption bar is comfortably met.Primary sources
Status
Unchanged —
required. RFC 10024 does not change whether HTTPS is required; it changes what a current TLS 1.3 configuration should offer. The hybrid group is stated as a checklist item, not as a separaterequiredtopic.Checks
npm run buildpasses.npm run lintandnpm run format:checkpass. No page count or category change, soSKILL.mdand the digest are untouched (pre-commit hook confirms).🤖 Generated with Claude Code