|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5433 (2009)
|
|
Title:
|
Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) Method
|
|
|
2.
|
Status of approval:
|
|
|
Fully released.
|
|
3.
|
Justification for the specific reference:
|
|
|
This specification has been developed by the IETF and is used by the ITU-T G.987.3 without change.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known issues.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
None
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Widely used by the industry.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[AES] National Institute of Standards and Technology,/
"Specification for the Advanced Encryption Standard/
(AES)", Federal Information Processing Standards/
(FIPS) 197, November 2001./
/
[CBC] National Institute of Standards and Technology,/
"Recommendation for Block Cipher Modes of Encryption --/
Methods and Techniques", Special Publication (SP) 800-38A,/
December 2001./
/
[CMAC] National Institute of Standards and Technology,/
"Recommendation for Block Cipher Modes of Operation: The/
CMAC Mode for Authentication", Special Publication/
(SP) 800-38B, May 2005./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H./
Levkowetz, "Extensible Authentication Protocol (EAP)",/
RFC 3748, June 2004./
/
[RFC4282] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, "The/
Network Access Identifier", RFC 4282, December 2005./
/
[RFC4634] Eastlake, D. and T. Hansen, "US Secure Hash Algorithms/
(SHA and HMAC-SHA)", RFC 4634, July 2006./
/
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an/
IANA Considerations Section in RFCs", BCP 26, RFC 5226,/
May 2008./
/
[RFC5247] Aboba, B., Simon, D., and P. Eronen, "Extensible/
Authentication Protocol (EAP) Key Management Framework",/
RFC 5247, August 2008.
|
|
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
|
|
