|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4017 (2005)
|
|
Title:
|
Extensible Authentication Protocol (EAP) Method Requirements for Wireless LANs
|
|
|
2.
|
Status of approval:
|
|
|
The referred IETF RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.akm refers to and makes use of the terms definition and several relevant requirements, IETF RFC 4017, 2005.
|
|
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=4017
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the IETF referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the IETF referred RFCs, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced documents are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,/
"Remote Authentication Dial In User Service (RADIUS)",/
RFC 2865, June 2000./
/
[RFC3579] Aboba, B. and P. Calhoun, "RADIUS (Remote/
Authentication Dial In User Service) Support For/
Extensible Authentication Protocol (EAP)", RFC 3579,/
September 2003./
/
[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and/
H. Levkowetz, "Extensible Authentication Protocol/
(EAP)", RFC 3748, June 2004./
/
[IEEE 802.11] 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-/
2003, 2003./
/
[IEEE 802.1X] IEEE Standards for Local and Metropolitan Area/
Networks: Port based Network Access Control, IEEE Std/
802.1X-2004, December 2004./
/
[IEEE 802.11i] Institute of Electrical and Electronics Engineers,/
"Supplement to Standard for Telecommunications and/
Information Exchange Between Systems - LAN/MAN Specific/
Requirements - Part 11: Wireless LAN Medium Access/
Control (MAC) and Physical Layer (PHY) Specifications:/
Specification for Enhanced Security", IEEE 802.11i,/
July 2004./
|
|
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):
|
|
|
The referred IETF RFC is available on the web.
[1] IETF RFC 4017 (2005), Extensible Authentication Protocol (EAP) Method Requirements for Wireless LANs: available at "http://www.ietf.org/rfc/rfc3280.txt?number=4017"
|
