|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5289 (2008)
|
|
Title:
|
TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)
|
|
|
2.
|
Status of approval:
|
|
|
Approved; Standards Track
|
|
3.
|
Justification for the specific reference:
|
|
|
This IETF RFC defines the TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM) that are used in this Recommendation.
|
|
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:
|
|
|
[RFC2104] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed-Hashing for Message Authentication", RFC 2104, February 1997./
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC4492] Blake-Wilson, S., Bolyard, N., Gupta, V., Hawk, C., and B.Moeller, "Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS)", RFC 4492, May 2006./
[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./
[RFC5288] Salowey, J., Choudhury, A., and D. McGrew, "AES-GCM Cipher Suites for TLS", RFC 5288, August 2008./
[AES] National Institute of Standards and Technology, "Specification for the Advanced Encryption Standard (AES)", FIPS 197, November 2001./
[SHS] National Institute of Standards and Technology, "Secure Hash Standard", FIPS 180-2, August 2002./
[CBC] National Institute of Standards and Technology,"Recommendation for Block Cipher Modes of Operation - Methods and Techniques", SP 800-38A, December 2001./
[GCM] National Institute of Standards and Technology, "Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) for Confidentiality and Authentication", SP 800-38D, November 2007./
[Wang05] Wang, X., Yin, Y., and H. Yu, "Finding Collisions in the Full SHA-1", CRYPTO 2005, August 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
|
|
