2.8.3 Telephone Number Mapping (enum)

Last Modified: 2003-06-30

Patrik Faltstrom <paf@cisco.com>
Richard Shockey <rich.shockey@neustar.biz>
Transport Area Director(s):
Allison Mankin <mankin@psg.com>
Jon Peterson <jon.peterson@neustar.biz>
Transport Area Advisor:
Allison Mankin <mankin@psg.com>
Mailing Lists:
General Discussion: enum@ietf.org
To Subscribe: enum-request@ietf.org
In Body: subscribe
Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/
Description of Working Group:
This working group has defined a DNS-based architecture and protocol
2916] by which an E.164 number, as defined in ITU Recommendation E.164,
be expressed as a Fully Qualified Domain Name in a specific Internet
Infrastructure domain defined for this purpose (e164.arpa). The result
the ENUM query is a series of DNS NAPTR resource records [RFC2915] 
can be used to contact a resource (e.g.URI) associated with that

The Working Group proposes to advance RFC 2916 from Proposed Standard
Draft Standard.


E.164 numbers are globally unique, language independent identifiers for
resources on Public Telecommunication Networks that can support many
different services and protocols. E.164 numbers are used to identify
ordinary phones, fax machines, pagers, data modems, email clients, text
terminals for the hearing impaired, etc.

A prospective caller may wish to discover which services and protocols
supported by the terminal named by a given telephone number. The caller
also require more information than just the telephone number to
with the terminal.

The holder of an E.164 number or device may wish to control what URI's,
associated with that number.

Working Group Revised Goals and Scope:

1. The working group will update RFC 2916 to reference the DDDS system
  (revision of RFC 2915) and advance RFC 2916 to Draft Standard.

2. The working group will examine and document various aspects of ENUM
  administrative and/or operational procedures as Informational.
  Issues to be considered include privacy and security considerations
  in storing ENUM related data as well as validation and
  authentication of data, including DDDS NAPTR records in the DNS. The
  working group will coordinate activities in these areas with the
  DNSEXT WG and PROVREG WG when appropriate.

3. The Working Group will continue to maintain appropriate contact and
  liaison with standards bodies and groups, specifically ITU-T SG2,
  in order to provide technical or educational information as needed,
  such as the appropriate use of DNS.  The Working Group will
  encourage the exchange of technical information within the
  emerging global ENUM community as well as documentation on practical
  experiences with implementations or administration of RFC 2916.
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
Aug 03  Document appropriate ENUM Security and Privacy Issues (Informational)
Nov 03  Document appropriate ENUM Registration and Provisioning Procedures (Informational)
  • - draft-ietf-enum-rfc2916bis-06.txt
  • - draft-ietf-enum-epp-e164-02.txt
  • - draft-ietf-enum-privacy-security-01.txt
  • - draft-ietf-enum-h323-01.txt
  • - draft-ietf-enum-sip-00.txt
  • - draft-ietf-enum-msg-00.txt
  • - draft-ietf-enum-webft-00.txt
  • Request For Comments:
    E.164 number and DNS (RFC 2916) (18159 bytes)
    Number Portability in the Global Switched Telephone Network (GSTN): An Overview (RFC 3482) (78552 bytes)

    Current Meeting Report

    None received.


    The UK ENUM Trial
    Privacy & Security
    VoIP and ENUM The Austrian Trial
    ENUM Trial Implementation in Korea
    ENUM in Sweden