Making a Standard Work ENUM Commercialization and Experiences

Making a Standard Work - ENUM Commercialization and Experiences Presented to: ENUM Summit 2005 Presented by: Robert W. Schafer & Ronan Lupton Date: 27 th June 2005 PT 0000. 00/00/04

House Keeping – Chatham Rule & Q&A This workshop will be held under The Chatham House Rule which will mean that participants are free to use the information received following the meeting, but neither the identity nor the affiliation of the audience speaker(s) may be revealed. It will allow people to speak as individuals, and to express views that may not be those of their organisations, and therefore it encourages free discussion which we believe will be of benefit to all attending. We plan to leave adequate time for questions and answers at the end, Please note: There is no such thing as a stupid question! 3 02/10/2020

Deliverables • • • Achieving Delegation The dynamics of ENUM Numbering issues NAPTR – More than just access to ‘old world’ telephone numbers Moving from technology trial to operational reality – Defining Vo. IP – What is the regulatory debate about? – Getting the regulatory focus right – Remarks • See it live! • Concluding remarks 4 02/10/2020

ENUM Hierarchy, Delegation and Registrars 5 02/10/2020

ENUM Hierarchy, Delegation and Registrars The ENUM system (a. k. a. , “golden tree”) has several levels commonly referred to as Tiers The reference to “golden” for the tree structure is in place in order to ensure against erroneous operation and data or information flow As DNS technology is proven to be extremely scalable, service providers, enterprises and registrars may also act as private solution providers within the ENUM environment The following slide give a visible display of the logical hierarchies as unfolding in many countries today 6 02/10/2020

The ENUM Tiers • Tier 0 – Top Level Domain: e 164. arpa • Tier 1 – Country Delegation (e. g. , Ireland/+353 = 3. 5. 3. e 164. arpa) • Tier 2 – DNS Name Servers containing NAPTR records 7 02/10/2020

Delegation Overview – Country to Regional Registry • Delegation requests are sent to Regional Internet Registry (RIR) – RIRs (ARIN / RIPE NCC / APNIC/LACNIC/Afri. NIC) • RIR acknowledges request • RIR announces request – To the public – On website – To the ITU TSB • RIR tracks comments during a 60 working day period • Pending ITU-T approval, delegation may proceed. 8 02/10/2020

Achieving Delegation – Finding Tier 0 • National Government or ministries would generally approach the ITUTelecommunications Standardization Bureau along with their regional Internet Registries in order to apply for a trial or permanent. e 164. arpa delegation. ITU - TSB ARIN / RIPE NCC / APNIC/LACNIC/Afri. NIC Country Registry CC. e 164. arpa USA/NANP CC 1 LLC Tier 1 9 02/10/2020 IETF/IAB

Trial Hierarchy – Developing Stakeholders • Getting through a delegation and establishing a trial for ENUM hierarchies and players would appear as follows: Tier 0 Tier 1 Country Registry e 164. arpa USA/NANP CC 1 LLC Tier 2 Registrar X Registrar Y Registrar Z • So where’s the competition? Where’s the money? Where’s the consumer? 10 02/10/2020

Operational Hierarchy • It is perceived that the fully operational ENUM hierarchy will look like this: Country Registry e 164. arpa Tier 0 Tier 1 Competition space USA/NANP CC 1 LLC Tier 1 Tier 2 Registrar X Small ISP Registrar Y Medium ASP ENUM Registrants (End Users/Customers) 11 02/10/2020 Registrar Z Large Enterprise

Competition Space – Zero Sum to Positive Sum? • Competition is likely exist between the following ENUM entities: – Tier 2 registrars or Telecom Service Providers (TSPs) – Small Internet Service Providers – Application Service Providers (ASPs) – Medium to large enterprises (Supply Chain Partners) – Secure Authentication providers / Enterprise Security Providers 12 02/10/2020

How will this work? – Competitive Advantage Differentiation (Non-Price Value) Competitive Advantage Lower Cost 13 02/10/2020

General Stakeholders – ITU and RIRs – National Governments – Regulatory Authorities – Tier 1 Registry – Tier 2 Registrars – ISPs – ASPs – Consumers – Large Enterprises – Equipment Vendors – Security Agencies 14 02/10/2020

