RFC 8696: Using Pre-Shared Key (PSK) in the Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
The invention of a large-scale quantum computer would pose a serious challenge for the cryptographic algorithms that are widely deployed today. The Cryptographic Message Syntax (CMS) supports key transport and key agreement algorithms that could be broken by the invention of such a quantum computer. By storing communications that are protected with the CMS today, someone could decrypt them in the future when a large-scale quantum computer becomes available. Once quantum-secure key management algorithms are available, the CMS will be extended to support the new algorithms if the existing syntax does not accommodate them. This document describes a mechanism to protect today's communication from the future invention of a large-scale quantum computer by mixing the output of key transport and key agreement algorithms with a pre-shared key.
Document record
- Document ID
- RFC8696
- Published
- December 2019
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8693OAuth 2.0 Token ExchangeCurrent
January 2020
- RFC 8692Internet X.509 Public Key Infrastructure: Additional Algorithm Identifiers for RSASSA-PSS and ECDSA Using SHAKEsCurrent
December 2019
- RFC 8701Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS ExtensibilityCurrent
January 2020
- RFC 8702Use of the SHAKE One-Way Hash Functions in the Cryptographic Message Syntax (CMS)Current
January 2020
- RFC 8689SMTP Require TLS OptionCurrent
November 2019
- RFC 8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensCurrent
February 2020
- RFC 8707Resource Indicators for OAuth 2.0Current
February 2020
- RFC 8708Use of the HSS/LMS Hash-Based Signature Algorithm in the Cryptographic Message Syntax (CMS)Obsoleted
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?