Naming Things with Hashes
draft-farrell-decade-ni-07
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2012-06-04
(latest revision 2012-05-31)
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
In Last Call
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Barry Leiba
|
|
IESG note |
|
Alexey Melnikov (Alexey.Melnikov@isode.com) is the document shepherd.
|
|
Send notices to |
|
stephen.farrell@cs.tcd.ie, cdannewitz@upb.de, Borje.Ohlman@ericsson.com, kutscher@neclab.eu, philliph@comodo.com, ari.keranen@ericsson.com, draft-farrell-decade-ni@tools.ietf.org, Alexey.Melnikov@isode.com
|
Internet Engineering Task Force S. Farrell
Internet-Draft Trinity College Dublin
Intended status: Standards Track D. Kutscher
Expires: December 2, 2012 NEC
C. Dannewitz
University of Paderborn
B. Ohlman
A. Keranen
Ericsson
P. Hallam-Baker
Comodo Group Inc.
May 31, 2012
Naming Things with Hashes
draft-farrell-decade-ni-07
Abstract
This document defines a set of ways to identify a thing using the
output from a hash function, specifying URI, URL, 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.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 2, 2012.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
Farrell, et al. Expires December 2, 2012 [Page 1]
Internet-Draft Naming Things with Hashes May 2012
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Hashes are what Count . . . . . . . . . . . . . . . . . . . . 4
3. Named Information (ni) URI Format . . . . . . . . . . . . . . 5
4. .well-known URL Format . . . . . . . . . . . . . . . . . . . . 7
5. URL Segment Format . . . . . . . . . . . . . . . . . . . . . . 8
6. Binary Format . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Human-readable Format . . . . . . . . . . . . . . . . . . . . 9
8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9.1. Assignment of Named Information (ni) URI Scheme . . . . . 12
9.2. Assignment of Named Information for Humans (nih) URI
Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.3. Assignment of Well Known URI prefix ni . . . . . . . . . . 13
9.4. Hash Name Algorithm Registry . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 15
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
12.1. Normative References . . . . . . . . . . . . . . . . . . . 17
12.2. Informative References . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
Farrell, et al. Expires December 2, 2012 [Page 2]
Internet-Draft Naming Things with Hashes May 2012
1. Introduction
Names or identifiers are used in various protocols for identifying
resources. In many scenarios those names or identifiers contain
values that are hash function outputs. However, different
deployments have chosen various different ways to include hash
function outputs in such names or identifiers. This document
specifies standard ways to do that to aid interoperability.
Hash function outputs can be used to ensure uniqueness in terms of
mapping URIs [RFC3986] to a specific resource, or to make URIs hard
to guess for security reasons. Since, there is no standard way to
interpret those strings, today in general only the creator of the URI
Show full document text