The Dynamics of ENUM 15 02/10/2020

Problem: Address Complexity +1 214 786 4491 http: www. jonathangreene. localisp. net email: jonathan. greene@localisp. net +1 214 891 0495 sip: jonathan. greene@mcisip. net +1 214 890 6143 im: jonathan. greene@messaging. net 16 02/10/2020

Problem: IP Addresses Not Dialable Over a billion wireless and wireline customer devices with keypads http: www. jonathangreene. localisp. net email: jonathan. greene@localisp. net sip: jonathan. greene@mcisip. net im: jonathan. greene@messaging. net 17 02/10/2020

ENUM Simplified • Take a phone number +353 -1 -506 -9888 • Turn it into a domain 8. 8. 8. 9. 6. 0. 5. 1. 3. 5. 3. e 164. arpa • Ask the DNS • Return a list of URI’s mailto: robert. schafer@mci. com sip: robert. schafer@mci. com 18 02/10/2020

Basic ENUM DNS Architecture Tier 0 is the Top Level Domain, e 164. arpa The “Global” ENUM Tier TIER 0 Each Country Code will have its own Tier 1 registry TIER 1 The “National” ENUM Tier TIER 2 … TIER 2 Specific information linked to each telephone number will be stored by service providers at the Tier 2 level The “Competitive” ENUM Tier 19 02/10/2020

Privacy and Security • Unlike PSTN translations, The DNS is PUBLIC SPACE! • Solution is proxy addressing for ENUM records • The person being contacted should decide: – to whom they wish to communicate – how they wish to communicate – when they wish to communicate • MCI customer portal and enhanced network capabilities are ideally suited to work with ENUM • EPP provides a secure provisioning mechanism 20 02/10/2020

Provisioning • Utilisation of EPP – Extensible Provisioning Protocol will assist registrars retain secure and efficient interworking with Tier 1 and End-Users of ENUM • EPP supports the retrieval, creation, deletion and renewal of XML data elements in the / for the NAPTR records • The extensions to the EPP for ENUM consist of XML data for E. 164 domain names and for the NAPTR fields: – Order – Preference – Flags – Service – Regular Expression – Replacement 21 02/10/2020

ENUM Enabled Applications ENUM DNS Internet Available Customer Profile Applications Translation to Internet Address(es) +1 -877 -925 -6987 mail: \d. jones@joneselectronicsinc. com fax: \davidjones@joneselectronicsinc. com im: \drjones@joneselectronicsinc. com +1 -972 -7295798 D N S +1 -214 -891 -0495 22 02/10/2020 +1 -202 -924 -9597 http: \www. joneselectronicsinc. com

ENUM Value - Bridging Vo. IP Islands ENUM DNS abc. globalip. com xyz. sipnet. com SIP server +1 214 891 0495 Session sip: axelm@globalip. com 23 02/10/2020 sip: 1243679343010@xyz. sipnet. com

ENUM delegations approved China (86) Austria (43) Romania (40) Ascension (247) Poland (48) Australia (61) 24 02/10/2020 Finland (358) Czech Republic (420) UAE (971) Switzerland (41) Sweden (46) Netherlands (31) France (33) Brazil (55) Norway (47) Taiwan (886) Germany (49) UK (44) Iceland (354) Korea (82) Liechtenstein (423) St Helena (290) Singapore (65) Ireland (353) Japan (82) Armenia(3 74) Hungary (36) Slovak Republic (421)

UK ENUM Trial • MCI joined Country Code 44 UK ENUM trial in 2003 • Trial ended late 2003 and trial report is now in the public domain • MCI participated as an application service provider, using existing MCI telephone numbers in Country Code 44 to demonstrate ENUM support for IP connectivity independent of the PSTN • Trial results collected provide information and experiences on how to implement ENUM in the commercial phase 25 02/10/2020

UK ENUM Trial Application-SIP Service Interworking Calling Party Called Party +441223381002 customeraddress SIP Server Service Provider X Service Provider Y Proxy Server sip: mciukenum 2@nvta. globalip. com Internet 26 02/10/2020 ENUM DNS

