ENUM Status

1
ENUM Status

• ENUM Workshop
• Dublin, Ireland, June 3rd, 2004
• Richard STASTNY
• ÖFEG, Postbox 147, 1103-Vienna
• tel[phone]mailtorichard.stastny_at_oefeg.
  at

The opinions expressed here may or may not be
that of my company
2
Content

• ENUM International
• ETSI ENUM Plugtest and Technical Specifications
• ENUM in Austria

3
ENUM
Contact (not Content) is King
Douglas Rushkoff
4
ENUM

• ENUM perfectly matches phone numbers to internet
  domain names
• Considered a key enabler for Convergence
• Whatever that is..
• The potential for using TNs to address multiple
  applications other than voice
• Mobility and Presence
• Video
• Creates service interoperability across domain
  boundaries
• ENUM accelerates the shift from location to
  individual based communications addressing

5
Stating the obvious..
How do you route a VoIP call end to end on IP if
all you have is a Telephone Number?

• Accelerators to the adoption of VoIP services
• Proliferation of broadband access data networks
• Regulatory Tolerance (the light touch)
• Cost savings delivered not just access avoidance
• Increased competition, including new market
  entrants
• A better voice service than TDM

6
Why E.164 Numbers ?

• Addressing is the most important asset in ANY
  network service!
• People know how to use Telephone Numbers
• Telephone numbering system (E.164 is stable
  global and reliable)
• Billions of devices only use numeric key pads,
  especially wireless
• In the case of Local Number Portability (FCC
  First Order and Report), MCI has stated that,
  based on a nationwide Gallup survey, 83 percent
  of business customers and 80 percent of
  residential customers would be unlikely to change
  service providers if they had to change their
  telephone numbers.
• ENUM is perhaps the ultimate in number
  portability
• VoIP and new IP Services (Instant Messaging,
  Video) can use Real Telephone Numbers!
• URIs like sipuser_at_domain have advantages and
  disadvantages
• Biggest problem they cannot be dialed on the PSTN
• In fact they cannot be dialed at all
• URIs and telephone numbers will co-exist for the
  indefinite future

7
(Very short) ENUM History

• 1999 IETF ENUM WG formed
• 2000 IETF ENUM WG RFC2916
• 2001 Various Workshops (ITU-T, Europe, US,
  Asia, )
• 2002 ITU -T Interim Procedures (IAB, RIPE-NCC)
  ITU -T generic TLD Investigation
  ETSI TS 102 051 "ENUM Administration in Europe"
• 2003 ETSI TS 102 172 "Minimum Requirements for
  Interoperability of European ENUM
  Trials" IETF new ENUM revision, IANA
  registered enumservices ITU-T final
  procedures ENUM domain
• 2004 ETSI ENUM Workshop (Feb 2004) and Plugtest
  ( 2004)
• IETF New RFC 3761
• Enumservices registration
• 1st Commercialization in Austria

8
ENUM Delegations
Delegations in e164.arpa as of June 1st, 2004

• 31 Netherlands
• 33 France
• 353 Ireland
• 358 Finland
• 36 Hungary
• 374 Armenia
• 40 Romania
• 41 Switzerland
• 420 Czech Republic
• 421 Slovakia
• 423 Liechtenstein
• 43 Austria
• 44 UK
• 46 Sweden
• 48 Poland
• 49 Germany

• 246 Diego Garcia
• 247 Ascension
• 290 Saint Helena
• 55 Brazil
• 65 Singapore
• 86 China
• 88234 Global Networks Switzerland AG
• 87810 VISIONng UPT
• 971 UAE

• 1 North America gains momentum
• additional Asian countries (Korea, Japan,
  Australia, ) soon to come ?

http//www.ripe.net/enum/request-archives/
9
International ENUM Activities 2004

• ETSI - make existing ENUM Implementations
  interoperable
• ETSI TISPAN WG4 (April 2004, September 2004)
• Update ETSI TS 102 172 to Version 2 - Mid 2004
• ETSI TS 102 055 on Infrastructure ENUM End 2004
• 2nd ETSI ENUM Plugtest Workshop (4-8 October
  2004)
• ETSI ENUM Plugtests planned December 2004 and Q2
  2005
• IETF - advance RFC2916bis to draft standard
  RFC3761 (done)
• Register various "enumservices" with IANA (SIP
  and H323 registered)
