Numbering All the Bones

Transcription

1 NORDUnet September 2014 Uppsala, Sweden Peter Szegedi Project Development Officer Numbering All the Bones

2 Identity Peter Szegedi szegedip Amsterdam Hungarian Budapest LA szegedi1pet @graham.terena.org Who I am NAMING & NUMBERIG How to reach me ADDRESSING Name translates to an address. But who s behind that address? Slide 2

3 The identity paradox An assigned telephone number has an end-user but the end-user has no face. There are many corner cases. Complex authentication and number validation problem. Even the service provider cannot identify the used from a large number block. Liar paradox (Catch 22): I am lying. This statement is neither true nor false because it is self-referential. I am the valid End-user because the provider that I select identified me as such. This statement is also circular and/or self-referential. Slide 3

4 To break the end-user identity paradox External database Registration, public vetting, and aging Lookup service (DNS) ENUM database Slide 4 End-user Opt-in ENUM

5 From address chaos to address harmony Service centric vs. User centric Separate naming/numbering from the underlying addressing and transport Service agnostic addressing scheme centered around the user Slide 5

6 Why telephone numbers Telephone numbers are global, uniform, and standardized resource identifiers. All E.164 telephone numbers are known to the network because every phone is registered by default in a global arrangement. In contrast, SIP URI relies on the user to populate a record in DNS. That is why many IP to IP calls today route through the PSTN. IP-based devices may register with a local server, a web site, or an IP PBX but there is no universal address directory until ENUM is completed. Slide 6

7 What does ENUM do Maps existing PSTN phone numbers to service specific addresses h323: sip: tel: Based on state-of-the-art DNS Follows a user centric approach szegedi@terena.org does not affect PSTN application level functions such as call routing and signaling facilitates the discovery of resources associated with a telephone number, and does not impact how applications operate does not change the existing right-to-use rules and principles for telephone numbers Slide 7

8 How it works ENUM (DNS) mapps PSTN number to to enable Voice over IP using SIP 3. DNS returns NAPTR record containing SIP URL 2. Calling party proxy UAC queries DNS for location of end point 1. The caller simply dials the person s normal telephone number 4. Calling party UA connects the call Slide 8

9 How it works ENUM (DNS) mapps PSTN number to to enable Voice over IP using SIP ENUM 3. DNS returns NAPTR record containing SIP URL to Calling Party UA 2. SIP UAC queries DNS for location of end point Response Query e164.arpa? Call Setup 1. Caller dials normal phone number Dial SIP Proxy 4. Caller s UA initiates call with SIP URL Sip Sip:jmce@domain.com SIP Proxy Slide 9

10 What is this all for a) Mapping PSTN numbers to Unified Resource Identifiers (URIs) in order to support dialling on devices with numerical keypad only i.e. yet another lookup service before placing the call. b) Looking up services/access methods (e.g., SIP URI, GDS Number, Web URL, etc.) assigned to PSTN numbers in various domains i.e. service discovery. c) Directing (primarily long distance) calls over research networks end-toend i.e. bypassing carrier networks and saving PSTN carrier or IP peering costs. d) Substituting direct peering relationships i.e. accepting incoming calls on an open, public interface governed by NRENs. e) Creating a universal VoIP/ VC directory for R&E - i.e. global arrangement for registering and publishing enduser reachability in a structured, verifiable way.

11 What is this all for b) Address harmony b) One single ENUM (PSTN fallback) for unified dialing c) Service agnostic (service discovery) c) Cost savings b) Long distance calls over NREN end-to-end c) Reduce peering traffic to commercial networks d) Scalability b) No need for direct peering c) Accept calls on a public interface (DNSsec!) e) User identity b) Registration, validation and aging c) Portability Slide 11

12 How to communicate this a) Dial from everywhere! No language, alphabet, or device barriers Take no technical but business approach Reverse business model (difficult to justify though) More ENUM you call the cheaper your bill will be Community effort is needed, once you join Slide 12

13 NRENum.net service of TERENA ENUM service for academia Operated and governed by NRENs Recognized by RIPE ENUM WG (e164.arpa) Slide 13

14 Service milestones August 2006 NRENum.net came into operation May 2008 Became a community service March 2012 Service went global September 2013 Global governance Service policy can be downloaded from Slide 14

15 Global service coordinated by TERENA Global NRENum.net Governance Committee (GNGC) Tim Boundy Janet, UK Erik Kikkenborg NORDUnet, Nordic countries in Europe Ben Fineman Internet2, USA Alex Galhano Robertson RNP, Brazil Jamie Sunderland AARnet, Australia Praveen Misra ERNET, India NRENum.net Opertions Team Mihaly Meszaros NIIF, Hungary Daniel Stirnimann SWITCH, Switzerland Rui Ribeiro FCCN, Portugal Bartlomiej Idzikowski PSNC, Poland Jan Ruzicka CESNET, Czech Republic Kewin Stoeckigt ACM Bernie Hoeneisen Ucom.ch DNS server locations Budapest, Hungary Zagreb, Croatia Zürich, Switzerland Stockholm, Sweden Ann Arbor, Michigan, USA Washington DC, USA Indianapolis, Indiana, USA Palo Alto, California, USA Sydney, Australia Perth, Australia Slide 15

16 36 County Codes delegated

17 < ENUM

18 Global initiatives to support ENUM dialling Internet2 Net+ Video Exchange Global Video Aliance (GVA) Internet2, AARnet, RedCLARA, NORDUnet, Janet, CESNET Global RealTime Communications exchange (GRTC) CEO Forum led by AARnet GÉANT educonf GN3plus - led by Janet Slide 18

19 How to participate... Want your county code to be delegated... Contact Peter Szegedi, TERENA Website: Send your request to Join the mailing list at in Europe and Asia Pacific and Africa, talk to TERENA In the Nordics talk to Erik Kikkenborg, NORDUnet in North America, talk to Internet2 in Latin America, talk to RedCLARA Slide 19

20 Bad practices 1. Get delegated and do nothing Set up a national policy Sub-delegation Tools to support number registration 2. Use virtual numbers Sometimes inevitable (e.164 number shortage) We are flexible but we must avoid (future) clash From sandbox to Telco/Regulator liaison Global CC is not realistic as of today Wildcard number blocks Identity problem still Crawler issue Slide 20

21 To do list... Regulators Require VoIP/Telco operators to provide SIP URIs Require national domain registry to support ENUM Require Telco s to have ENUM enabled gateways Provide PSTN number as a resource Telco/VoIP providers Use ENUM lookups in routing decisions Make money on call termination Web community Solve the address chaos, single sign on Facilitate ENUM for application specific addresses NREN community Solve the identity paradox, authentication and validation Slide 21

22 Window of opportunity Greenfield approach... FCC call on All-IP communications and numbering testbeds Dialog with PHONEWORD.org Telcos are hesitant, Web world is excited! Replace SS7 with ENUM federation NRENum.net could be one of the ENUM trees Demonstrate success to the global community... Slide 22

23 GN4 SA8 Real Time Applications and Multimedia Management Task 1 Real Time Applications (RTA) educonf (H323/GDS) SIP/URI NRENum.net Europe Task 2 Web Real Time Communications (WebRTC) Roadmap for NRENs Demonstrator Task 3 Open Educational Resource (OER) Metadata aggregation engine Web portal front-end Slide 23