The Named Information (ni) URI Scheme: Core Syntax
draft-farrell-decade-ni-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2011-10-24
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                               S. Farrell
Internet-Draft                                    Trinity College Dublin
Intended status: Standards Track                             D. Kutscher
Expires: April 26, 2012                                              NEC
                                                            C. Dannewitz
                                                 University of Paderborn
                                                               B. Ohlman
                                                                Ericsson
                                                         P. Hallam-Baker
                                                       Comodo Group Inc.
                                                        October 24, 2011

           The Named Information (ni) URI Scheme: Core Syntax
                       draft-farrell-decade-ni-00

Abstract

   This document defines a URI-based name form that identifies a named
   object via hash-based binding.  The URI name form defined is intended
   for use in applications that need to uniquely identify resources in a
   location-independent way such as accessing in-network storage
   (DECADE), information-centric networking and more generally.  The
   format is designed to support 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 April 26, 2012.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Farrell, et al.          Expires April 26, 2012                 [Page 1]
Internet-Draft                 ni URI Core                  October 2011

   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.  Format . . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Processing NI URIs . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Verifying URI/Resource Mappings  . . . . . . . . . . . . .  4
     3.2.  Testing for Equality . . . . . . . . . . . . . . . . . . .  5
     3.3.  Mapping to HTTP(S) URLs  . . . . . . . . . . . . . . . . .  5
   4.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   5.  The Named Information URI TYPE . . . . . . . . . . . . . . . .  6
     5.1.  Encoding Considerations  . . . . . . . . . . . . . . . . .  6
     5.2.  Syntax . . . . . . . . . . . . . . . . . . . . . . . . . .  7
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  8
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
     8.1.  Assignment of Network Information (ni) URI Scheme  . . . .  8
     8.2.  Assignment of Well Known URI prefix ni . . . . . . . . . .  9
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     9.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10

Farrell, et al.          Expires April 26, 2012                 [Page 2]
Internet-Draft                 ni URI Core                  October 2011

1.  Introduction

   URIs [RFC3986] are used in various protocols for identifying
   resources.  In many deployments those URIs contain strings that are
   hash function outputs in order to ensure uniqueness in terms of
   mapping the URI to a specific resource, or to make URIs hard to guess
   for security reasons.  However, there is no standard way to interpret
   those strings, and so today in general only the creator of the URI
Show full document text