• Definitions for HTTP, FTP, TEL, MAIL SMS, MMS
  due shortly
• ITU-T - make "Interim Procedures" permanent
  (ITU-T, IAB, RIPE)
• ITU-T SG2 Plenary last week, updated Interim
  Procedures
• E.A-ENUM planned to be determined next plenary
• Establish national policy frameworks
• 25 CCs already delegated in e164.arpa, more to
  come soon
• Start commercial deployment of ENUM
• some countries are already planning commercial
  deployments of ENUM during this year (e.g.
  Austria)

10
ENUM Status Asia

• The Asia-Pacific Telecommunity (APT) and the ITU
  organized a joint workshop on ENUM and
  Internationalized Domain Names (IDN) from 21-22
  May, 2004 in Brunei Darussalam. All materials are
  posted on the workshop web site including the
  workshop programme (Word).
• ENUM Overview (Power Point), Richard Shockey,
  IETF ENUM WG Co-Chair, Senior Manager - Strategic
  Technology Initiatives, NeuStar, Inc.
• Interim Procedures for ENUM trials (PowerPoint),
  Greg Jones, ITU
• ENUM Readiness and Trial Implementation Status in
  Australia (Power Point), Paul White, Australian
  Communications Authority (ACA), Australia
• Activities and status in Japan (Power Point),
  Hirofumi Hotta, Japan Registry Service (JPRS),
  Japan
• Activities and Status in China (Power Point), 
  Zhang Dakun, Ministry of Information Industry
  (MII), China
• Korea ENUM Trial Status Update (Power
  Point), Kwan-Ho Song and Dr. Sungwoo Shin, Korea
  Network Information Center (KRNIC)
• ENUM in Singapore (Power Point),  James
  Seng, Infocom Development Authority (IDA),
  Singapore
• ENUM in Europe and Austria (Power
  Point),  Richard Stastny, OEFEG, Austria

11
The biggest problem (James Seng)
Delegation of e164.arpa

• Those who wants to do trials or deploy services
  cant get the delegation
• Those who can get delegation dont know what to
  do with it.
• People starting to use private golden tree

12
Public ENUM Status - What about the US?

• US DOMESTIC POLICY August 13, 2003
• United States Government reiterates its support
  for RFC 2916 and endorses moving forward with
  ENUM based on the concept of a Industry Managed
  LLC
• Similar to Number Portability Structure
• http//www.ntia.doc.gov/ntiahome/press/2003/enum_0
  8132003.htm
• United States ENUM Forum - Created by industry to
  develop policy and steps to Implement ENUM in the
  United States
• http//www.enum-forum.org
• Participants include MCI, ATT, Sprint, SBC,
  Verizon, NeuStar, Cox , CW, Cisco, Telcordia
• Canada too .. http//www.enumorg.ca
• NANP Regulators now in monthly conference calls

13
Content

• ENUM International
• ETSI ENUM Plugtest and Technical Specifications
• ENUM in Austria

14
1st ETSI ENUM Plugtest Workshop

• February 2004 at ETSI in Sophia Antipolis
  (France)
• Welcome to ETSI by Karl Heinz Rosenbrock
  (Director General)
• 72 participants registered / 55 attended
• APRICOT 2004 meeting in Kuala Lumpur in parallel
• some just didn't get a flight or a hotel because
  of 3GSM in Cannes and the carneval in Nice
• all presentations available at
• http//docbox.etsi.org/tispan/open/ENUM-Workshop-2
  0040224-Sophia/
• Goals of the workshop
• Provide an overview on current ENUM trials and
  implementations
• User ENUM in e164.arpa
• Carrier (infrastructure, operator, enterprise)
  "ENUM"
• Discuss future plans, open issues and way forward
• Investigate the needs and requirements for an
  ETSI ENUM Plugtest event
• Define a roadmap

15
Day 1 User ENUM

• ETSI View on User ENUM (Tony Holmes, BT, ETSI
  TISPAN WG4)
• UK (Jim Reid, Chair UK ENUM Trial Group)
• France (Sophie Coste-Martinez, France Telecom)
• Japan (Richard Stastny on behalf of Hiro Hotta,
  JPRS)
