Document: Quick Scan ENUM Client: Directoraat-Generaal Telecommunicatie en Post (DGTP) Contact: Thomas de Haan Authors: Sander Paul van Tongeren / Ed Achterberg Telephone: 030-6349650 Mobile: 06-21285217 (Sander) / 06-53530320 (Ed) Project: E201.009 Date: 30-04-2001 © Electronic Paper / 201.009 1/35 Contents 1. Introduction.......................................................................................................... 4 2. Summary .............................................................................................................. 5 3. ENUM general ...................................................................................................... 6 4. ENUM-Players ...................................................................................................... 8 4.1 Commercial players ...................................................................................... 8 4.1.1 VeriSign GRS and Telcordia Technologies ..................................... 10 4.1.2 NetNumber...................................................................................... 11 4.1.3 Neustar ........................................................................................... 12 4.2 Non-profit .................................................................................................... 12 4.2.1 Internet Engineering Task Force (IETF) .......................................... 15 4.2.2 ITU-T Study Group 2....................................................................... 15 4.2.3 Internet Architecture Board (IAB) .................................................... 15 4.2.4 The Internet Engineering Steering Group (IESG)............................ 16 4.2.5 Internet Society (ISOC) ................................................................... 16 4.2.6 Internet Corp. for Assigned Names and Numbers (ICANN)............. 16 4.2.7 TIPHON .......................................................................................... 16 4.2.8 Réseaux IP Européens Network Coordination Centre (RIPE NCC). 17 4.3 Government ................................................................................................ 18 4.4 End Users ................................................................................................... 19 5. Implementation ENUM Standard ...................................................................... 21 5.1 Implementation models of ENUM................................................................ 21 5.2 EP5-model .................................................................................................. 22 5.3 Risks and issues of concern with ENUM..................................................... 24 5.3.1 Telephone numbers ........................................................................ 24 5.3.2 Content of the ENUM database....................................................... 25 5.3.3 Public need ..................................................................................... 25 5.3.4 Competition..................................................................................... 25 5.3.5 Price control on registration and usage of ENUM............................ 25 5.3.6 Consumer protection (Slamming and hijacking) .............................. 25 5.3.7 Security........................................................................................... 26 5.3.8 Implementation of ENUM standard e164.arpa................................. 26 6. Government ....................................................................................................... 27 6.1 Key questions on official ENUM.................................................................. 27 6.1.1 Pro’s and con’s of an officially endorsed ENUM .............................. 27 6.1.2 Are the pro’s hard enough to justify an official ENUM? ................... 28 6.1.3 Match ENUM-policy with self-regulated Internet?............................ 28 6.1.4 Could an official ENUM be seen as intervention?............................ 28 6.1.5 Can both official and private ENUM systems co-exist? ................... 29 6.1.6 Can regulators prevent alternative private ENUM systems?............ 29 6.1.7 What happens if ENUM is publicly endorsed and official?............... 30 6.1.8 What happens if we do nothing? ..................................................... 30 6.1.9 How will an endorsement change the market environment?............ 30 6.1.10 Are there other beneficiaries? ......................................................... 30 © Electronic Paper / 201.009 2/35 6.1.11 Will it frustrate private ENUM implementations?.............................. 30 6.1.12 The right ENUM-structure? ............................................................. 30 6.1.13 Can we still change it in e.g. 5 years? ............................................. 30 6.2 ENUM specific questions ............................................................................ 31 6.2.1 Single root versus multiple competing roots? .................................. 31 6.2.2 Service level alternative ENUM-like solutions?................................ 31 6.2.3 Intellectual Property Rights (IPR’s) within ENUM ............................ 31 6.2.4 How would ITU IPR policy serve? ................................................... 31 6.3 ENUM and related technologies/services.................................................... 32 6.3.1 Other developed or implemented initiatives/concepts?.................... 32 6.3.2 Relation between ENUM and these initiatives and are they competing? ..................................................................................... 33 6.3.3 What is the relation between ENUM and 3GPP? ............................ 33 6.3.4 How will private DNS environment affect ENUM? ........................... 34 6.3.5 Relation ENUM and telco’s.............................................................. 34 6.4 Related issues ............................................................................................ 34 6.4.1 Authorization and authentication problems...................................... 34 6.4.2 Interest IETF/IAB to ask ITU to delegate the ENUM data?.............. 34 6.4.3 What is the ‘legal standing’ of IETF papers? ................................... 34 6.4.4 Management of the DNS server running the TLD and could there be a more distributed management between USA and ROW?............. 34 7. Terminology ....................................................................................................... 35 © Electronic Paper / 201.009 3/35 1. Introduction EP1 has been given the assignment by the Government (DGTP) to do a quick scan on how the Government may collaborate with the implementation of ENUM2 in The Netherlands. When using ENUM, EP refers to that stated in IETF’s3 technical specification RFC 29164, which was produced by a working group of the same name. EP will focus on real value of ENUM and the generated potential benefits for all relevant parties. In chapter 4 we defined the players (commercial, non-profit, government and end users) and their interests. In chapter 5 we will describe four existing ENUM-models and the major issues of concern are highlighted. We also introduce an rough draft of a alternative model (EP5). In chapter 6 we will answers the questions raised by DGTP. 1 Electronic Paper 2 Telephone Number Mapping 3 Internet Engineering Task Force: http://www.ietf.org 4 http://www.ietf.org/rfc/rfc2916.txt © Electronic Paper / 201.009 4/35 Summary ENUM is a complex and all-embracing issue. In this quick scan we have listed the players and tried to shed some light on important issues. We are unfortunately not able to provide DGTP with a final and a clear set of recommendations. We suggest to have a workshop together with DGTP and EP to complete the questions in more detail. This workshop can be used as a starting point for a consultation. The discussion about the actual implementation of ENUM is still going on. Given the different roles of the players in each model, it will take some time to come to an world- wide agreed standard model. The competitive position of Internet Service Providers (ISP) and Telecommunication Service Providers (TPS) will drive the needed government attention. Given the lack of firm commitments and clear directions, any consultation will also need to form a ‘public’ opinion. If the discussion on a ENUM standard will take too long, a small chance exists that other initiative will launch their services. Already some services are launched to provide easy access to (Mobile) internet resource from a (mobile) telephone handset. These initiative could set the scene and potentially one of them could become a de- facto standard. We recommend DGTP to wait and review the situation after more clarity is available on the ENUM standard within the ITU, IETF and the role of the TSP and ESP. In the mean time a (informal) consultation could be held to get feedback from the market. If E164 numbers are going to be used, some interference of DGTP is needed, as this might have impact on the existing number plan. © Electronic Paper / 201.009 5/35 3. ENUM general What Is ENUM?5 ENUM is a protocol and a database that maps telephone numbers to Internet domain names. The domain name that corresponds to the telephone number will be written in reverse order and is included under a specially allocated second-level domain. ENUM, an idea of Patrik Falstrom6, allows a phone number to also serve as the basis for someone's e-mail address. The arrangement would effectively