ENUM Overview ENUM Vo IP Peering the Future

ENUM Overview ENUM - Vo. IP Peering & the Future of NGN Signaling Peering 2007 Richard Shockey IETF ENUM WG Co-Chair Director – Member of Technical Staff Neu. Star, Inc. 46000 Center Oak Plaza Sterling VA 20166 USA richard. shockey@neustar. com richard@shockey. us +1 571. 434. 5651

Neu. Star Heritage Neu. Star provides trusted and neutral infrastructure services that allow networks to connect and interoperate, enabling: – Routing of 2 B telephone numbers daily (NANPA – NPAC) – Over 12 billion DNS routing queries monthly Additional Highlights – Operates. US and. BIZ TLD’s • Publicly held company – NSR - – Telco-quality performance – solutions require 99. 9% to 99. 999% NYSE reliability • Awarded GSMA Root Registry (680 – The largest communications registry on Earth GSM Operators) 9/05 And Neu. Star has consistently delivered value to customers – Providing Automated Access Provisioning for Network Grooming – Efficiently Managing Competitive Porting – Enabling Network Synergies during Acquisitions – Managing Access to Numbering Resources – Enabling Interoperability for Short Codes • Equinix and Telehouse join global SIP-IX initiative for IMS and Vo. IP enablement 2/06 • Acquired Ultra. DNS 4/06 • 800 + Employees

Why are we here? Bye PSTN. Well, eventually. • Shockey’s Law: Money is the answer what is the question? • Voice is a 800 Billion Dollar Global Industry • • • Deutsche Telecom said it will shut down the PSTN in 2019 British Telecom said it will have the 21 CN fully in place 2015 KPN talks about 2010 GSM-A ongoing discussion about IPX North American Cable Operators are already there. – They WILL optimize Vo. IP session termination strategies by routing directly from one SP to another in 2007 Is there a DMS / 5 ESS bone yard ready?

For the 6, 332 time : “Islands of Vo. IP” problem $ • The PSTN is used as the inter-VOIP “default” network – Service is degraded as it must transverse multiple networks Every VOIP network is an Island (apologies to John Donne!) – Enterprise or carrier VOIP dial plans cannot be remotely accessed by other VOIP gateways • Clash between flat-rate calling and variable network costs – PSTN termination, settlement, and management • Demand to differentiate services in market – Higher quality, presence, usage communities

Vo. IP Peering: It’s not just Vo. IP and it’s not just Peering Cross platform Interoperability Any IP session from any device on any network to any device on any network • Reduce complexity and costs – PSTN termination, settlement, and management – Efficient, scalable business and technology models – Secure, high performance infrastructure • Drive higher-level feature sets – Presence, location, communities and quality – Seamless inter-working of SIP and IMS applications across domains – Reliable call setup and service delivery

Core ENUM RFC 3761 ENUM DNS Service 3. DNS returns NAPTR record containing SIP URL to Calling Party UA 2. Calling party proxy UAC queries DNS for endpoint location Response sip: name@domain. com Query 4. 3. 2. 1. 5. 5. 2. 0. 2. 1. e 164. arpa “Call Setup” 1. The caller dials Sip sip: name@domain. com the person’s telephone number Dial +1 -202 -555 -1234 4. Calling party UA Sip Proxy connects the call Sip Proxy

The NGN Signaling Architecture is not fully in place • You HAVE to translate phone numbers into routing information. • SS 7/C 7 Network cannot be sustained any more than managing 2 networks TDM and IP There is no new service creation in TDM based networks. Confusion about the 3 flavors of ENUM • • – Public - e 164. arpa – Infrastructure – ie 164. arpa – Private – industry lead or private consortiums • Confusion about the role of a root/apex – Who controls the apex – Is a APEX needed • Confusion about the delegation models. – Do you need Tier 2’s? – Carrier vs Nation State • Enterprises are changing the game as well by demanding IP trunking.

ENUM query technology is winning the NNI Interconnection Signaling Protocol argument • DNS based ENUM is faster than SIP Redirect by a factor of 10 • DNS Queries integrates neatly with SIP URI resolution • Commercial - Private ENUM services have exploded • RFC 3761 is central to all NGN architectures – IMS – 3 GPP – MMS/SMS on IP – Packet. Cable 1. 5

Coming – Direct trunking of Vo. IP to SP Networks http: //www. sipforum. org/sipconnect

The Problem with 1 st Gen Vo. IP Peering • First generation peering fabrics won’t scale – Lack of policy control and number validation – Voice, voice, and more voice • New Applications ? ? ? • Major operators want more – – – Redundant and Resilient Infrastructure Policy-based control of service exchange Support for asymmetric business relationships Global service coverage Ecosystem of hardware, software, and service providers. • Combining Registry and Termination services lock carriers into single solution.

Public DNS will never work for service providers • Infrastructure ENUM in the Global DNS will never happen. – ie 164. arpa – DOA in the IETF • Why would any service provider place information into the global DNS that resolves to points of network interconnection? – Security implications staggering – DDOS – No DNSSEC in our lifetime – SPIT • All service provider relationships have been private and will IMHO continue to be bi-lateral.

Its not about ENUM roots. Its about Registries. • The existing SS 7/C 7 signaling networks cannot accommodate NGN IP services. • Vo. IP Peering requires Telephone Number Registries (databases) • Who do you trust do manage YOUR DATA. • The business processes of how operators exchange data to enable interoperable services – How the data is queried is irrelevant • The Registry must be able to process and distribute both IP as well as PSTN data such as LNP

