metasystema.org
CurrentPROPOSED STANDARDIETF stream

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

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

This document discusses the use of the Domain Name System (DNS) for storage of data associated with E.164 numbers, and for resolving those numbers into URIs that can be used (for example) in telephony call setup. This document also describes how the DNS can be used to identify the services associated with an E.164 number. This document obsoletes RFC 3761. [STANDARDS-TRACK]

Document record

Document ID
RFC6116
Published
March 2011
Authors
S. Bradner; L. Conroy; K. Fujiwara
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
22
Also known as
—
Obsoletes:
RFC 3761

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 →

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/6116-the-e-164-to-uniform-resource-identifiers-uri-dynamic-delegation-discovery-syste