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

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (urn WG)
Author Michael Mealling 
Last updated 2020-01-21 (latest revision 2002-05-07)
Stream Internet Engineering Task Force (IETF)
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3404 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Patrik Fältström
IESG note Responsible: RFC Editor
Send notices to <jcurran@netgeeks.net>
A new Request for Comments is now available in online RFC libraries.

        RFC 3404
        Title:      Dynamic Delegation Discovery System (DDDS)
                    Part Four: The Uniform Resource Identifiers (URI)
                    Resolution Application
        Author(s):  M. Mealling
        Status:     Standards Track
        Date:       October 2002
        Mailbox:    michael@neonym.net
        Pages:      18
        Characters: 40124
        Obsoletes:  2915, 2168
        I-D Tag:    draft-ietf-urn-uri-res-ddds-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3404.txt

This document describes a specification for taking Uniform Resource
Identifiers (URI) and locating an authoritative server for information
about that URI.  The method used to locate that authoritative server
is the Dynamic Delegation Discovery System.

This document is part of a series that is specified in "Dynamic
Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS"
(RFC 3401).  It is very important to note that it is impossible to
read and understand any document in this series without reading the

This document is a product of the Uniform Resource Names Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.