RFC 5076: ENUM Validation Information Mapping for the Extensible Provisioning Protocol
In plain English — editorial summary, not part of the RFC
This document describes an Extensible Provisioning Protocol (EPP) extension framework for mapping information about the validation process that has been applied for the E.164 number (or number range) that the E.164 Number Mapping (ENUM) domain name is based on. Specified in the Extensible Markup Language (XML), this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of ENUM Domain Names. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5076
- Published
- December 2007
- Authors
- B. Hoeneisen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4969IANA Registration for vCard EnumserviceUpdated
August 2007
- RFC 5346Operational Requirements for ENUM-Based Softswitch UseCurrent
October 2008
- RFC 6315IANA Registration for Enumservice 'iax'Current
July 2011
- RFC 5105ENUM Validation Token Format DefinitionCurrent
December 2007
- RFC 4979IANA Registration for Enumservice 'XMPP'Updated
August 2007
- RFC 5333IANA Registration of Enumservices for Internet CalendaringUpdated
October 2009
- RFC 4759The ENUM Dip Indicator Parameter for the "tel" URICurrent
December 2006
- RFC 4725ENUM Validation ArchitectureCurrent
November 2006
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?