Skip to main content

Post-Quantum Cryptography for Engineers

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Aritra Banerjee , Tirumaleswar Reddy.K , Dimitrios Schoinianakis , Tim Hollebeek
Last updated 2023-08-10
Replaced by draft-ietf-pquip-pqc-engineers
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-pquip-pqc-engineers
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The presence of a Cryptographically Relevant Quantum Computer (CRQC) would render state-of-the-art, public-key cryptography deployed today obsolete, since all the assumptions about the intractability of the mathematical problems that offer confident levels of security today no longer apply in the presence of a CRQC. This means there is a requirement to update protocols and infrastructure to use post- quantum algorithms, which are public-key algorithms designed to be secure against CRQCs as well as classical computers. These algorithms are just like previous public key algorithms, however the intractable mathematical problems have been carefully chosen, so they are hard for CRQCs as well as classical computers. This document explains why engineers need to be aware of and understand post- quantum cryptography. It emphasizes the potential impact of CRQCs on current cryptographic systems and the need to transition to post- quantum algorithms to ensure long-term security. The most important thing to understand is that this transition is not like previous transitions from DES to AES or from SHA-1 to SHA2, as the algorithm properties are significantly different from classical algorithms, and a drop-in replacement is not possible.


Aritra Banerjee
Tirumaleswar Reddy.K
Dimitrios Schoinianakis
Tim Hollebeek

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)