|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3579 (2003)
|
|
Title:
|
RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP), IETF RFC, September 2003.
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.cso refers to RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP), IETF RFC, September 2003.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3579
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC/
1321, April 1992./
/
[RFC2104] Krawczyk, H., Bellare, M. and R. Canetti, "HMAC:/
Keyed-Hashing for Message Authentication", RFC 2104,/
February 1997./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", RFC 2279, January 1998./
/
[RFC2284] Blunk, L. and J. Vollbrecht, "PPP Extensible/
Authentication Protocol (EAP)", RFC 2284, March 1998./
/
[RFC2401] Atkinson, R. and S. Kent, "Security Architecture for/
the Internet Protocol", RFC 2401, November 1998./
/
[RFC2406] Kent, S. and R. Atkinson, "IP Encapsulating Security/
Payload (ESP)", RFC 2406, November 1998./
/
[RFC2409] Harkins, D. and D. Carrel, "The Internet Key Exchange/
(IKE)", RFC 2409, November 1998./
/
[RFC2486] Aboba, B. and M. Beadles, "The Network Access/
Identifier", RFC 2486, January 1999./
/
[RFC2865] Rigney, C., Willens, S., Rubens, A. and W. Simpson,/
"Remote Authentication Dial In User Service (RADIUS)",/
RFC 2865, June 2000./
/
[RFC2988] Paxson, V. and M. Allman, "Computing TCP's/
Retransmission Timer", RFC 2988, November 2000./
/
[RFC3162] Aboba, B., Zorn, G. and D. Mitton, "RADIUS and IP6",/
RFC 3162, August 2001./
/
[RFC3280] Housley, R., Polk, W., Ford, W. and D. Solo, "Internet/
X.509 Public Key Infrastructure Certificate and/
Certificate Revocation List (CRL) Profile", RFC 3280,/
April 2002./
/
[RFC3576] Chiba, M., Dommety, G., Eklund, M., Mitton, D. and B./
Aboba, "Dynamic Authorization Extensions to Remote/
Authentication Dial In User Service (RADIUS)", RFC/
3576, July 2003./
Informative References/
/
[RFC826] Plummer, D., "An Ethernet Address Resolution/
Protocol", STD 37, RFC 826, November 1982./
/
[RFC1510] Kohl, J. and C. Neuman, "The Kerberos Network/
Authentication Service (V5)", RFC 1510, September/
1993./
/
[RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD/
51, RFC 1661, July 1994./
/
[RFC2548] Zorn, G., "Microsoft Vendor-specific RADIUS/
Attributes", RFC 2548, March 1999./
/
[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and/
Policy Implementation in Roaming", RFC 2607, June/
1999./
/
[RFC2716] Aboba, B. and D. Simon,"PPP EAP TLS Authentication/
Protocol", RFC 2716, October 1999./
/
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000./
/
[RFC2867] Zorn, G., Aboba, B. and D. Mitton, "RADIUS Accounting/
Modifications for Tunnel Protocol Support", RFC 2867,/
June 2000./
/
[RFC2868] Zorn, G., Leifer, D., Rubens, A., Shriver, J.,/
Holdrege, M. and I. Goyret, "RADIUS Attributes for/
Tunnel Protocol Support", RFC 2868, June 2000./
/
[RFC2869] Rigney, C., Willats, W. and P. Calhoun, "RADIUS/
Extensions", RFC 2869, June 2000./
/
[RFC2983] Black, D. "Differentiated Services and Tunnels", RFC/
2983, October 2000./
/
[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G. and J./
Roese, "IEEE 802.1X Remote Authentication Dial In User/
Service (RADIUS) Usage Guidelines", RFC 3580,/
September 2003./
/
[IEEE802] IEEE Standards for Local and Metropolitan Area/
Networks: Overview and Architecture, ANSI/IEEE Std/
802, 1990./
/
[IEEE8021X] IEEE Standards for Local and Metropolitan Area/
Networks: Port based Network Access Control, IEEE Std/
802.1X-2001, June 2001./
/
[MD5Attack] Dobbertin, H., "The Status of MD5 After a Recent/
Attack", CryptoBytes Vol.2 No.2, Summer 1996./
/
[Masters] Slatalla, M. and J. Quittner, "Masters of Deception."/
HarperCollins, New York, 1995./
/
[NASREQ] Calhoun, P., et al., "Diameter Network Access Server/
Application", Work in Progress./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
