Guidelines for Cryptographic Algorithm Agility
draft-iab-crypto-alg-agility-01
The information below is for an old version of the document.
| Document | Type | Expired Internet-Draft (iab) | |
|---|---|---|---|
| Author | Russ Housley | ||
| Last updated | 2014-12-29 (Latest revision 2014-06-27) | ||
| Replaces | draft-housley-crypto-alg-agility, draft-housley-crypto-alg-agility | ||
| Stream | Internet Architecture Board (IAB) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Reviews |
GENART Telechat review
(of
-07)
Ready with Issues
GENART Last Call review
(of
-06)
Ready with Issues
SECDIR Last Call review
(of
-06)
Has Issues
|
||
| Stream | IAB state | Active IAB Document | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-iab-crypto-alg-agility-01.txt
https://www.ietf.org/archive/id/draft-iab-crypto-alg-agility-01.txt
Abstract
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)