• Sweden (Staffan Hagnell, NIC-SE)
• Poland (Andrezej Bartosiewicz, NASK)
• Ireland (Niall O'Reilly, .ie DR)
• Austria (Richard Stastny, OeFEG)
• Germany (Stefan Dieterle, DENIC)
• Netherlands (Adrian Georgescu, AG Projects)
• US (Gary Richenaker, US ENUM Forum, Telcordia)
• Finnland (Klaus Nieminen, Finnish Communication
  Authority)
• Australia (Robert Johnston, Australian
  Communications Authority)
• plus contributions from Korea and Slovakia

16
Main Points Day 1

• The approach towards validation/authentication
  varies widely, from very secure to almost
  non-existent. It demands more discussion/considera
  tion (ETSI created a Work Item)
• Privacy and data security issues are viewed as
  critical (ETSI STF)
• ENUM is viewed as a potential enabler for future
  services and therefore has general regulatory
  support
• There is currently no killer application for the
  initial launch but there is a strong focus
  towards VoIP
• The approach towards implementation and interface
  requirements varies widely (ETSI TS 102 172 V2
  1st ETSI ENUM Plugtest)
• There are differing views on the potential role
  of incumbent telcos and their importance to ENUM
• Regulatory issues are important but are not THE
  key factor in the rollout of ENUM services. ENUM
  will succeed or fail regardless.

17
Day 2 Infrastructure "ENUM"

• ETSI view on Infrastructure ENUM (Tony Holmes,
  BT)
• Carrier ENUM (James Yu, Neustar)
• identify home MMSC, SMSC, SMPP GW, MSSP, HLR/HSS,
  
• MNP data retrieval (identify routing
  number/prefix)
• Infrastructure ENUM (Douglas Ranalli, Netnumber)
• SMS, MMS, NP, IMS (SIP)
• EREG (Tony Rutkowski, Verisign)
• ENUM Registry and IRIS (Internet Registry
  Information Service)
• Freenum.org (Michael Haberler, IPA, nic.at)
• International routing of freephone calls for VoIP
• Recap
• applications/implementations vary more then User
  ENUM
• ETSI TS 102 055 on Infrastructure ENUM

18
Roadmap to Plugtests

• Agreement to organize ETSI ENUM Plugtest events
• Organization Committee
• Michael Haberler, Marco Bernardi, Patrick
  Guillemin, Tony Holmes, Adrian Georgescu, Richard
  Stastny
• ETSI
• Press Release
• ETSI Webpage http//www.etsi.org/plugtests
• email contact plugtests_at_etsi.org
• Mailing list plugtests-enum_at_list.etsi.org
• Raise awareness in various bodies and mailing
  lists
• IETF, RIPE, CENTR, APNIC, ICANN, ITU-T, VON, ..
• 26-30 April ETSI TISPAN3 WG4 discussed further
  actions

19
Roadmap to Plugtests cont.

• 4-8 October 2004 (fixed)
• 2nd ETSI ENUM Plugtest Workshop
• parallel to TISPAN-projects meeting
• participation from Asia-Pacific welcome and
  expected
• define and organize the 1st Plugtest
• 29 Nov 3 Dec 2004 (fixed)
• 1st Plugtest for IP Communications
  (SIP/H323/NGN/ENUM)
• 3rd ETSI ENUM Plugtest Workshop in parallel to
  prepare for
• 2Q 2005 2nd Plugtest potential issues are
• ENUM administrative interfaces
• Infrastructure ENUM
• User ENUM 2nd run
• ETSI Plugtests events and related workshops are
  open for everybody

20
Contacts

• ETSI Plugtest website
• http//www.etsi.org/plugtests/
• E-mail contact plugtests_at_etsi.org
• Mailing List plugtests-enum_at_list.etsi.org
• Subscribe
• sending to listserv_at_list.etsi.org
• subject (empty)
• in the body of the message
• SUB PLUGTESTS-ENUM (firstname lastname)
• Presentations and additional info
• http//docbox.etsi.org/tispan/open/ENUM-Workshop-2
  0040224-Sophia/

21
Recap of ETSI ENUM Activities

• Current Work on ENUM in ETSI TISPAN WG4
• ETSI TS 102 172 Version 2
• New title Minimum Requirements for
  Interoperability of ENUM Implementations (dropped
  the terms Trial and Europe)
• add additional ENUM services (pres, ifax, sms,
  mms, )
• add additional info in ENUM e.g. for ENUM-driven
  numbers
• WI on Authentification and Validation
• Questionnaire on Identification and Validation
• BCP on Authentification and Validation (ETSI
  Guide)
• WI on ENUM Privacy
• ETSI TISPAN WG4/WG7/STF 268 case study
• ETSI TS 102 055 on Infrastructure ENUM
• for routing within and between IP Communication
  Service Providers coexistence with User ENUM
• may use one or more trees within public or
  private DNS
• see also comments by ETSI TISPAN to ICANN on .tel
  application
• ETSI ENUM Plugtests coordination

22
Content

• ENUM International
• ETSI ENUM Plugtest and Technical Specifications
• ENUM in Austria

23
ENUM Background in Austria

• 2000-09 Start of activities within Telekom
  Austria
• 2001-08 First consulation by Austrian regulator
  (RTR)
• 2002-02 ENUM Workshop RTR, group of interested
  partners formed
• 2002-05 Delegation request by RTR to RIPE,
  ITU-TSB for 3.4.e164.arpa
• 2002-06 Tier 1 Registry in operation by NIC.AT
  (the Austrian ccTLD)
• 2002-07 First draft of policy framework for MoU
  by RTR
• 2002-09 Austrian ENUM Trial Platform established
  officially
• 2002-09 ENUM Tier 2 Nameserver (Telekom Austria)
  and clients in operation
• 2002-11 Policy Framework and MoU ready, official
  start of trial
• 2002-11 First Live Demo in Atlanta, GA (Fall
  VON/TIPHON/VISIONng)
• 2002-12 Ready to invite friendly ENUM subscribers
  and users
• 2003-02 Conversion to ETSI TS 102 172 compliance
• 2003-10 First part of trial completed, second
  phase started (business customers)
• 2003-12 Large Scale ENUM and VoIP Pilot started
  at the Uni Vienna (AT43)
• 2003-10 Decision to start preparation for
  commercial deployment
• 2004-10 Target date for commercial ENUM start

24
Austrian ENUM Platform

• The Austrian ENUM TRIAL Platform has fulfilled
  its task
• demonstrated the feasibility of ENUM (proof of
  concept)
• has its lessons learnt
• solved the open issues (e.g. validation, numbers
  to use) (more or less -)
• considers ENUM ready for production
• so the trial phase is ending
• It is necessary to embed ENUM in the legal
  framework
• This is done by the Austrian National Regulatory
  Authority (NRA) - RTR
• The Austrian ENUM Platform will consult RTR
  regarding ENUM issues

25
Legal Framework

• New Austrian Telecommunication Law (TKG 2003)
• based on the New European Framework (NRF)
• New Numbering Ordinance in Austria
• in force since May 12th, 2004
• taking VoIP and ENUM already into account
• 43 720 for national portable number and VoIP
  (semi-nomadic)
• 43 780 for VoIP and ENUM (nomadic)
• Contract between NRA (RTR) and Tier 1 Registry
  (nic.at)
• contains the policy framework for ENUM
• the charter for the 3.4.e164.arpa domain
• the validation guidelines for the Registry and
  Registrars
• basic technical, operational and administrative
  requirements
• Consulting on VoIP and ENUM issues by the
  Austrian ENUM Platform and the AK-TK
  (Intercarrier Platform)

26
Lessons learnt in the ENUM Trials

• Basic issues solved
• ENUM technology works,
• ENUM policy and administration most problems
  solved,
• but there was a shift in focus for the business
  models.
• The original business model of ENUM for
  residential subscribers with opt-in for existing
  numbers has problems
• it's a second line service,
• privacy problems with multiple services (e-mail
  spam)
• Validation and re-validation problem,
• but the major problem is How to overcome
  Metcalfe's Law?
• The usefulness, or utility, of a network equals
  the square of the number of users
• so new approaches are needed.

27
New approaches to ENUM

• New approaches for IP Communications with ENUM
• ENUM for IP-based private networks ("PBX and
  IP-Centrex) with direct-dial-in (DDI)
• ENUM-driven number ranges for IP Communications
  for nomadic users (teleworkers and road-warriors,
  using laptops, PDAs, WiSIP phones and dual-mode
  devices)
• mobile numbers with validation via the SIM-Card
• residential users using terminal adapters with
  FXO ports
• Note well IP Communications is not IP Telephony
• it is IP based services
• ONE of these services is VoIP - and others like
• Directory, Mobility,
• Instant Messaging, Presence, Video, Chat, SMS,
  and, and,
• will become more and more important

28
Main Use Cases for ENUM

• Business IP PBX and IP Centrex
• with geographic and/or numbers for networks (ENUM
  opt-in)
• linking VoIP islands together globally via the
  Internet
• will be reached from the PSTN via private or
  public gateways
• Residential and Business ENUM-driven numbers
• IP device can be reached from IP and PSTN (via
  generic gateways)
• calls may be routed to IP directly from the
  originating PSTN network
• Residential mobile numbers (ENUM opt-in)
• terminate IP originated calls on IP, plus
  evenually forwarding or forking to the mobile
  phone
• PSTN operators may provide forced ENUM access
  from the PSTN via GG
• Residential geographic numbers (ENUM opt-in)
• secondary line (separate termination on PSTN and
  IP)
• primary line attached via terminal adapter or
  SIP-server with FXO port
• primary line (ported out), reached from PSTN via
  PoI

29
ENUM-driven Number Range

• Format 43 780 abcdef (ghi)
• the registration of the ENUM domain IS the number
  assignment
• a cancellation of the ENUM domain will relinquish
  the number
• easy, cheap, one-step process
• decoupling of number range allocation and gateway
  operator
• any gateway may route the whole number
  range,just needs to be able to query ENUM
• any gateway may route similar number ranges
  (e.g. 87810, 42360, 260510, )
• these gateways are called generic gateways (GG)

30
The Generic Gateway
ENUMTier 1
ENUMRegistry
Generic Gateway Operator
IPCSPRegistrar
ENUMTier 2
PSTN ENUM-driven number range e.g. 43 780
Subscription
Internet
Registration
Calling Party A
Called Party B
31
Identification and Validation

• Identification of E.164 number assignees within
  the ENUM system
• depending on identification required for E.164
  number
• (Re-)Validation (re-)checks the right to use the
  E.164 number
• this does not necessarily require identification
  within ENUM
• Validation methods are therefore dependent on the
  number range used
• ENUM-driven numbers (43780)
• only identification may be required (pre-paid?),
  validation is implicit
• phone book entry required
• Mobile numbers (opt-in)
• validation via SIM-Card (e.g. SMS)
• numbers directly assigned to end-user (e.g.
  private networks) (opt-in)
• validation via assignment document
• geographic numbers (opt-in)
• validation via credentials under investigation
• If RegistrarTSP Identification and Validation
  internal matter

32
Austrian National Activities 2004

• Establish a national policy framework 2Q2004
• Start commercial deployment of ENUM 3Q2004
• Residential customers
• ENUM-driven number range 43780 (and also 87810
  VISIONng)
• Mobile numbers (opt-in)
• geographic numbers (terminating on IP) (opt-in)
• geographic numbers primary line on PSTN (opt-in)
• Corporate Customers (IP PBX and IP Centrex)
• Geographic/network numbers (opt-in, IP PBX)
• Geographic/network numbers (opt-in, ported out,
  IP Centrex)
• Deploy Generic Gateways (GG) and ENUM access
  codes from PSTN
• Planned
• Make numbers in ENUM SMS- and MMS-enabled
• Provide trusted identification on SIP for CLI
  (emergency service)
• Provide certificates for E.164 numbers
• to be used in signaling and validation
• Usage of SIM-Cards and IMSI for mobile IP
  Communications
• Provide location information and emergency
  service routing proxies

33
ENUM Myths

• DNS is not fast enough..
• no appreciable effect on call setup times
  (400MS).
• DNS wont scale?!?!
• 10 billion data items already
• More data in intranets than outside
• Over 100,000,000 delegations already
• Every E-Mail including spam has to query DNS

34
Summary

• User ENUM is ready for commercial deployment
• it is technically working
• may inter-work seamlessly with Infrastructure
  ENUM
• client and server applications and products exist
• administrative issues solved internationally and
  nationally
• Main Use Cases are for VoIP, but other services
  may come soon
• messaging, presence, location based services,
• Some countries are already planning, others may
  follow soon
• Issues still under discussion
• privacy
• end-user information in WHOIS
• end-user information in NAPTR
• security
• DNSSEC still under evaluation
• Identification (network asserted identities)
• Common problems on the Internet solutions
  needed everywhere

35
The End
Thank you for your attention
www.enum.nic.at www.oefeg.at www.rtr.at
portal.etsi.org