Last Modifield: 05/06/2002
The Working Group proposes to advance RFC 2916 from Proposed Standard to 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 are supported by the terminal named by a given telephone number. The caller may also require more information than just the telephone number to communicate with the terminal.
The holder of an E.164 number or device may wish to control what URI's, are 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.
|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|
|JUN 02||Revise and update RFC 2916 appropriate to DDDS (revision of 2915) and advance to Draft Standard|
|JUL 02||Document appropriate ENUM Registration and Provisioning Procedures (Informational)|
|AUG 02||Document appropriate ENUM Operational Security, Privacy Issues and Procedures (Informational)|
|RFC2916||PS||E.164 number and DNS|