A Uniform Resource Name (URN) Namespace for Federated Content
RFC 4198

Document Type RFC - Informational (November 2005; No errata)
Author Dave Tessman 
Last updated 2015-10-14
Stream IETF
Formats plain text html pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 4198 (Informational)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ted Hardie
Send notices to (None)
Network Working Group                                         D. Tessman
Request for Comments: 4198                                      Zelestra
Category: Informational                                    November 2005

     A Uniform Resource Name (URN) Namespace for Federated Content

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).


   This document describes a URN (Uniform Resource Name) namespace for
   identifying content resources within federated content collections.
   A federated content collection often does not have a strong
   centralized authority but relies upon shared naming, metadata, and
   access conventions to provide interoperability among its members.

1.  Introduction

   Federated content collections are often loose constructs of both
   small and large content providers, with an active community, but
   without significant central authority.  Members are bound together by
   shared purpose and interoperate through shared naming, metadata, and
   access conventions.  Federations may also consist of other
   federations, creating complex associations and dependencies.

   A content provider may join or leave a federation at any time and may
   be part of more than one federation at the same time.  Content
   providers may also cease as organizations altogether, freeing their
   domain names for use by others.  In addition, content identifiers are
   spread throughout the members of a federation.  These identifiers are
   stored on various media, sometimes for long durations before being
   used.  Therefore, although they work well in situations without a
   strong content naming authority, URLs are insufficient as content
   identifiers within a federation because they cannot be uniquely and
   permanently tied to a specific content resource.

Tessman                      Informational                      [Page 1]
RFC 4198          URN Namespace for Federated Content      November 2005

   This URN namespace provides a mechanism whereby a central naming
   authority is not required.  Providers maintain naming authority over
   their own content within guidelines that guarantee URNs to be unique
   and permanent.

   A simple identifier resolution convention is also recommended to
   provide a consistent URN resolver interface across all providers.

   This namespace specification is for a formal namespace.

2.  Terminology

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   and "OPTIONAL" are to be interpreted as described in RFC 2119 [1].

3.  Specification Template

   Namespace ID:


   Registration Information:

      Registration Version Number: 1
      Registration Date: 2005-04-25

   Declared registrant of the namespace:

      Name:       Zelestra
      Address:    2314 Henrietta Avenue
                  La Crescenta, CA 91214-3007

      Contact:    Dave Tessman
      E-mail:     dtessman@zelestra.com

   Declaration of syntactic structure:

      The NSS has the following ABNF [2] specification:

      NSS         = ProviderId ":" DateId ":" ResourceId
      ProviderId  = 1*(label ".") toplabel
      DateId      = (CCYY [MM [DD]]) / 1*3(DIGIT)
      ResourceId  = 1*(alphanum / other / ("%" hex hex))
      label       = alphanum / alphanum *(alphanum / "-") alphanum
      toplabel    = ALPHA / ALPHA *(alphanum / "-") alphanum
      CCYY        = 4(DIGIT)

Tessman                      Informational                      [Page 2]
RFC 4198          URN Namespace for Federated Content      November 2005

      MM          = ("0" %x31-39) / ("1" %x30-32)
      DD          = ("0" %x31-39) / (%x31-32 DIGIT) / "30" / "31"
      alphanum    = ALPHA / DIGIT
      hex         = DIGIT / %x41-46 / %x61-66
      other       = "(" / ")" / "+" / "," / "-" / "." / ":" / "=" /
                    "@" / ";" / "$" / "_" / "!" / "*" / "'"

      ProviderId is the content provider's identifier.  ProviderId MUST
      be an Internet domain name and MUST be owned by the organization
      creating the resource and allocating the URN to the resource.

      DateId is a date in ISO 8601 Basic Format (CCYY[MM[DD]]), and MUST
      correspond to a specific day on which the organization allocating
      the URN owned the domain name specified in the ProviderId.  If not
      included, the default value for MM and DD is "01".  DateIds of 1
      to 3 digits are reserved.

      ResourceId MUST be unique among all ResourceIds emanating from the
      same provider and having the same DateId.

   Relevant ancillary documentation:


   Identifier uniqueness considerations:

      The combination of ProviderId and DateId serves to uniquely
      identify the organization that is allocating the URN.  That
Show full document text