ITU's 160 anniversary

Committed to connecting the world

  •  
Girls in ICT day 2025

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Y.oneM2M.SEC.SOL     
  ITU-T A.5 justification information for referenced document IETF RFC 5487 (2009) in draft Y.oneM2M.SEC.SOL
1. Clear description of the referenced document:
Name: IETF RFC 5487 (2009)
Title: Pre-Shared Key Cipher Suites for TLS with SHA-256/384 and AES Galois Counter Mode
2. Status of approval:
Approved as IETF document
3. Justification for the specific reference:
This IETF RFC defines the Pre-Shared Key Cipher Suites for TLS with SHA-256/384 and AES Galois Counter Mode 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/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=5487
5. Other useful information describing the "Quality" of the document:
This RFC was approved in March 2009.
6. The degree of stability or maturity of the document:
Informational IETF Stream document approved March 2009.
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./
/
[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./
/
[MODES] National Institute of Standards and Technology,/
"Recommendation for Block Cipher Modes of Operation -/
Methods and Techniques", SP 800-38A, December 2001./
/
[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./
/
[RFC4279] Eronen, P. and H. Tschofenig, "Pre-Shared Key Ciphersuites/
for Transport Layer Security (TLS)", RFC 4279,/
December 2005./
/
[RFC4785] Blumenthal, U. and P. Goel, "Pre-Shared Key (PSK)/
Ciphersuites with NULL Encryption for Transport Layer/
Security (TLS)", RFC 4785, January 2007./
[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./
/
[SHS] National Institute of Standards and Technology, "Secure/
Hash Standard", FIPS 180-2, August 2002./
[RFC5289] Rescorla, E., "TLS Elliptic Curve Cipher Suites with SHA-/
256/384 and AES Galois Counter Mode (GCM)", RFC 5289,/
August 2008./
/
[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
Note: This form is based on Recommendation ITU-T A.5