RFC 3404 (rfc3404) - Page 2 of 18

Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)

RFC 3404               DDDS Based URI Resolution            October 2002


   4.5   Valid Databases  . . . . . . . . . . . . . . . . . . . . . .  7
   5.    Examples . . . . . . . . . . . . . . . . . . . . . . . . . .  8
   5.1   An example using a URN . . . . . . . . . . . . . . . . . . .  8
   5.2   CID URI Scheme Example . . . . . . . . . . . . . . . . . . .  9
   5.3   Resolving an HTTP URI Scheme . . . . . . . . . . . . . . . . 11
   6.    Notes  . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
   7.    IANA Considerations  . . . . . . . . . . . . . . . . . . . . 12
   8.    Security Considerations  . . . . . . . . . . . . . . . . . . 12
   9.    Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . 13
         References . . . . . . . . . . . . . . . . . . . . . . . . . 13
         Appendix A: Pseudo Code  . . . . . . . . . . . . . . . . . . 15
         Author's Address . . . . . . . . . . . . . . . . . . . . . . 17
         Full Copyright Statement . . . . . . . . . . . . . . . . . . 18

1. Introduction

   The Dynamic Delegation Discovery System (DDDS) is used to implement
   lazy binding of strings to data, in order to support dynamically
   configured delegation systems.  The DDDS functions by mapping some
   unique string to data stored within a DDDS Database by iteratively
   applying string transformation rules until a terminal condition is
   reached.

   This document describes a DDDS Application for resolving Uniform
   Resource Identifiers (URI).  It does not define the DDDS Algorithm or
   a Database.  The entire series of documents that do so are specified
   in "Dynamic Delegation Discovery System (DDDS) Part One: The
   Comprehensive DDDS" (RFC 3401) [1].  It is very important to note
   that it is impossible to read and understand any document in that
   series without reading the related documents.

   Uniform Resource Identifiers (URI) have been a significant advance in
   retrieving Internet-accessible resources.  However, their brittle
   nature over time has been recognized for several years.  The Uniform
   Resource Identifier working group proposed the development of Uniform
   Resource Names (URN) [8] to serve as persistent, location-independent
   identifiers for Internet resources in order to overcome most of the
   problems with URIs.  RFC 1737 [6] sets forth requirements on URNs.

   During the lifetime of the URI-WG, a number of URN proposals were
   generated.  The developers of several of those proposals met in a
   series of meetings, resulting in a compromise known as the Knoxville
   framework.  The major principle behind the Knoxville framework is
   that the resolution system must be separate from the way names are
   assigned.  This is in marked contrast to most URIs, which identify
   the host to contact and the protocol to use.  Readers are referred to
   [7] for background on the Knoxville framework and for additional
   information on the context and purpose of this proposal.



Mealling                    Standards Track