RFC 6920: Naming Things with Hashes
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6920
- Published
- April 2013
- Authors
- S. Farrell; D. Kutscher; C. Dannewitz; B. Ohlman; A. Keranen; P. Hallam-Baker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6570URI TemplateCurrent
March 2012
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 6283Extensible Markup Language Evidence Record Syntax (XMLERS)Current
July 2011
- RFC 7565The 'acct' URI SchemeCurrent
May 2015
- RFC 6270The 'tn3270' URI SchemeCurrent
June 2011
- RFC 6196Moving mailserver: URI Scheme to HistoricCurrent
March 2011
- RFC 5870A Uniform Resource Identifier for Geographic Locations ('geo' URI)Current
June 2010
- RFC 8141Uniform Resource Names (URNs)Current
April 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?