Telephone Number Mapping (enum) ------------------------------- Charter Last Modified: 2006-03-24 Current Status: Active Working Group Chair(s): Patrik Faltstrom Richard Shockey Real-time Applications and Infrastructure Area Director(s): Jon Peterson Cullen Jennings Real-time Applications and Infrastructure Area Advisor: Jon Peterson Secretary(ies): Alexander Mayrhofer 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 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 Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jul 2004 Jun 2006 ENUM Implementation Issues and Experiences Oct 2004 Oct 2005 IANA Registration for Enumservice VOID Sep 2005 Feb 2006 ENUM Validation Information Mapping for the Extensible Provisioning Protocol Oct 2005 Jun 2006 ENUM Validation Architecture Oct 2005 Feb 2006 ENUM Validation Token Format Definition Oct 2005 May 2006 IANA Registration for an Enumservice Containing PSTN Signaling Information Nov 2005 Jun 2006 IANA Registration for vCard Enumservice Feb 2006 Feb 2006 IANA Registration for IAX Enumservice Feb 2006 Jun 2006 Guide and Template for IANA Registrations of Enumervices Mar 2006 Apr 2006 Infrastrucure ENUM Requirements Mar 2006 Jun 2006 A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services Mar 2006 Jul 2006 A Telephone Number Mapping (ENUM) Service Registration for Internet Calendaring Services Apr 2006 Apr 2006 The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM Apr 2006 May 2006 IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC2916 PS Sep 2000 E.164 number and DNS RFC3482 I Feb 2003 Number Portability in the Global Switched Telephone Network (GSTN): An Overview RFC3764Standard May 2004 enumservice registration for SIP Addresses-of-Record RFC3762Standard May 2004 ENUM Service Registration for H.323 URL RFC3761Standard May 2004 The E.164 to URI DDDS Application (ENUM) RFC3953Standard Jan 2005 Enumservice Registration for Presence Services RFC4002Standard Feb 2005 IANA Registration for ENUMservices web and ft RFC4114Standard Jun 2005 E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) RFC4355Standard Jan 2006 IANA Registration for Enumservices email, fax, mms, ems and sms RFC4415 PS Feb 2006 IANA Registration for Enumservice Voice RFC4414 PS Feb 2006 An ENUM Registry Type for the Internet Registry Information Service (IRIS)