Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 19
- Abstract
- Many IETF protocols use cryptographic algorithms to provide confidentiality, integrity, authentication, or digital signature. Communicating peers must support a common set of cryptographic algorithms for these mechanisms to work properly. This memo provides guidelines to ensure that protocols have the ability to migrate from one mandatory-to-implement algorithm suite to another over time.
- Publication Date
- 2015-11-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC7696- Link
- https://doi.org/10.17487/RFC7696
- Author(s)
- Russ Housley
Latest version of IETF RFC 7696
Document Versions — IETF RFC 7696
-
▶ IETF RFC 7696 (2015-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3766 [Active*]
Bibliographic Reference(s)
- 10.1007-3-540-44448-3_41 — BN EXTERNAL
- 10.1007-3-540-44647-8_19 — K EXTERNAL
- IEEE.STD802.11.1997 — WiFi EXTERNAL
- NIST.SP.800-30D — GCM EXTERNAL
- Wikipedia, "BEAST attack" under "Transport Layer Security", November 2015, < https://en.wikipedia.org/w/index.php?title= Transport_Layer_Security&oldid=689441642#BEAST_attack >. EXTERNAL
- Wikipedia, "Wired Equivalent Privacy", November 2015, < https://en.wikipedia.org/w/index.php? title=Wired_Equivalent_Privacy&oldid=688848497 >. EXTERNAL
- IETF RFC 1984 [Active*]
- IETF RFC 3365 [Active*]
- IETF RFC 3610 [Active*]
- IETF RFC 3748 [Active*]
- IETF RFC 4302 [Active*]
- IETF RFC 4303 [Active*]
- IETF RFC 4307 [Superseded*]
- IETF RFC 4422 [Active*]
- IETF RFC 5116 [Active*]
- IETF RFC 5246 [Superseded*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5652 [Active*]
- IETF RFC 5751 [Superseded*]
- IETF RFC 6347 [Superseded*]
- IETF RFC 6916 [Active*]
- IETF RFC 6975 [Active*]
- IETF RFC 7296 [Active*]
- IETF RFC 7366 [Active*]
- IETF RFC 7435 [Active*]
- IETF RFC 7525 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7696.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7696, Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms. Available at https://doi.org/10.17487/RFC7696
Snippet:
IETF RFC 7696, Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms. Available at https://doi.org/10.17487/RFC7696
HTML (ISO 690 compliant)
Preview:
IETF RFC 7696, Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms. Available at https://doi.org/10.17487/RFC7696
Snippet:
<span class="citation"><cite>IETF RFC 7696</cite>, Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms. Available at <a href="https://doi.org/10.17487/RFC7696" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7696</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7696, Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
doi: 10.17487/RFC7696
url: https://doi.org/10.17487/RFC7696
doi: 10.17487/RFC7696
url: https://doi.org/10.17487/RFC7696
Snippet:
<li> <cite id="bib-rfc7696">IETF RFC 7696</cite>, Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms <span class="doi">10.17487/RFC7696</span> </li>
Referenced By
- IETF RFC 9231 [Active*]