RFC 5526: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM
In plain English — editorial summary, not part of the RFC
This document defines the use case for Infrastructure ENUM and proposes its implementation as a parallel namespace to "e164.arpa", as defined in RFC 3761, as the long-term solution to the problem of allowing carriers to provision DNS records for telephone numbers independently of those provisioned by end users (number assignees). This memo provides information for the Internet community.
Document record
- Document ID
- RFC5526
- Published
- April 2009
- Authors
- J. Livingood; P. Pfautz; R. Stastny
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5527Combined User and Infrastructure ENUM in the e164.arpa TreeCurrent
May 2009
- RFC 6116The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Current
March 2011
- RFC 5506Support for Reduced-Size Real-Time Transport Control Protocol (RTCP): Opportunities and ConsequencesCurrent
April 2009
- RFC 5552SIP Interface to VoiceXML Media ServicesCurrent
May 2009
- RFC 5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsUpdated
March 2009
- RFC 5486Session Peering for Multimedia Interconnect (SPEERMINT) TerminologyCurrent
March 2009
- RFC 5567An Architectural Framework for Media Server ControlCurrent
June 2009
- RFC 5484Associating Time-Codes with RTP StreamsCurrent
March 2009
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?