| rfc9852v2.txt | rfc9852.txt | |||
|---|---|---|---|---|
| skipping to change at line 100 ¶ | skipping to change at line 100 ¶ | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
| "OPTIONAL" in this document are to be interpreted as described in BCP | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
| 14 [RFC2119] [RFC8174] when, and only when, they appear in all | 14 [RFC2119] [RFC8174] when, and only when, they appear in all | |||
| capitals, as shown here. | capitals, as shown here. | |||
| 3. Implications for Post-Quantum Cryptography (PQC) | 3. Implications for Post-Quantum Cryptography (PQC) | |||
| Cryptographically Relevant Quantum Computers (CRQCs), once available, | Cryptographically Relevant Quantum Computers (CRQCs), once available, | |||
| will have a huge impact on TLS traffic (see, e.g., Section 2 of | will have a huge impact on TLS traffic (see, e.g., Section 3 of | |||
| [PQC-FOR-ENGINEERS]). To mitigate this, TLS applications will need | [PQC-FOR-ENGINEERS]). To mitigate this, TLS applications will need | |||
| to migrate to Post-Quantum Cryptography (PQC) [PQC]. Detailed | to migrate to Post-Quantum Cryptography (PQC) [PQC]. Detailed | |||
| considerations of when an application requires PQC or when a CRQC is | considerations of when an application requires PQC or when a CRQC is | |||
| a threat that an application needs to protect against are beyond the | a threat that an application needs to protect against are beyond the | |||
| scope of this document. | scope of this document. | |||
| It is important to note that the TLS Working Group is focusing its | It is important to note that the TLS Working Group is focusing its | |||
| efforts on TLS 1.3 or later; TLS 1.2 will not be supported (see | efforts on TLS 1.3 or later; TLS 1.2 will not be supported (see | |||
| [TLS12FROZEN]). This is one more reason for new protocols to require | [TLS12FROZEN]). This is one more reason for new protocols to require | |||
| TLS to default to TLS 1.3, where PQC is actively being standardized, | TLS to default to TLS 1.3, where PQC is actively being standardized, | |||
| End of changes. 1 change blocks. | ||||
| 1 lines changed or deleted | 1 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||