|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved in June 2014
|
|
3.
|
Justification for the specific reference:
|
|
|
This IETF RFC defines AES-CCM Elliptic Curve Cryptography (ECC) Cipher Suites for TLS that are used in this Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding document is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 7251 has been in existence since 2014.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
See clause 8
|
|
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)", FIPS 197, November 2001./
/
[CCM] National Institute of Standards and Technology,/
"Recommendation for Block Cipher Modes of Operation: The/
CCM Mode for Authentication and Confidentiality", SP/
800-38C, May 2004./
/
[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 Galois/
Counter Mode (GCM) Cipher Suites for TLS", RFC 5288,/
August 2008./
/
[RFC5639] Lochter, M. and J. Merkle, "Elliptic Curve Cryptography/
(ECC) Brainpool Standard Curves and Curve Generation", RFC/
5639, March 2010./
/
[RFC6066] Eastlake, D., "Transport Layer Security (TLS) Extensions:/
Extension Definitions", RFC 6066, January 2011./
/
[RFC6090] McGrew, D., Igoe, K., and M. Salter, "Fundamental Elliptic/
Curve Cryptography Algorithms", RFC 6090, February 2011./
/
[RFC6347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer/
Security Version 1.2", RFC 6347, January 2012./
/
[RFC6655] McGrew, D. and D. Bailey, "AES-CCM Cipher Suites for/
Transport Layer Security (TLS)", RFC 6655, July 2012./
[SP800-57] National Institute of Standards and Technology,/
"Recommendation for Key Management - Part 1: General/
(Revision 3)", SP 800-57 Part 1, July 2012./
[IEEE802154]/
IEEE, "Wireless Personal Area Networks", IEEE Standard/
802.15.4-2006, 2006./
/
[PKCS11] RSA Laboratories, "PKCS #11: Cryptographic Token Interface/
Standard version 2.20", Public Key Cryptography Standards/
PKCS#11-v2.20, 2004./
/
[RFC4309] Housley, R., "Using Advanced Encryption Standard (AES) CCM/
Mode with IPsec Encapsulating Security Payload (ESP)", RFC/
4309, December 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
|
|
