2.5.3 Telephone Number Mapping (enum)

NOTE: This charter is a snapshot of the 66th IETF Meeting in Montreal, Quebec Canada. It may now be out-of-date.

Last Modified: 2006-03-24


Patrik Faltstrom <paf@cisco.com>
Richard Shockey <rich.shockey@neustar.biz>

Real-time Applications and Infrastructure Area Director(s):

Jon Peterson <jon.peterson@neustar.biz>
Cullen Jennings <fluffy@cisco.com>

* The Real-time Applications and Infrastructure Area Directors were seated during the IETF 65.

Real-time Applications and Infrastructure Area Advisor:

Jon Peterson <jon.peterson@neustar.biz>


Alexander Mayrhofer <alexander.mayrhofer@enum.at>

Mailing Lists:

General Discussion: enum@ietf.org
To Subscribe: enum-request@ietf.org
In Body: subscribe
Archive: http://www.ietf.org/mail-archive/web/enum/index.html

Description of Working Group:

The ENUM working group has defined a DNS-based architecture and
[RFC 3761] by which an E.164 number, as defined in ITU Recommendation
E.164, can be expressed as a Fully Qualified Domain Name in a specific
Internet Infrastructure domain defined for this purpose (e164.arpa).


E.164 numbers are globally unique, language independent identifiers for
resources on Public Telecommunication Networks that can support many
different services and protocols. There is an emerging desire for
network operators to utilize aspects of RFC 3761 to discover points of
interconnection necessary to terminate communications sessions
identified by a E164 number,in addition to identifying end point
protocols and services.

Working Group Revised Goals and Scope:

1. The working group will update RFC 3761 and advance to Draft

2. The working group will examine and document the use of RFC 3761 to
facilitate network interconnection for services using E.164 addressing.
The working group will coordinate its activities with other IETF
groups, existing or to be chartered, that are investigating elements of
peering and or interconnection for VoIP or other services that
use E.164 addressing.

3. The working group will continue examine and document various aspects
of ENUM administrative and /or operational procedures irrespective of
whether e164.arpa domain is used.

4. The working group will also examine the use of RFC 3761 technology
for storing and delivering other information about services addressed
E.164 numbers, for example PSTN call routing and signaling data.

5. The Working Group will continue to maintain appropriate contact and
liaison with other standards bodies and groups, specifically ITU-T SG2,
to provide technical or educational information and address, as needed,
issues related to the use of the E.164 numbering plan for services on
networks. In addition the Working Group will continue to encourage the
exchange of technical information within the emerging global ENUM
community as well as documentation on practical experiences with
implementations, alternate technology uses and the administration and
provisioning of RFC 3761.

6. As described in RFC 3761, the IETF documents and registers the
Enumservices. While extant, it is the ENUM working group that performs
the technical review and development of the Enumservices for the
Internet community. The working group determines whether to advance
and how to progress them technically. Coordination with other WGs will
be taken into account on these.

Other than Enumservices, all proposed deliverables of the working group
will be discussed with and approved by the Area Directors, who may
require wider review due to the broad impact of the subject.

Goals and Milestones:

Done  Initial draft of Service ENUM Requirements
Done  Initial draft of ENUM Protocol
Done  Revised draft of ENUM Protocol
Done  Submit ENUM Protocol document to IESG for publication as Proposed
Done  Revise and update RFC 2916 appropriate to DDDS (revision of 2915)
Done  ENUM service registrations for SIP and H.323
Mar 2006  Enumservice Registration for Local Number Portability and Related Data as a Proposed Standard
Apr 2006  Requirements for Carrier Interconnection using ENUM as an Informational
Jun 2006  Carrier Interconnection using ENUM as a Proposed Standard
Jul 2006  ENUM Privacy and Security Considerations as an Informational
Aug 2006  Advancement of RFC 3761 to Draft Standard


  • draft-ietf-enum-experiences-05.txt
  • draft-ietf-enum-void-02.txt
  • draft-ietf-enum-validation-epp-03.txt
  • draft-ietf-enum-validation-arch-04.txt
  • draft-ietf-enum-validation-token-02.txt
  • draft-ietf-enum-pstn-05.txt
  • draft-ietf-enum-vcard-04.txt
  • draft-ietf-enum-iax-01.txt
  • draft-ietf-enum-enumservices-guide-02.txt
  • draft-ietf-enum-infrastructure-enum-reqs-03.txt
  • draft-ietf-enum-im-service-01.txt
  • draft-ietf-enum-calendar-service-01.txt
  • draft-ietf-enum-infrastructure-00.txt
  • draft-ietf-enum-cnam-04.txt
  • draft-ietf-enum-branch-location-record-00.txt
  • draft-ietf-enum-combined-01.txt
  • draft-ietf-enum-edns0-00.txt
  • draft-ietf-enum-uri-00.txt
  • draft-ietf-enum-3761bis-00.txt

    Request For Comments:

    RFC2916 PS E.164 number and DNS
    RFC3482 I Number Portability in the Global Switched Telephone Network (GSTN): An Overview
    RFC3761 Standard The E.164 to URI DDDS Application (ENUM)
    RFC3762 Standard ENUM Service Registration for H.323 URL
    RFC3764 Standard enumservice registration for SIP Addresses-of-Record
    RFC3953 Standard Enumservice Registration for Presence Services
    RFC4002 Standard IANA Registration for ENUMservices web and ft
    RFC4114 Standard E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)
    RFC4355 Standard IANA Registration for Enumservices email, fax, mms, ems and sms
    RFC4414 PS An ENUM Registry Type for the Internet Registry Information Service (IRIS)
    RFC4415 PS IANA Registration for Enumservice Voice

    Meeting Minutes


    ENUM document status
    Enumservice ERN
    Infrastructure ENUM DDDS Application
    Enumservices Guide & Template
    3761 BIS revision to Draft Status
    Combined User and Carrier ENUM in the e164.arpa tree
    Enumservices guide and template