1. ENUM - VoIP Peering Peering 2007 ENUM Overview
ENUM - VoIP Peering
& the Future of NGN Signaling
Peering 2007
ENUM Overview
Richard Shockey
IETF ENUM WG Co-Chair
Director – Member of Technical Staff
NeuStar, Inc.
46000 Center Oak Plaza
Sterling VA USA
ENUM and the Enterprise

2. NeuStar Heritage Operates .US and .BIZ TLD’s Additional Highlights
NeuStar provides trusted and neutral infrastructure services that allow networks to connect and interoperate, enabling:
Routing of 2B telephone numbers daily (NANPA – NPAC)
Over 12 billion DNS routing queries monthly
Operates .US and .BIZ TLD’s
Telco-quality performance – solutions require 99.9% to % reliability
The largest communications registry on Earth
And NeuStar 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
Additional Highlights
Publicly held company – NSR -NYSE
Awarded GSMA Root Registry (680 GSM Operators) 9/05
Equinix and Telehouse join global SIP-IX initiative for IMS and VoIP enablement 2/06
Acquired UltraDNS 4/06
800 + Employees

3. Why are we here? Bye 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 21CN fully in place 2015
KPN talks about 2010
GSM-A ongoing discussion about IPX
North American Cable Operators are already there.
They WILL optimize VoIP session termination strategies by routing directly from one SP to another in 2007
Is there a DMS / 5ESS bone yard ready?

4. For the 6,332 time : “Islands of VoIP” 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

5. Cross platform Interoperability
VoIP Peering: It’s not just VoIP 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

6.
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
Query e164.arpa
“Call Setup”
1. The caller dials the person’s telephone number
Sip
4. Calling party UA connects the call
Dial
Sip Proxy
Sip Proxy
ENUM and the Enterprise

7. The NGN Signaling Architecture is not fully in place
You HAVE to translate phone numbers into routing information.
SS7/C7 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 - e164.arpa
Infrastructure – ie164.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.

8. 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 – 3GPP
MMS/SMS on IP
PacketCable 1.5

9. Coming – Direct trunking of VoIP to SP Networks

10. The Problem with 1st Gen VoIP 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.

11. Public DNS will never work for service providers
Infrastructure ENUM in the Global DNS will never happen.
ie164.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.

12. Its not about ENUM roots. Its about Registries.
The existing SS7/C7 signaling networks cannot accommodate NGN IP services.
VoIP 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

13. VoIP traffic exchanges will be private and bilateral
Considerable VoIP 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
QoS is an issue (perception is reality)
VPN and “big yellow wire interconnections”
VoIP traffic exchanges will be private and bilateral
GSM GPRS/IPX traffic is an example.

14. NeuStar’s Solution What is SIP-IX?
NeuStar’s Solution What is SIP-IX?
A coordination function enabling services over IP to interoperate across domains
An extension of NeuStar’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
ENUM and the Enterprise

15. SIP-IX Product Architecture

16. NeuStar’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
NeuStar’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

17. 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.

18. Key Unique Features and Benefits of SIP-IX (cont.)
Operators control where to exchange bearer traffic
NeuStar 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 VoIP 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

19. All Call Query on Call Origination via 3761
All PSTN and VoIP or advanced service data delivered in one query.
New Service Delivery is just a URI away.
SIP redirect option avaiable
$ORIGIN carrier.net
Output
ord pr fl service regexp
IN NAPTR "u" “E2U+sip" .
and
IN NAPTR "u" “E2U+sip:contact" .
IN NAPTR "u" "E2U+pstn:tel" "!^.*$!tel: ;npdi;rn= "
IN NAPTR "u" "E2U+pstn:cnam" "!^.*$!data:application/cnam,Richard%Shockey!"
Plus
IN NAPTR "u" "E2U+ical“ "!^.*$!
IN NAPTR "u" "E2U+sms“
IN NAPTR "u" "E2U+pres “
IN NAPTR "u" "E2U+im“
IN NAPTR "u" "E2U+vcard“ "!^.*$!

20. NeuStar’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
Process turns
CO Code and NPAC
data into URIs, then
loads the mapping
into the Routing DB
CO Code
Assignments

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

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

23. 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.

24. In Conclusion ….