ENF/ERO ENUM Convergence Workshop Tony Holmes Chairman ETSI SPAN11 NAR BTexact Technologies Numbering Addressing & Routeing 9-10 January 2002 Standards Developments

© British Telecommunications plc The Starting Point Questions ENUM looked to answer How do you find services on the Internet if you only have a telephone number [E.164]? How to enable new IP services while creating new competitive markets and protect consumer choice,etc? How can consumers and carriers have equal access to these new opportunities? How do we create a trusted TN based resource for information about those services? How do you make this simple, easy to use, without “reinventing the wheel”?

© British Telecommunications plc Some early answers from the IETF Use the DNS …i t works... It’s global...It scales..etc. Telephone Number in = URI out RFC2916 was developed by the IETF to define the use of DNS resource records to find optional : addresses Voice over IP SIP / H.323 servers Voice Mail servers Fax Machines New and yet undefined services !

© British Telecommunications plc Some technical realisation aspects Hierarchical registry operations and name servers will need to be generally deployed at the international, national and sub-national levels To support geographically dispersed national resources, the ENUM DNS root zone arpa.tld requires a DNS backbone dispersed around the world Main ENUM name servers (e.g., root zone & CC) should be capable of sustaining loads probably comparable to that carried by current root name servers

© British Telecommunications plc What is still at issue? Not the technical underpinnings No substantial argument with the technology identified in RFC 2916 At issue are the implementation details These are now being addressed by - IETF/ITU - various regions/countries

© British Telecommunications plc Some agreements between IETF/ITU Agreement on delegation model that completely follows the ITU-T E.164 plan for inclusion in the agreed zone E164. geographic zones controlled by appropriate Member State. ITU will insure that Member States have authorized the inclusion of their Country Code in ENUM DNS zone ITU will coordinate with the agreed Root Administrator

© British Telecommunications plc Background to the ITU & ETSI documents SG2 Supp ETSI initial SG2 Rap US SG-A Sweden France UK Nethl’ds ETSI SPAN SG2 Genv AdRec ETSI SPAN SG2 Genv ‘Timing has dictated’ Some examples of national activities

© British Telecommunications plc ITU-T Supplement Supplements are: purely informative not an integral part of any Recommendation they do not imply agreement

© British Telecommunications plc ITU-T Supplement on operational and administrative issues associated with ENUM Provides an overview of concepts Describes issues that need to be addressed by Administrations as they consider the inclusion of numbers within the DNS which are under their jurisdiction Also covers issues that need to be addressed by stakeholders of shared country codes e.g. codes for Networks and Global Services :

© British Telecommunications plc ITU Draft Recommendation Principles & Procedures for Administration of E.164 CCs ITU has responsibility for Administrative control of CC’s Recommendation defines principles & procedures for assignee to register a CC domain at the ENUM root level in the DNS Recognises Subsequent levels are national matters (guidance on this will be in the ITU Supplement) Doesn’t cover technical operation of the DNS

© British Telecommunications plc ETSI Technical Specification Aim: To provide basic set of principles that should be adhered to in order to maximise potential benefits from publicly available ENUM implementations within Europe “Efforts at drawing together a a co-ordinated approach should not only result in a firm foundation for ENUM activities within the European environment but should also assist in enhancing the competitive communications environment” The importance of gaining the support or all relevant parties was recognised as a prime requirement

© British Telecommunications plc Some emerging principles within Europe from ETSI E.164 integrity must be maintained Compliance with Data Protection Directives Adherence to ITU Recommendations and IETF Specifications Compliance with National Regulatory requirements Must facilitate a competitive environment Must be user ‘Opt in’ Existing network functions must not be compromised e.g. Number Portability, Carrier Selection All provide good safeguards

© British Telecommunications plc Major Issues of concern Provisioning based on false information by users Authentication and validation requirements Abuse of data stored Regulatory requirements Alternative ENUM implementations ….and more! These will be considered tomorrow!

© British Telecommunications plc What still needs to be done? Administrations must be encouraged to actively consider national implementation aspects The ETSI Framework document needs to be completed and formally agreed Issues surrounding the choice of gTLD must be resolved URGENTLY! All effort must be put into completion of the ITU studies to facilitate the insertion of Country Codes within the DNS A better understanding of ENUM needs to be promulgated through the ONP Experts Committee Europe MUST be proactive