1 / 22

Update on ITU-T ENUM Activities

Update on ITU-T ENUM Activities. Steven D. Lind AT&T SG-A ENUM - Ad Hoc February 12, 2001. Workshops and Meetings. IP-Telecom Interworking Workshop on Numbering, Naming, Addressing and Routing (25-27 January 2000) ITU-T Study Group 2 Meetings 7-17 March 2000

michelerogers
Download Presentation

Update on ITU-T ENUM Activities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. 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 S.D. Lind - SG A ENUM Ad Hoc

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

  5. Working Party 1/2 Meeting19-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 S.D. Lind - SG A ENUM Ad Hoc

  6. 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. • Each member state would inform the TSB of the name server that would house the country/service specific information. • The information to be put into DNS at the country code level would come only from the TSB. S.D. Lind - SG A ENUM Ad Hoc

  7. ITU ENUM Workshop17 January 2001 • Objective: Discuss Administrative Issues Related to the Operational Deployment of the ENUM Protocol • Tutorials presented on: • Overview of the Domain Name System • ENUM Technical Issues • ENUM • ENUM Administration - Some Numbering Perspectives S.D. Lind - SG A ENUM Ad Hoc

  8. 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. • Building and Maintaining integrity of E.164 • How should Tier 1 Registries be selected? S.D. Lind - SG A ENUM Ad Hoc

  9. 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: • How to determine the most appropriate arrangement? • Who runs national Registries? • An agreed process needs to be developed between participating Member States [of an Integrated Numbering Plan]. S.D. Lind - SG A ENUM Ad Hoc

  10. 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: • Assignees of Network Codes need to be formally made aware of their obligations with respect to ENUM. • Some ITU-T Recommendations related to E.164 Network Codes may require review/amendment/revision. S.D. Lind - SG A ENUM Ad Hoc

  11. 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): • Assignees of E.164 resources for Groups of Countries need to be formally made aware of their obligations with respect to ENUM. • Some ITU-T Recommendations related to E.164 resources for Groups of Countries may require review/amendment/revision. S.D. Lind - SG A ENUM Ad Hoc

  12. 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: • 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. S.D. Lind - SG A ENUM Ad Hoc

  13. Administration Issues (cont.) • ISSUE 9: This item was discussed when aspects of Service Providers were considered with respect to ENUM: • 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? • Differences across Administrations? • Intellectual Property Rights? S.D. Lind - SG A ENUM Ad Hoc

  14. 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? S.D. Lind - SG A ENUM Ad Hoc

  15. Administration Issues (cont.) • ISSUE 16: Concerning some ENUM administration issues related to the Service Registrar models: • 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? S.D. Lind - SG A ENUM Ad Hoc

  16. 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? S.D. Lind - SG A ENUM Ad Hoc

  17. 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? S.D. Lind - SG A ENUM Ad Hoc

  18. 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)? S.D. Lind - SG A ENUM Ad Hoc

  19. 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: • more concerns about integrated numbering plans • subdelegation issues, and • opinions that technical issues totally within DNS, or totally within E.164 numbering resource administration, are out of scope. S.D. Lind - SG A ENUM Ad Hoc

  20. 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? S.D. Lind - SG A ENUM Ad Hoc

  21. 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 • Very Rough First Draft Developed • Circular Letter to Promote ENUM Awareness • E164.arpa still an open issue • out of scope for SG2 • revolt led by France; all of Europe sympathetic S.D. Lind - SG A ENUM Ad Hoc

  22. ITU ENUM Resource • www.itu.int/infocom/enum/workshopjan01/index.html S.D. Lind - SG A ENUM Ad Hoc

More Related