Telephone Number Mapping (enum)

Last Modified: 2006-12-15

Additional information is available at tools.ietf.org/wg/enum

Chair(s):

  • 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>

    Real-time Applications and Infrastructure Area Advisor:

  • Jon Peterson <jon.peterson@neustar.biz>

    Secretary(ies):

  • 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
    protocol
    [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).

    Background:

    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
    Standard.

    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
    working
    groups, existing or to be chartered, that are investigating elements of
    peering and or interconnection for VoIP or other services that
    typically
    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
    by
    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
    IP
    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
    them
    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
    Done  Enumservice Registration for Local Number Portability and Related Data as a Proposed Standard
    Done  Requirements for Carrier Interconnection using ENUM as an Informational
    Done  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

    Internet-Drafts:

    ENUM Implementation Issues and Experiences (60946 bytes)
    ENUM Validation Information Mapping for the Extensible Provisioning Protocol (45438 bytes)
    ENUM Validation Token Format Definition (32332 bytes)
    IANA Registration for vCard Enumservice (16832 bytes)
    IANA Registration for IAX Enumservice (15265 bytes)
    Guide and Template for IANA Registrations of Enumservices (35231 bytes)
    Infrastrucure ENUM Requirements (14554 bytes)
    A Telephone Number Mapping (ENUM) Service Registration for Internet Calendaring Services (11144 bytes)
    A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services (9869 bytes)
    The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM (11746 bytes)
    IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for Media type 'application/cnam' (26930 bytes)
    The ENUM Branch Location Record (15904 bytes)
    Combined User and Infrastructure ENUM in the e164.arpa tree (23749 bytes)
    ENUM Requirement for EDNS0 Support (23491 bytes)
    The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) (43424 bytes)
    IANA Registration for Enumservice 'XMPP' (12925 bytes)
    IANA Registration for Enumservice UNUSED (21876 bytes)

    Request For Comments:

    E.164 number and DNS (RFC 2916) (18159 bytes) obsoleted by RFC 3761
    Number Portability in the Global Switched Telephone Network (GSTN): An Overview (RFC 3482) (78552 bytes)
    enumservice registration for SIP Addresses-of-Record (RFC 3764) (17604 bytes)
    ENUM Service Registration for H.323 URL (RFC 3762) (8450 bytes)
    The E.164 to URI DDDS Application (ENUM) (RFC 3761) (41559 bytes) obsoletes RFC 2916
    Enumservice Registration for Presence Services (RFC 3953) (13875 bytes)
    IANA Registration for ENUMservices web and ft (RFC 4002) (18072 bytes)
    E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) (RFC 4114) (31490 bytes)
    IANA Registration for Enumservices email, fax, mms, ems and sms (RFC 4355) (30218 bytes)
    IANA Registration for Enumservice Voice (RFC 4415) (15956 bytes)
    An ENUM Registry Type for the Internet Registry Information Service (IRIS) (RFC 4414) (89985 bytes)
    IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information (RFC 4769) (24945 bytes)
    ENUM Validation Architecture (RFC 4725) (33216 bytes)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.