Ireland ENUM Trial • MCI joined Irish ENUM Trial Group for Country Code 353 in 2004. This trial is just now concluding • MCI participated as a Tier 2 Provider using existing Country Code 353 MCI telephone numbers to explore provisioning and interface capabilities with the Irish Tier 1 registry • The Irish trial has now moved to construct a Policy Advisory Board in order to move the trial to production phase 27 02/10/2020

What about the U. S. ? U. S. Government supports ENUM! • CC 1 ENUM Limited Liability Company § CC 1 ENUM LLC formed last year § RFP for Tier 1 Registry Management § Karen Mulberry-MCI is Chairman § Technical Advisory Committee § Website www. enumllc. com • U. S. ENUM Forum § Forum developing U. S. requirements § Robert Schafer-MCI is Administrator § Website www. enumf. org 28 02/10/2020

MCI and ENUM • ENUM provides a simple way around existing Internet address complexity using an address customers are already familiar with – telephone numbers • MCI’s global network is well positioned to implement ENUM with existing and new services. ENUM nicely complements MCI’s robust network management and security platform • ENUM will support customer communications on a global scale while increasing the degree of control they have over how and when, and to whom they communicate 29 02/10/2020

What will ENUM do? • ENUM can translate a familiar telephone number into any Internet address, working behind the scenes to simplify customer communications • ENUM will support new customer applications, including find me/follow me, simple integrated conferencing, and directory services • ENUM gives customers WORLDWIDE address translation capability, while safeguarding specific customer addresses from widespread exposure when combined with MCI’s global network 30 02/10/2020

Numbering Issues 31 02/10/2020

Numbering Some common issues: 1. Numbering is viewed as a scarce national resource 2. Users dial E. 164 numbers 3. Use of corporate dial plans 4. Numbering can be allocated based on population demographics 5. Numbering rules can detract from mobility 6. Need for and fear of nomadic numbers 32 02/10/2020

Fostering Good Numbering Policy for ENUM While numbering is important to nations unnecessary regulation can lead to stymied investment opportunities and lack of willingness to deploy new innovative services. Good numbering policies for ENUM: 1. Regulators should allow ubiquitous access for all (national) publicly accessible numbers 2. Pay heed to existing legal requirements including emergency service access 3. Allow competition to develop by only regulating where regulation is needed e. g. introduction of new nomadic number ranges (UK, Ireland, Germany, Austria) 4. Preserving the interests of users while not impeding innovation and potential future markets 33 02/10/2020

NAPTR – More than just voice communication 34 02/10/2020

NAPTR - Naming Authority Pointer Record NAPTR – Naming Authority Pointer Record • What is a NAPTR? – A NAPTR is the logical “key” or service resource record residing with the Tier 2 registrar • Where are NAPTRs located? – The NAPTR is found via the DNS hierarchy, Tier 2 registry • What is the NAPTR function? – The NAPTR is the logical record that represents End User/Customer routing or desired choice of communications 35 02/10/2020

NAPTR – Looks like what? **Recommend use of proxies for privacy reasons ** 36 02/10/2020

Common mistakes • ENUM and NAPTRs are far more powerful and operate over and above the simple telephone network addressing we are all accustomed to in the Telephony world (See slide 39). Now we have control to nominate methods of communication • If Plain Old Telephone numbers ever become obsolete or complementary the NAPTR would provide the required “glue” for seamless convergence 37 02/10/2020

Other services powered by ENUM/NAPTR • NAPTRs can point to various other service types such as: – SIP – Presence – Email – MMS – SMS – EMS – Fax – H. 323 – Conferencing [Integrated] 38 02/10/2020

Moving from technology trial to operational reality? 39 02/10/2020

1. Making a trial a functional reality Problem 1 - Competition • Tier 1 Registry selection, only one organisation can run the Tier 1 registry thus ensuring the registry/registrar model, in a given nation state • Tier 2 Registrars interact with and provide services to consumers, deciding on items such as: – Service levels – Service functionality – Pricing – Efficiency – Reach – Segmentation of Market – Target market – Position of Registrar (Mass Market, Enterprise, Wholesale) 40 02/10/2020

