Crypto-Agility Requirements for Remote Authentication Dial-In User Service (RADIUS)
RFC 6421
Document | Type | RFC - Informational (November 2011; No errata) | |
---|---|---|---|
Author | David Nelson | ||
Last updated | 2015-10-14 | ||
Replaces | draft-nelson-radext-crypto-agility-requirements | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6421 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Dan Romascanu | ||
IESG note | Bernard Aboba (Bernard_Aboba@hotmail.com) is the document shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) D. Nelson, Ed. Request for Comments: 6421 Elbrys Networks, Inc. Category: Informational November 2011 ISSN: 2070-1721 Crypto-Agility Requirements for Remote Authentication Dial-In User Service (RADIUS) Abstract This memo describes the requirements for a crypto-agility solution for Remote Authentication Dial-In User Service (RADIUS). Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6421. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Nelson Informational [Page 1] RFC 6421 Crypto-Agility Requirements for RADIUS November 2011 This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction ....................................................2 1.1. General ....................................................2 1.2. Requirements Language ......................................3 1.3. Publication Process ........................................3 2. A Working Definition of Crypto-Agility ..........................4 3. The Current State of RADIUS Security ............................5 4. The Requirements ................................................5 4.1. Overall Solution Approach ..................................5 4.2. Security Services ..........................................6 4.3. Backwards Compatibility ....................................7 4.4. Interoperability and Change Control ........................9 4.5. Scope of Work ..............................................9 4.6. Applicability of Automated Key Management Requirements .....9 5. Security Considerations ........................................10 6. Acknowledgments ................................................10 7. References .....................................................10 7.1. Normative References ......................................10 7.2. Informative References ....................................11 1. Introduction 1.1. General At the IETF 66 meeting, the RADIUS Extensions (RADEXT) Working Group (WG) was asked by members of the Security Area Directorate to prepare a formal description of a crypto-agility work item and corresponding charter milestones. After consultation with one of the Security Area Directors (Russ Housley), text was initially proposed on the RADEXT WG mailing list on October 26, 2006. The following summarizes that proposal: Nelson Informational [Page 2] RFC 6421 Crypto-Agility Requirements for RADIUS November 2011 The RADEXT WG will review the security requirements for crypto- agility in IETF protocols, and identify the deficiencies of the existing RADIUS protocol specifications against these requirements. Specific attention will be paid to RFC 4962 [RFC4962].Show full document text