|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs was published by the Internet Research Task Force
|
|
3.
|
Justification for the specific reference:
|
|
|
Used as a normative reference
|
|
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=8032
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This document is a product of the Internet Research Task Force (IRTF) and represents the consensus of the Crypto Forum Research Group of the Internet Research Task Force (IRTF).
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Information document published in 2017
|
|
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:
|
|
|
[FIPS202] National Institute of Standards and Technology, "SHA-3/
Standard: Permutation-Based Hash and Extendable-Output/
Functions", FIPS PUB 202, August 2015,/
./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, DOI/
10.17487/RFC2119, March 1997,/
./
/
[RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms/
(SHA and SHA-based HMAC and HKDF)", RFC 6234,/
DOI 10.17487/RFC6234, May 2011,/
./
/
[RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves/
for Security", RFC 7748, DOI 10.17487/RFC7748, January/
2016, .
|
|
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
|
