|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved; Proposed Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 5288 (2008), AES Galois Counter Mode (GCM) Cipher Suites for TLS, specifies the use of AES [AES] in Galois Counter Mode with various key exchange mechanisms as a cipher suite for TLS, which is an element for communication in conjuntion with the API for the access to the ECI Host IP stack resource in draft new J.1012. Thus IETF RFC 5288 (2008) is a normative reference for draft new J.1012 (ex-part3).
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
approved
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
approved and stable
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
n/a
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[AES] National Institute of Standards and Technology,/
"Advanced Encryption Standard (AES)", FIPS 197,/
November 2001./
/
[GCM] Dworkin, M., "Recommendation for Block Cipher Modes of/
Operation: Galois/Counter Mode (GCM) and GMAC",/
National Institute of Standards and Technology SP 800-/
38D, November 2007./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC5116] McGrew, D., "An Interface and Algorithms for/
Authenticated Encryption", RFC 5116, January 2008./
/
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer/
Security (TLS) Protocol Version 1.2", RFC 5246,/
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
|
