|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were published via the Independent Stream Editor (ISE).
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation references these ciphers as specified in the reference.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/draft=&rfc=7539&doctitle=&group=&holder=&iprtitle=&patent=&submit=rfc
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been implemented in code in various languages and is used in several industry sectors already.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Information document published via the Independent Stream Editor (ISE).
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[AE] Bellare, M. and C. Namprempre, "Authenticated Encryption:/
Relations among notions and analysis of the generic/
composition paradigm", September 2008,/
./
/
[Cache-Collisions]/
Bonneau, J. and I. Mironov, "Cache-Collision Timing/
Attacks Against AES", 2006,/
./
/
[FIPS-197] National Institute of Standards and Technology, "Advanced/
Encryption Standard (AES)", FIPS PUB 197, November 2001,/
fips-197.pdf>./
/
[LatinDances]/
Aumasson, J., Fischer, S., Khazaei, S., Meier, W., and C./
Rechberger, "New Features of Latin Dances: Analysis of/
Salsa, ChaCha, and Rumba", December 2007,/
./
/
[LatinDances2]/
Ishiguro, T., Kiyomoto, S., and Y. Miyake, "Modified/
version of 'Latin Dances Revisited: New Analytic Results/
of Salsa20 and ChaCha'", February 2012,/
./
/
[NaCl] Bernstein, D., Lange, T., and P. Schwabe, "NaCl:/
Networking and Cryptography library", July 2012,/
./
/
[Poly1305_Donna]/
Floodyberry, A., "poly1305-donna", February 2014,/
./
/
[Procter] Procter, G., "A Security Analysis of the Composition of/
ChaCha20 and Poly1305", August 2014,/
./
/
[RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA-/
384, and HMAC-SHA-512 with IPsec", RFC 4868,/
DOI 10.17487/RFC4868, May 2007,/
./
/
[RFC5116] McGrew, D., "An Interface and Algorithms for Authenticated/
Encryption", RFC 5116, DOI 10.17487/RFC5116, January 2008,/
./
/
[RFC7296] Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T./
Kivinen, "Internet Key Exchange Protocol Version 2/
(IKEv2)", STD 79, RFC 7296, DOI 10.17487/RFC7296, October/
2014, ./
/
[SP800-67] National Institute of Standards and Technology,/
"Recommendation for the Triple Data Encryption Algorithm/
(TDEA) Block Cipher", NIST 800-67, January 2012,/
SP-800-67-Rev1.pdf>./
/
[Standby-Cipher]/
McGrew, D., Grieco, A., and Y. Sheffer, "Selection of/
Future Cryptographic Standards", Work in Progress,/
draft-mcgrew-standby-cipher-00, January 2013./
/
[Zhenqing2012]/
Zhenqing, S., Bin, Z., Dengguo, F., and W. Wenling,/
"Improved Key Recovery Attacks on Reduced-Round Salsa20/
and ChaCha*", 2012./
/
|
|
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
|
|
