|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
May 2011 as Information
|
|
3.
|
Justification for the specific reference:
|
|
|
The referenced document constitutes provisions of this Recommendation
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG).
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6234.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None.
|
|
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./
/
[RFC5869] Krawczyk, H. and P. Eronen, "HMAC-based Extract-and-Expand/
Key Derivation Function (HKDF)", RFC 5869, May 2010./
/
[SHS] "Secure Hash Standard", United States of American,/
National Institute of Science and Technology, Federal/
Information Processing Standard (FIPS) 180-3,/
http://csrc.nist.gov/publications/fips/fips180-3//
fips180-3_final.pdf./
/
[US-ASCII] ANSI, "USA Standard Code for Information Interchange",/
X3.4, American National Standards Institute: New York,/
1968.
|
|
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.
|
