datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

Crypto-Agility Requirements for Remote Authentication Dial-In User Service (RADIUS)
draft-ietf-radext-crypto-agility-requirements-07

RFC
Document Stream: IETF
Last updated: 2011-07-25
Replaces: draft-nelson-radext-crypto-agility-requirements
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html
IETF State: WG Document (radext)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown
IESG State: RFC 6421
IANA Action State: No IC 
Responsible AD: Dan Romascanu
IESG Note: Bernard Aboba (Bernard_Aboba@hotmail.com) is the document shepherd.
Send notices to: radext-chairs@tools.ietf.org, draft-ietf-radext-crypto-agility-requirements@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-radext-crypto-agility-requirements.

Abstract:
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.

Authors:
David Nelson <d.b.nelson@comcast.net>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)