|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
RFC - Experimental (ISE Stream)
|
|
3.
|
Justification for the specific reference:
|
|
|
EAP-PSK-ECCSI defined in Annex D of x.ibc-iot uses EAP-PSK protocol specified in IETF RFC 4764
|
|
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=4764
|
|
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:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[2] Aboba, B., Beadles, M., Arkko, J., and P. Eronen, "The Network/
Access Identifier", RFC 4282, December 2005./
/
[3] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H./
Levkowetz, "Extensible Authentication Protocol (EAP)",/
RFC 3748, June 2004./
/
Bersani & Tschofenig Experimental [Page 57]/
RFC 4764 EAP-PSK January 2007/
/
[4] Bellare, M., Rogaway, P., and D. Wagner, "The EAX mode of/
operation", FSE 04, Springer-Verlag LNCS 3017, 2004./
/
[5] Gilbert, H., "The Security of One-Block-to-Many Modes of/
Operation", FSE 03, Springer-Verlag LNCS 2287, 2003./
/
[6] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA/
Considerations Section in RFCs", BCP 26, RFC 2434,/
October 1998./
/
[7] National Institute of Standards and Technology, "Specification/
for the Advanced Encryption Standard (AES)", Federal/
Information Processing Standards (FIPS) 197, November 2001./
/
[8] 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./
|
|
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
|
|