2. Making a trial a functional reality Problem 2 – Standardisation • Maintaining standard public ENUM implementations in order to facilitate public/national markets • Maintaining requirements to foster interoperable “Private ENUM” so that communications can co-exist outside closed enterprises with private dial plans or secure communications platforms/arrangements • Thus the selection of the. e 164. arpa for telephone numbers. (ARPA Address and Routing Parameters Area) • General list of issues can be found in IETF RFCs 41 02/10/2020

3. Making a trial a functional reality Problem 3 – Alternative Dial Plans • Users rarely dial normal dial plans on corporate networks • Not all numbers dialed are E. 164 numbers • Numbering policies are divergent based on the country of operation • Natural domestic (mass market) consumers are used to dialing plans • Dial plan information can/could be easily resolved using ENUM technology 42 02/10/2020

4. Making a trial a functional reality Problem 4 – Registry / Registrar logic • A Registry runs the DNS server for a specific name space • A Registrar facilitates customers who want to have things registered but not directly with the registry • Registry and Registrar operations may co-exist at Tier 2 level • Registrars update, change or cancel customer data on the Registry and would be responsible for billing and other service issues • Registries would interact with the DNS under each Country Code, in a country according to national/local policy 43 02/10/2020

5. Making a trial a functional reality Problem 5 – Services Authentication and Provision Customers / End-Users may choose service from a multitude of Tier 2 / service providers for: – email – Sip/Vo. IP – Telephony – Web homepage – Many more … ENUM serves to announce the location of the service provided to the consumer regardless of who the underlying service provider actually is National legislation may need amendment in order to foster greater electronically enabled sign-up and authentication in a converging world, while remaining compliant with Data Protection and Privacy rules 44 02/10/2020

ENUM Clearly is: • Not about Carrier Selection or Carrier Pre-Selection – It is the selection/nomination of services within a given service space • Not about telco bypass or substitution – It is a viable and efficient alternative to circuit switched technology • Not about Number Portability – It is a more efficient and broader IP address mechanism • Not about changing national numbering plans – It is conformant with the ITU-T E. 164 standard – It is conformant with national numbering administration and policies It fully respects rights and prerogatives of national states and jurisdictions 45 02/10/2020

Regulation: How Is Vo. IP Defined by Regulators? 46 02/10/2020

There is No Universally Accepted Definition of Vo. IP • ITU Study Group 2 Has Developed Consensus on Key Concept: – IP Telephony: IP is an acronym for Internet Protocol. It is a communications protocol developed to support a packet switched network. The protocol has been developed by the IETF. IP telephony is the exchange of information primarily in the form of speech that utilizes a mechanism known as Internet Protocol. Internet telephony and Vo. IP are specific subsets of IP telephony. – Internet Telephony: The combination of the term ‘Internet’ with the term telephony is seen as inappropriate. The Internet offers many capabilities to users including the ability to carry bidirectional speech in real-time or near real time. We consider this to be an intrinsic capability of the Internet and not a telecommunications service. – Voice over IP (Vo. IP) – IP telephony in which the principal transmission network or networks are private managed, IP-based networks of any type, such as Voice-over-frame relay; voice over cable; voice-over-DSL, etc. • WTO Initiatives – “Devil in the Details” 47 02/10/2020

• OECD Working Party on Telecom & Information Services Policies - “Trends in IP Technology: Their Impact on the Traditional Telephony Carrier World” (March 2002): Key Conclusions: – “Given the sheer size of the traditional telephony infrastructures it is reasonable to anticipate that integrated IP-based voice applications and traditional telephony may co-exist for many years…” – “Vo. IP will be sold on feature functionality and the value of applications within which it has been integrated rather than purely on the traditional view of ‘cost per minute’ to the end user. . . …IP-based applications will foster new rather than replacement communications…” 48 02/10/2020

