Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms, November 2015
- File formats:
- BEST CURRENT PRACTICE
- R. Housley
- NON WORKING GROUP
Cite this BCP: TXT
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.