RFC 6421: Crypto-Agility Requirements for Remote Authentication Dial-In User Service (RADIUS)
In plain English — editorial summary, not part of the RFC
This memo describes the requirements for a crypto-agility solution for Remote Authentication Dial-In User Service (RADIUS). This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6421
- Published
- November 2011
- Authors
- D. Nelson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 12
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6407The Group Domain of InterpretationObsoleted
October 2011
- RFC 6402Certificate Management over CMS (CMC) UpdatesObsoleted
November 2011
- RFC 6440The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 OptionCurrent
December 2011
- RFC 6394Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE)Current
October 2011
- RFC 6448The Unencrypted Form of Kerberos 5 KRB-CRED MessageCurrent
November 2011
- RFC 6347Datagram Transport Layer Security Version 1.2Obsoleted
January 2012
- RFC 6331Moving DIGEST-MD5 to HistoricCurrent
July 2011
- RFC 6520Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Heartbeat ExtensionUpdated
February 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?