RFC 3404: Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)
In plain English — editorial summary, not part of the RFC
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 others. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3404
- Published
- October 2002
- Authors
- M. Mealling
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 18
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3403Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) DatabaseCurrent
October 2002
- RFC 3402Dynamic Delegation Discovery System (DDDS) Part Two: The AlgorithmCurrent
October 2002
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 3123A DNS RR Type for Lists of Address Prefixes (APL RR)Current
June 2001
- RFC 3401Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDSCurrent
October 2002
- RFC 4143Facsimile Using Internet Mail (IFAX) Service of ENUMUpdated
November 2005
- RFC 3755Legacy Resolver Compatibility for Delegation Signer (DS)Obsoleted
May 2004
- RFC 3845DNS Security (DNSSEC) NextSECure (NSEC) RDATA FormatObsoleted
August 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?