Naming Things with Hashes
RFC 6920
Document | Type |
RFC - Proposed Standard
(April 2013; Errata)
Was draft-farrell-decade-ni (individual)
|
|
---|---|---|---|
Authors | Stephen Farrell , Dirk Kutscher , Christian Dannewitz , Börje Ohlman , Ari Keränen , Phillip Hallam-Baker | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6920 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Barry Leiba | ||
IESG note | Alexey Melnikov (Alexey.Melnikov@isode.com) is the document shepherd. | ||
Send notices to | Alexey.Melnikov@isode.com |
Internet Engineering Task Force (IETF) S. Farrell Request for Comments: 6920 Trinity College Dublin Category: Standards Track D. Kutscher ISSN: 2070-1721 NEC C. Dannewitz University of Paderborn B. Ohlman A. Keranen Ericsson P. Hallam-Baker Comodo Group Inc. April 2013 Naming Things with Hashes Abstract This document defines a set of ways to identify a thing (a digital object in this case) using the output from a hash function. It specifies a new URI scheme for this purpose, a way to map these to HTTP URLs, and binary and human-speakable formats for these names. The various formats are designed to support, but not require, a strong link to the referenced object, such that the referenced object may be authenticated to the same degree as the reference to it. The reason for this work is to standardise current uses of hash outputs in URLs and to support new information-centric applications and other uses of hash outputs in protocols. Status of This Memo This is an Internet Standards Track document. 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). Further information on Internet Standards is available in Section 2 of RFC 5741. 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/rfc6920. Farrell, et al. Standards Track [Page 1] RFC 6920 Naming Things with Hashes April 2013 Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Hashes Are What Count . . . . . . . . . . . . . . . . . . . . 4 3. Named Information (ni) URI Format . . . . . . . . . . . . . . 6 3.1. Content Type Query String Attribute . . . . . . . . . . . 8 4. .well-known URI . . . . . . . . . . . . . . . . . . . . . . . 9 5. URL Segment Format . . . . . . . . . . . . . . . . . . . . . . 10 6. Binary Format . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Human-Speakable (nih) URI Format . . . . . . . . . . . . . . . 11 8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 8.1. Hello World! . . . . . . . . . . . . . . . . . . . . . . . 13 8.2. Public Key Examples . . . . . . . . . . . . . . . . . . . 13 8.3. nih Usage Example . . . . . . . . . . . . . . . . . . . . 14 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 9.1. Assignment of ni URI Scheme . . . . . . . . . . . . . . . 15 9.2. Assignment of nih URI Scheme . . . . . . . . . . . . . . . 15 9.3. Assignment of .well-known 'ni' URI . . . . . . . . . . . . 16 9.4. Creation of Named Information Hash Algorithm Registry . . 16 9.5. Creation of Named Information Parameter Registry . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 12.1. Normative References . . . . . . . . . . . . . . . . . . . 20 12.2. Informative References . . . . . . . . . . . . . . . . . . 21 Farrell, et al. Standards Track [Page 2] RFC 6920 Naming Things with Hashes April 2013 1. Introduction Identifiers -- names or locators -- are used in various protocols toShow full document text