1. Update on ITU-T ENUM Activities Steven D. Lind AT&T SG-A ENUM - Ad Hoc February 12, 2001

2. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc2 Workshops and Meetings §IP-Telecom Interworking Workshop on Numbering, Naming, Addressing and Routing (25-27 January 2000) §ITU-T Study Group 2 Meetings l 7-17 March 2000 l 19-26 October 2000 (Working Party 1/2) l 23 January - 2 February 2001 §ITU ENUM Workshop (17 January 2001)

3. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc3 IP-Telecom Interworking Workshop §Introduction of IETF & ITU-T Environments §Initial List of NNAR Issues to Allow Interworking §Identification of Lead Group to Progress Work

4. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc4 ITU-T Study Group 2 Meeting 7-17 March 2000 §Began Work on SG2 Issues §Familiarity with IETF Work Referencing Rec. E.164 §Submitted I-Ds on: l E.164 Supplement on Number Portability l Draft Rec. E.370 - Service Principles of PSTN-IP Interworking l Draft Rec. E.callflows - ENUM Call Flows for VoIP Interworking

5. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc5 Working Party 1/2 Meeting 19-26 October 2000 §Liaison Developed from WP 1/2 to IETF/ISOC §Sets Out Common Understandings Made on Administration and other Aspects §Will Form the Basis for On-Going Studies §www.itu.int/infocom/enum/wp1-39_rev1.htm §www.ietf.org/rfc/rfc3026.txt

6. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc6 Liaison Statement §The Actual Operation of the ENUM DNS ("e164.arpa") was Outside the Scope of Study Group 2. §Information for and Participation by Each Country was a National Matter. l Each member state would inform the TSB of the name server that would house the country/service specific information. l The information to be put into DNS at the country code level would come only from the TSB.

7. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc7 ITU ENUM Workshop 17 January 2001 §Objective: Discuss Administrative Issues Related to the Operational Deployment of the ENUM Protocol §Tutorials presented on: l Overview of the Domain Name System l ENUM Technical Issues l ENUM l ENUM Administration - Some Numbering Perspectives

8. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc8 Administration Issues §ISSUE 1: An agreed process needs to be developed, e.g., between appropriate authorities. §ISSUE 2: The status of.arpa matters (including e164.arpa matters) is ?? §ISSUE 3: The following "issues" text was discussed. l Building and Maintaining integrity of E.164 l How should Tier 1 Registries be selected?

9. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc9 Administration Issues (cont.) §ISSUE 4:These are also items about inserting numbers into Registries (for ENUM) for numbers that are within a Country Code for a Country (or an integrated numbering plan), as national matters: l How to determine the most appropriate arrangement? l Who runs national Registries? l An agreed process needs to be developed between participating Member States [of an Integrated Numbering Plan].

10. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc10 Administration Issues (cont.) §ISSUE 5: These are items about inserting numbers into DNS for numbering resources that are within a Country Code shared by Networks: l Assignees of Network Codes need to be formally made aware of their obligations with respect to ENUM. l Some ITU-T Recommendations related to E.164 Network Codes may require review/amendment/revision.

11. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc11 Administration Issues (cont.) §ISSUE 6: These are items about inserting numbers into DNS for numbering resources that are within a Country Code shared by Groups of Countries (noting that this is work in progress in ITU-T SG2): l Assignees of E.164 resources for Groups of Countries need to be formally made aware of their obligations with respect to ENUM. l Some ITU-T Recommendations related to E.164 resources for Groups of Countries may require review/amendment/revision.

12. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc12 Administration Issues (cont.) §ISSUE 7: For E.164 resources behind a CC+IC (for Networks) or a CC+GIC (for Groups of Countries), resource assignees are responsible for providing E.164 assignment information to DNS Administrators (for ENUM). §ISSUE 8: This item was discussed when Number Portability (NP) was considered with respect to ENUM: l In some cases with Number Portability, the name server must point to a Service Registrar on an individual E.164 number basis, not a number block.

13. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc13 Administration Issues (cont.) §ISSUE 9: This item was discussed when aspects of Service Providers were considered with respect to ENUM: l Some countries are moving to single number administration and payment for numbers, does this raise additional issues? §ISSUE 10: What is the relationship between a user and a telephone number, and how is that relationship expressed in ENUM? l Differences across Administrations? l Intellectual Property Rights?

14. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc14 Administration Issues (cont.) §ISSUE 11: Customer perception where an E.164 number that provides access to an ISP, other than the one responsible for the number, experiences differing QoS and cost? §ISSUE 12: Privacy of information/consumer protection. §ISSUE 13: Legal intercept? §ISSUE 14: Regulatory implications e.g., monitoring of QoS, etc.? §ISSUE 15: Determination of who qualifies to be a Service Registrar?

15. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc15 Administration Issues (cont.) §ISSUE 16: Concerning some ENUM administration issues related to the Service Registrar models: l Is one model, or are a number of different models, preferable? §ISSUE 17: How can E.164/DNS integrity be safeguarded if responsibility for number insertion in the DNS lies with the customer? §ISSUE 18: How should validation of subscriber identity, data, and NAPTRs (service-specific records) occur?

16. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc16 Administration Issues (cont.) §ISSUE 19: How can number/name hijacking/fraud be prevented? §ISSUE 20: How will number changes/number churn be handled? §ISSUE 21: How will ceased numbers be notified/recovered? §ISSUE 22: Could prepaid mobile numbers, or pagers, be inserted? If so, how will ownership, e.g., of mobile terminals, be validated?

17. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc17 Administration Issues (cont.) §ISSUE 23: How will changes/ownership/loss/ theft/cease issues be addressed? Who has these responsibilities? §ISSUE 24: Geographic numbers would lose location information, and will begin to look more like personal numbers. §ISSUE 25: Impact on number plans/number administration? Possible new requirements? §ISSUE 26: Are additional controls required where numbers are shared?

18. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc18 Administration Issues (cont.) §ISSUE 27: Should/could requirements on carriers/third parties be enforced? §ISSUE 28: There are issues concerning technical/operational matters (such as testing, performance/loading characteristics, dependencies on infrastructure characteristics, etc.) that are related to ENUM administration. There are matters are related to machine types, architectures, reliability, etc., as additional technical issues. §ISSUE 30: How is RIPE-NCC to know who is authoritative when claiming so (to RIPE-NCC)?

19. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc19 Administration Issues (cont.) §ISSUE 31: When (international) E.164 addresses are used as routing numbers, how can they be authenticated? §ISSUE 32: What ENUM administrative issues apply to E.164 numbering for global services as defined by ITU-T Recommendations? §ISSUE 33: Other comments and discussions, limited by lack of time included: l more concerns about integrated numbering plans l subdelegation issues, and l opinions that technical issues totally within DNS, or totally within E.164 numbering resource administration, are out of scope.

20. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc20 Administration Issues (cont.) §ISSUE 34: How can competition for ENUM services, and for service provision, be promoted in different market segments and by different service providers?

21. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc21 ITU-T Study Group 2 Meeting 23 January - 2 February 2001 §Supplement to provide guidance to Member States on Implementation Issues out of 1/17 Workshop l Very Rough First Draft Developed §Circular Letter to Promote ENUM Awareness §E164.arpa still an open issue l out of scope for SG2 l revolt led by France; all of Europe sympathetic

22. 12 February 2001S.D. Lind - SG A ENUM Ad Hoc22 ITU ENUM Resource §www.itu.int/infocom/enum/workshopjan01/ index.html