RFC 4114: E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)

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

This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of E.164 numbers that represent domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of E.164 numbers. [STANDARDS-TRACK]

Document record

Document ID

RFC4114

Published

June 2005

Authors

S. Hollenbeck

Status

PROPOSED STANDARD

Stream

IETF

Area

rai

Pages

17

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4114
• Reported errata exist →

Topics

• shared central repository

Related documents

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

• RFC 4117Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)Current

  June 2005

• RFC 4119A Presence-based GEOPRIV Location Object FormatUpdated

  December 2005

• RFC 4103RTP Payload for Text ConversationUpdated

  June 2005

• RFC 4102Registration of the text/red MIME Sub-TypeUpdated

  June 2005

• RFC 4129Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA ProtocolCurrent

  September 2005

• RFC 4092Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP)Obsoleted

  June 2005

• RFC 4083Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP)Current

  May 2005

• RFC 4079A Presence Architecture for the Distribution of GEOPRIV Location ObjectsCurrent

  July 2005

Also filed under

• PROPOSED STANDARD
• 2005
• IETF stream
• rai area