|
|
|
|
|
|
|
|
|
|
| Last Update: May 26, 2010
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3482
02/2003
(30 p.)
pdf(2p)
|
M. Foster
T. McGarry
J. Yu |
|
Number Portability in the Global Switched Telephone Network (GSTN): An Overview |
|
This document provides an overview of E.164 telephone number
portability (NP) in the Global Switched Telephone Network (GSTN).
NP is a regulatory imperative seeking to liberalize local telephony
service competition, by enabling end-users to retain telephone
numbers while changing service providers. NP changes the fundamental
nature of a dialed E.164 number from a hierarchical physical routing
address to a virtual address, thereby requiring the transparent
translation of the later to the former. In addition, there are
various regulatory constraints that establish relevant parameters for
NP implementation, most of which are not network technology specific.
Consequently, the implementation of NP behavior consistent with
applicable regulatory constraints, as well as the need for
interoperation with the existing GSTN NP implementations, are
relevant topics for numerous areas of IP telephony works-in-progress
with the IETF.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4114
06/2005
(17 p.)
pdf(2p)
|
S. Hollenbeck |
|
E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) |
|
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.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4415
02/2006
(8 p.)
pdf(2p)
|
R. Brandner
L. Conroy
R. Stastny |
|
IANA Registration for Enumservice Voice |
|
This document registers the Enumservice "voice" (which has a defined
subtype "tel"), as per the IANA registration process defined in the
ENUM specification RFC 3761. This service indicates that the contact
held in the generated Uniform Resource Identifier (URI) can be used
to initiate an interactive voice (audio) call.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4725
11/2006
(17 p.)
pdf(2p)
|
A. Mayrhofer
B. Hoeneisen |
|
ENUM Validation Architecture |
|
An ENUM domain name is tightly coupled with the underlying E.164
number. The process of verifying whether or not the Registrant of an
ENUM domain name is identical to the Assignee of the corresponding
E.164 number is commonly called "validation". This document
describes validation requirements and a high-level architecture for
an ENUM validation infrastructure.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4769
11/2006
(13 p.)
pdf(2p)
|
J. Livingood
R. Shockey |
|
IANA Registration for an Enumservice Containing
PSTN Signaling Information |
|
This document registers the Enumservice type "pstn" and subtype "tel"
using the URI scheme 'tel', as well as the subtype "sip" using the
URI scheme 'sip' as per the IANA registration process defined in the
ENUM specification, RFC 3761.
This Enumservice is used to facilitate
the routing of telephone calls in those countries where number
portability exists.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4969
08/2007
(7 p.)
pdf(2p)
|
A. Mayrhofer |
|
IANA Registration for vCard Enumservice |
This memo registers the Enumservice "vCard" using the URI schemes
"http" and "https". This Enumservice is to be used to refer from an
ENUM domain name to a vCard instance describing the user of the
respective E.164 number.
Information gathered from those vCards could be used before, during,
or after inbound or outbound communication takes place. For example,
a callee might be presented with the name and association of the
caller before picking up the call.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4979
08/2007
(7 p.)
pdf(2p)
|
A. Mayrhofer |
|
IANA Registration for Enumservice 'XMPP' |
|
This document requests IANA registration of an Enumservice for XMPP,
the Extensible Messaging and Presence Protocol. This Enumservice
specifically allows the use of 'xmpp' Uniform Resource Identifiers
(URIs) in the context of E.164 Number Mapping (ENUM).
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5067
11/2007
(7 p.)
pdf(2p)
|
S. Lind
P. Pfautz |
|
Infrastructure ENUM Requirements |
|
This document provides requirements for "infrastructure" or "carrier"
ENUM (E.164 Number Mapping), defined as the use of RFC 3761
technology to facilitate interconnection of networks for E.164 number
addressed services, in particular but not restricted to VoIP (Voice
over IP.)
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC5076
12/2007
(24 p.)
pdf(2p)
|
B. Hoeneisen |
|
ENUM Validation Information Mapping
for the Extensible Provisioning Protocol |
|
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.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5105
12/2007
(17 p.)
pdf(2p)
|
O. Lendl |
|
ENUM Validation Token Format Definition |
|
An ENUM domain name is tightly coupled with the underlying E.164
number. The process of verifying whether the Registrant of an ENUM
domain name is identical to the Assignee of the corresponding E.164
number is commonly called "validation". This document describes a
signed XML data format -- the Validation Token -- with which
Validation Entities can convey successful completion of a validation
procedure in a secure fashion.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5278
07/2008
(22 p.)
pdf(2p)
|
J. Livingood
D. Troshynski |
|
IANA Registration of Enumservices for Voice and Video Messaging |
|
This document registers the Enumservice named "vmsg", which is used
to facilitate the real-time routing of voice, video, and unified
communications to a messaging system. This vmsg Enumservice
registers three Enumservice types: "voicemsg", "videomsg", and
"unifmsg". Each type also registers the subtypes "sip", "sips",
"http", and "https", as well as the subtype "tel" for the "voicemsg"
type.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5333
10/2009
(8 p.)
pdf(2p)
|
R. Mahy
B. Hoeneisen |
|
IANA Registration of Enumservices for Internet Calendaring |
|
This document registers Enumservices for Internet calendaring.
Specifically, this document focuses on Enumservices for scheduling
with iMIP (iCalendar Message-Based Interoperability Protocol) and for
accessing Internet calendaring information with CalDAV (Calendaring
Extensions to WebDAV).
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5346
10/2008
(14 p.)
pdf(2p)
|
J. Lim
W. Kim
C. Park
L. Conroy |
|
Operational Requirements for ENUM-Based Softswitch Use |
This document describes experiences of operational requirements and
several considerations for ENUM-based softswitches concerning call
routing between two Korean Voice over IP (VoIP) carriers, gained
during the ENUM pre-commercial trial hosted by the National Internet
Development Agency of Korea (NIDA) in 2006.
These experiences show that an interim solution can maintain the
stability of ongoing commercial softswitch system operations during
the initial stage of ENUM service, where the DNS does not have
sufficient data for the majority of calls.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC5483
03/2009
(30 p.)
pdf(2p)
|
L. Conroy
K. Fujiwara |
|
ENUM Implementation Issues and Experiences |
|
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.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC5527
05/2009
(10 p.)
pdf(2p)
|
M. Haberler
O. Lendl
R. Stastny |
|
Combined User and Infrastructure ENUM in the e164.arpa Tree |
|
This memo defines an interim solution for Infrastructure ENUM in
order to allow a combined User and Infrastructure ENUM implementation
in e164.arpa as a national choice. This interim solution will be
deprecated after implementation of the long-term solution.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
