Skip to main content

Guidelines for Cryptographic Algorithm Agility

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Russ Housley
Last updated 2014-01-08 (Latest revision 2013-12-20)
Replaced by RFC 7696
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-iab-crypto-alg-agility
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:


Many IETF protocols may use of cryptographic algorithms to provide confidentiality, integrity, or non-repudiation. Communicating peers must support the same cryptographic algorithm or algorithms for these mechanisms to work properly. This memo provides guidelines for ensuring that such a protocol has the ability to migrate from one algorithm to another over time.


Russ Housley

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