Considerable Vo. IP traffic will be exchanged at Internet Exchange Points • As Willi Sutton said “ Why do you rob banks. . because that is where the money is. ” • The Global Voice network will operate in parallel with classic TCP/IP traffic – – Voice is latency sensitive Voice has higher value per bit - though not as high as SMS Qo. S is an issue (perception is reality) VPN and “big yellow wire interconnections” • Vo. IP traffic exchanges will be private and bilateral – GSM GPRS/IPX traffic is an example.

Neu. Star’s Solution What is SIP-IX? • A coordination function enabling services over IP to interoperate across domains • An extension of Neu. Star’s neutrality and number portability, TLD, and DNS expertise • A standards-based Industry Alliance Program and interoperability certification • Infrastructure integrated with the internet’s leading global exchange providers

SIP-IX Product Architecture

Neu. Star’s Approach and Differentiators • The Operator is the center of the universe – SIP-IX is NOT a “HUB and Spoke” Architecture • The Service is tailored to the needs of Carriers – Comprehensive Product Features and Benefits – Business Model includes Query, Local Replica, and Hosted options – Exclusive IXP-based Service Delivery Architecture • Neu. Star’s experience and qualifications are second to none – – – – Neutral third party, with regular audits Private ENUM services in production for over three years ISO 9001 compliant, with unmatched ENUM, SIP, DNS expertise Investment in Industry Standards Unique experience with the NPAC and service provider customers Visible Commitment to Industry Partnerships and Alliances Proven Financial Strength and Transparency

Key Unique Features and Benefits of SIP-IX • Operators control where & how they access route data – Query option at multiple IXP locations – Local Replica option – Subscribe Option – Managed Local Replica option • Operators control partners access to route data – Contextual policy capabilities – Policy control of partner relationships, route exposure, and routing data – Centralized control of multiple services – Voice, video, IM, presence, etc. • Operators control their business relationships – Trading partners are not necessarily peers – Settlement terms are dictated and managed by the operator – Routes are only exposed to approved trading partners • Operators OWN their data and policies.

Key Unique Features and Benefits of SIP-IX (cont. ) • Operators control where to exchange bearer traffic – – – Neu. Star is not, and never will be, in the bearer path Public or private IXP exchange points Private interconnects No requirement for unique dedicated links SIP-IX does NOT create a hubbing architecture that limits connectivity options and injects unwanted latency • Operators are not limited to Vo. IP endpoints only – – “All Call Query” approach includes TDM route discovery option All data Portability Corrected automatically! Optional interconnect to TDM endpoints on IP backbones Optional interconnect to IP endpoints on TDM backbones

All Call Query on Call Origination via 3761 • • All PSTN and Vo. IP or advanced service data delivered in one query. New Service Delivery is just a URI away. SIP redirect option avaiable $ORIGIN. 1. 5. 6. 5. 4. 3. 4. 1. 7. 5. 1. carrier. net Output ord pr fl service regexp IN NAPTR and IN NAPTR Plus 20 10 "u" “E 2 U+sip" "!^. *$!sip: 15714345651@proxy 4. mso. net; user=phone!". 10 10 "u" “E 2 U+sip: contact" "!^. *$!sip: 15714345651@240. 67. 89. 124!". 30 10 "u" "E 2 U+pstn: tel" "!^. *$!tel: +15714345651; npdi; rn=+15712768933" 40 10 "u" "E 2 U+pstn: cnam" "!^. *$!data: application/cnam, Richard%Shockey!" IN NAPTR IN NAPTR 100 10 "u" "E 2 U+ical“ 100 10 "u" "E 2 U+sms“ 100 10 "u" "E 2 U+pres “ 100 10 "u" "E 2 U+im“ 100 10 "u" "E 2 U+vcard“ "!^. *$!http: //example. net/user 21. ical!" "!^. *$!mailto: 15714345651@mmsc 21@carrier. net!“ "!^. *$!pres: 15714345651@mmsc 21@carrier. net!“ "!^. *$!im: username@carrier. net!“ "!^. *$!http: //example. net/vcard. vcf!“

Neu. Star’s WMRS – in use by wireless industry today How do your route a picture if all you have is a phone number? Private ENUM with LNP Correction for MMS Routing CO Code Assignments Process turns CO Code and NPAC data into URIs, then loads the mapping into the Routing DB

White Label SIP-IX Services Application Server SS 7 Internet Broadsoft XO Servers AS SBC (ASH, SJC, ORD) Sonus XO XOPSX PSX Routing DB. STP Sonus SGX SGX SIP, RTP National IP Network Application Server MGCP, RTP IAD Wholesale VOIP Customer 1 SIP, RTP IAD PRI CAS DMS / 5 E PBX XO Customer Wholesale VOIP Customer 2 Sonus Remote Market GSX Sonus Local Market GSX DMS / 5 E PST N TDM VOIP SBC Session Border Control

The SIP-IX Paradigm Subscribe Or Query Neutral Registry External SIP-IX at IXP Po. P’s All call query on call origination déjà vu all over again Media Gateway Tandem Access Switch DNS or SIP Redirect Query Response SIP Proxy / SS / CSCF Terminating SIP Proxy / SS / CSCF Neutral Registry IP SCP Internal

There is still work to do. • SPEERMINT WG on Peering / Interconnection • Proposed PEPPERMINT BOF on Registry Provisioning issues. – “ ENUM is specifically chartered to develop protocols that involve the translation of E. 164 numbers to URI's. SPEERMINT has been chartered to develop best current practices among real-time application service providers and how such services interconnect across domain boundaries. It is clear from discussions in both working groups that Multi. Media Interconnection will require address of record data to be provisioned among administrative domains outside the normal scope of establishing a SIP session. ” • • Provisioning goes to the heart of the issue “ How do you trust the data you are using to route? ” Build on RFC 4114 and RFC 4414 ? ? ? Probably settle on SOAP/XML interfaces Working to formalize BOF in at IETF 69 in Chicago.

In Conclusion ….