RFC 5483: ENUM Implementation Issues and Experiences
In plain English — editorial summary, not part of the RFC
This document captures experiences in implementing systems based on the ENUM protocol and experiences of ENUM data that have been created by others. As such, it clarifies the ENUM and Dynamic Delegation Discovery System standards. Its aim is to help others by reporting both what is "out there" and potential pitfalls in interpreting the set of documents that specify the ENUM protocol. It does not revise the standards but is intended to provide technical input to future revisions of those documents. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5483
- Published
- March 2009
- Authors
- L. Conroy; K. Fujiwara
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6116The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Current
March 2011
- RFC 5346Operational Requirements for ENUM-Based Softswitch UseCurrent
October 2008
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 4759The ENUM Dip Indicator Parameter for the "tel" URICurrent
December 2006
- RFC 2916E.164 number and DNSObsoleted
September 2000
- RFC 4143Facsimile Using Internet Mail (IFAX) Service of ENUMUpdated
November 2005
- RFC 3404Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)Current
October 2002
- RFC 3403Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) DatabaseCurrent
October 2002
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?