|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved April 2013
|
|
3.
|
Justification for the specific reference:
|
|
|
This IETF RFC defines the rules for Naming Things with Hashes 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=6920
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ISOIEC7812] ISO, "Identification cards -- Identification of issuers --/
Part 1: Numbering system", ISO/IEC 7812-1:2006,/
October 2006, http://www.iso.org/iso/iso_catalogue//
catalogue_tc/catalogue_detail.htm?csnumber=39698./
/
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part One: Format of Internet Message/
Bodies", RFC 2045, November 1996./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,/
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext/
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999./
/
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, January 2005./
/
/
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and/
Registration Procedures for New URI Schemes", BCP 35,/
RFC 4395, February 2006./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, October 2006./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
/
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,/
Housley, R., and W. Polk, "Internet X.509 Public Key/
Infrastructure Certificate and Certificate Revocation List/
(CRL) Profile", RFC 5280, May 2008./
/
[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known/
Uniform Resource Identifiers (URIs)", RFC 5785,/
April 2010./
/
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type/
Specifications and Registration Procedures", BCP 13,/
RFC 6838, January 2013./
/
[SHA-256] NIST, "Secure Hash Standard", FIPS 180-3, October 2008,/
http://csrc.nist.gov/publications/fips/fips180-3//
fips180-3_final.pdf.
|
|
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
|
|
