[Sls-sea-dls] FW: [EXTERNAL] RFC 9958 on Post-Quantum Cryptography for Engineers
Howard.Weiss at parsons.us
Howard.Weiss at parsons.us
Fri Jun 19 09:50:58 EDT 2026
For your information. Since we are so invested in PQC in both the SecWG and SDLS WG - A nice overview of Post-Quantum Cryptography.
Regards
howie
-----Original Message-----
From: rfc-editor at rfc-editor.org <rfc-editor at rfc-editor.org>
Sent: Thursday, June 18, 2026 5:35 PM
To: ietf-announce at ietf.org; rfc-dist at rfc-editor.org
Cc: drafts-update-ref at iana.org; pqc at ietf.org; rfc-editor at rfc-editor.org
Subject: [EXTERNAL] RFC 9958 on Post-Quantum Cryptography for Engineers
A new Request for Comments is now available in online RFC libraries.
RFC 9958
Title: Post-Quantum Cryptography for Engineers
Author: A. Banerjee,
T. Reddy.K,
D. Schoinianakis,
T. Hollebeek,
M. Ounsworth
Status: Informational
Stream: IETF
Date: June 2026
Mailbox: aritra.banerjee at nokia.com,
k.tirumaleswar_reddy at nokia.com,
dimitrios.schoinianakis at nokia-bell-labs.com,
tim.hollebeek at digicert.com,
mike at ounsworth.ca
Pages: 42
I-D Tag: draft-ietf-pquip-pqc-engineers-14
URL: https://www.rfc-editor.org/info/rfc9958
DOI: 10.17487/RFC9958
The advent of a cryptographically relevant quantum computer (CRQC) would render state-of-the-art, traditional public key algorithms deployed today obsolete, as the mathematical assumptions underpinning their security would no longer hold. To address this, protocols and infrastructure must transition to post-quantum algorithms, which are designed to resist both traditional and quantum attacks. This document explains why engineers need to be aware of and understand post-quantum cryptography (PQC), and it details the impact of CRQCs on existing systems and the challenges involved in transitioning to post-quantum algorithms. Unlike previous cryptographic updates, this shift may require significant protocol redesign due to the unique properties of post-quantum algorithms.
This document is a product of the Post-Quantum Use In Protocols Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/
Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor at rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.
The RFC Editor Team
_______________________________________________
IETF-Announce mailing list -- ietf-announce at ietf.org To unsubscribe send an email to ietf-announce-leave at ietf.org
"NOTICE: This email message and all attachments transmitted with it may contain confidential information, including information that is privileged or protected by, and proprietary to, Parsons Corporation, and is intended solely for the use of the addressee for the specific purpose set forth in this communication. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited, and you should delete this message and all copies and backups thereof. The recipient may not further distribute or use any of the information contained herein without the express written authorization of the sender. If you have received this message in error, or if you have any questions regarding the use of the proprietary information contained therein, please contact the sender of this message immediately, and the sender will provide you with further instructions."
More information about the SLS-SEA-DLS
mailing list