|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3580 (2003)
|
|
Title:
|
IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines, 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 IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines, 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=3580
|
|
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:
|
|
|
Normative References/
/
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC/
1321, April 1992./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2284] Blunk, L. and J. Vollbrecht, "PPP Extensible/
Authentication Protocol (EAP)", RFC 2284, March 1998./
/
[RFC2865] Rigney, C., Willens, S., Rubens, A. and W. Simpson,/
"Remote Authentication Dial In User Service (RADIUS)",/
RFC 2865, June 2000./
/
[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./
/
[RFC3162] Aboba, B., Zorn, G. and D. Mitton, "RADIUS and IPv6",/
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./
/
[RFC3579] Aboba, B. and P. Calhoun, "RADIUS (Remote/
Authentication Dial In User Service) Support For/
Extensible Authentication Protocol (EAP)", RFC 3579,/
September 2003./
/
[IEEE8021X] IEEE Standards for Local and Metropolitan Area/
Networks: Port based Network Access Control, IEEE Std/
802.1X-2001, June 2001./
/
Informative References/
/
[RFC2104] Krawczyk, H., Bellare, M. and R. Canetti, "HMAC:/
Keyed-Hashing for Message Authentication", RFC 2104,/
February 1997./
/
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing/
an IANA Considerations Section in RFCs", BCP 26, RFC/
2434, October 1998./
/
[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./
/
[MD5Attack] Dobbertin, H., "The Status of MD5 After a Recent/
Attack." CryptoBytes Vol.2 No.2, Summer 1996./
/
[IEEE802] IEEE Standards for Local and Metropolitan Area/
Networks: Overview and Architecture, ANSI/IEEE Std/
802, 1990./
/
[IEEE8021Q] IEEE Standards for Local and Metropolitan Area/
Networks: Draft Standard for Virtual Bridged Local/
Area Networks, P802.1Q, January 1998./
/
[IEEE8023] ISO/IEC 8802-3 Information technology -/
Telecommunications and information exchange between/
systems - Local and metropolitan area networks -/
Common specifications - Part 3: Carrier Sense/
Multiple Access with Collision Detection (CSMA/CD)/
Access Method and Physical Layer Specifications, (also/
ANSI/IEEE Std 802.3- 1996), 1996./
/
[IEEE80211] Information technology - Telecommunications and/
information exchange between systems - Local and/
metropolitan area networks - Specific Requirements/
Part 11: Wireless LAN Medium Access Control (MAC) and/
Physical Layer (PHY) Specifications, IEEE Std./
802.11-1999, 1999./
/
[Berkeley] Borisov, N., Goldberg, I. and D. Wagner, "Intercepting/
Mobile Communications: The Insecurity of 802.11", ACM/
SIGMOBILE, Seventh Annual International Conference on/
Mobile Computing and Networking, July 2001, Rome,/
Italy./
/
[Arbaugh] Arbaugh, W., Shankar, N. and J.Y.C. Wan, "Your 802.11/
Wireless Network has No Clothes", Department of/
Computer Science, University of Maryland, College/
Park, March 2001./
/
[Fluhrer] Fluhrer, S., Mantin, I. and A. Shamir, "Weaknesses in/
the Key Scheduling Algorithm of RC4", Eighth Annual/
Workshop on Selected Areas in Cryptography, Toronto,/
Canada, August 2001./
/
[Stubbl] Stubblefield, A., Ioannidis, J. and A. Rubin, "Using/
the Fluhrer, Mantin and Shamir Attack to Break WEP",/
2002 NDSS Conference./
|
|
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
|
|