• European Commission Policy – 1998 EC Notice concluded that Internet voice services do not constitute voice telephony UNLESS: – They are offered commercially and separately to the public as voice services; – They are offered to and from PSTN termination points; and – They are offered in real time at the same level of speech quality and reliability as is offered by the PSTN. – January 2001 communication reaffirmed the 1998 position observing, however, that the quality of IP telephony over a single network has improved. – Vo. IP is not defined by new EC Communications Market Definition Recommendation issued in February 2003. 49 02/10/2020

ENUM is far more than Vo. IP however, Voice is component of ENUM! Competition is the most effective form of regulation in this developing area 50 02/10/2020

ENUM Applications and Network at Work Demonstration in collaboration with AG Projects Mr. Adrian Georgescu, Founder and CEO AG Projects PT 0000. 00/00/04

ENUM applications and clients • An application that uses ENUM lookups to perform routing logic is an ENUM application • An ENUM client is part of the ENUM application and translated DNS requests into information understood by the application • An ENUM resolver is a standard or modified DNS resolver that sits within the operating system of the device where the ENUM application runs 52 02/10/2020

ENUM components 53 02/10/2020

How to use ENUM Is simple: • Register a number in official e 164. arpa tree • Populate the zone with NAPTR records • Lookup the records Example used for the showcase: • • • 54 Register a +87810 number (with sip 2 sip. info) Map SIP address to the number (create also the SIP address) Map email address to the number Map a geo location to the number (web site or route planner) Lookup the records 02/10/2020

ENUM tools for this showcase • ENUM Tier 2 interface (http: //managed-dns. info) • ENUM client on Mac OSX (courtesy of John Cundall/Roke Manor Research) • Dig and nslookup utilities (standard DNS utilities) • ENUM enabled web browser (Firefox plug-in available from http: //Falb. at) • ENUM enabled SIP service (http: //Sip 2 SIP. info) • PSTN termination service (http: //MCI. com) Lets see ENUM at work: Point you browser to http: //mci. ag-projects. com 55 02/10/2020

Concluding remarks • ENUM is a standard that should be embraced – It’s a no brainer • Global standards should ensure efficient roll-out and operations • Regulation should remain no or very light touch • Liberal numbering policy is essential • National competitiveness and regional information society agenda’s will assist the rollout of ENUM • Further questions and comments can be made to presenters at: – Robert. schafer@mci. com; Ronan. lupton@mci. com; ag@agprojects. com 56 02/10/2020

Q&A Session 57 02/10/2020

References • 1 "Using E. 164 numbers with the Session Initiation Protocol (SIP)" by J. Peterson et al. Internet Draft, IETF, September 2003. Work in progress. • 2 RFC 3761: "The E. 164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)" by P. Falstrom and M. Mealing. IETF, April 2005. • 3 RFC 3403: "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database" by M. Mealing. IETF, October 2002. • 4 RFC 2915: "The Naming Authority Pointer (NAPTR) DNS Resource Record" by M. Mealing. IETF, September 2000. • 5 RFC 3725: " Using E. 164 numbers with the Session Initiation Protocol (SIP)" by J. Peterson et al. IETF, June 2004. • 6 RFC 2782: "A DNS RR for specifying the location of services (DNS SRV)" by A. Gulbrandsen et al. IETF, February 2000. • 7 "IANA Registration for ENUM services email, fax, mms, ems and sms" by R. Brandner et al. Internet Draft, IETF, June 2004. Work in progress. • 8 ESP-SOAP Connector White Paper for the ENUM-Trial project of T-Systems. September 2003, Berlin, Germany. http: //www. enum-trial. de/ • 9 "E. 164 Number Mapping for the Extensible Provisioning Protocol" by S. Hollenbeck. Internet Draft, IETF, August 2004. RFC 4114 June 2005. • 10 "Privacy and Security Considerations in ENUM" by R. Shockey et al. Internet Draft, July 2003. work in progress. • 11 RFC 2916 : “E. 164 number and DNS” by Peter Falstrom, Cisco Systems/IETF, September 2000. • 12 RFC 4002: IANA Registration for Enumservice 'web' and 'ft‘, R. Bradner, L. Conroy, R. Stastny, Internet memo. February 2005 • 13 “Numbering for Vo. IP and other IP Communications” R. Stastny Oe. FEG, October 2003 58 02/10/2020