metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 3761: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6116, RFC 6117.

Current document in this lineage: RFC 6116 — The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM); RFC 6117 — IANA Registration of Enumservices: Guide, Template, and IANA Considerations

In plain English — editorial summary, not part of the RFC

This document discusses the use of the Domain Name System (DNS) for storage of E.164 numbers. More specifically, how DNS can be used for identifying available services connected to one E.164 number. It specifically obsoletes RFC 2916 to bring it in line with the Dynamic Delegation Discovery System (DDDS) Application specification found in the document series specified in RFC 3401. It is very important to note that it is impossible to read and understand this document without reading the documents discussed in RFC 3401. [STANDARDS-TRACK]

Document record

Document ID
RFC3761
Published
April 2004
Authors
P. Faltstrom; M. Mealling
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
18
Also known as
—
Obsoletes:
RFC 2916
Obsoleted by:
RFC 6116, RFC 6117

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 2916 (2000)
  2. RFC 3761 (2004)
  3. RFC 6116 (2011)
  4. RFC 6117 (2011) ✓

Read the full history of IANA Registration of Enumservices: Guide, Template, and IANA Considerations →

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3761-the-e-164-to-uniform-resource-identifiers-uri-dynamic-delegation-discovery-syste