ENUM Presentation #846 Jong Lee Strategic Development VeriSign

2 A Couple of Things About ENUM It’s a Protocol – Nothing More and Nothing Less Opt-In Has to Go Carrier ENUM Matters; Public ENUM Does Not Tier 2 ENUM will Merge with SIP Location in Many Cases Technology Does Not Matter It’s Getting Too Political

3 Business/Regulatory State of the “Roots” Tier 0: Only one database controlled by RIPE NCC and ITU (policy only) Contains participating country codes. Delegation would be at the NPA level for the US Tier I: Within North America there could be several Tier 1 databases, which would provide multiple business opportunities instead of a single monopoly. The US Tier 1s would receive their delegation at the NPA level. Lot’s of Boring Trials Going on Now Tier II: A Few Interesting Trials Underway Every Carrier and Cooperative will have a Root

4 Current Issues With ENUM Very few VoIP platforms support ENUM today Nobody has figured out how to make money from ENUM yet Nothing in ENUM you can’t do with SIP Huge political issues over data ownership Who wants to be the root? ENUM solves only a small part of the problem Where you are is easy – how to get to you in a secure, reliable matter is another issue

5 ENUM: One Piece in the Puzzle Tier 1 ENUM Misc. IP Network? Location Server/Registrar Tier 2 ENUM Call Control IN NAPTR "u" "E2U+sip" IN NAPTR "u" “E2U+mailto"

6 ENUM: Missing Pieces I Know the Destination Domain of the Called Party I Can Now Query the Destination to Find the IP Address But: What QoS Rules are Associated with the Destination What Protocol/Variations are Available at the Destination What Network Path to Take What Security Policies/Keys Are Needed ENUM provides the information, but assumes the network will be able to figure it out. Reality: It Won’t (at least not yet)

7 ENUM Issues to Be Resolved Critical Mass (the Network Problem) Application developers Public or private directories Update rate One or many - providers, databases, … Regulatory and policy issues New identifiers Coverage PSTN Service Logic

8 Conclusions ENUM is starting to happen in trials Public trials have yet to generate anything interesting Private Tier 2 trials are getting interesting (like car wrecks are interesting) Interop, QoS and Security are barriers Need more Free Market input Opt-Out of Opt-In

Clearing and Peering: New Models for Carrier and Enterprise Interconnect

10 Conclusions (Answer Before Question) Clearing Is Over Peering is the New Model Old Model: Exchanging Traffic New Model: Peered Route Resolution Issues: Data Ownership Security Network Engineering Interoperability

Radical Statement 1: If a Call Starts on an IP Device and Ends on an IP Device, it should use the IP network end to end

Radical Statement 2: If a Call Starts or Stops on the PSTN, Use the PSTN

Fact: We Are Not Following Rule #1 or Rule #2 Today

14 Clearing and Peering: A History VoIP “Peering” Has Been Going on For Many Years More Clearing than Peering Arbitrage to Arbitrage Focus Replacing IXC/International Trunks with IP Long Haul Trunking Savings Bypass/Arbitrate This market is pretty much done New Models for Peering are Endpoint Focused Rather than Trunk Focused

15 There Is No VoIP Today Current model for VoIP carrier is local only Offnet calls connect via PSTN, even if destination is IP Many operators in more than one market use PSTN even for on-net traffic between platforms Small Operators face standard interconnect agreements for terminating offnet traffic Why VoIP Peering is Good Reduce costs of PSTN interconnect for IP-IP Calls Reduce operational burden of maintaining interconnects, MGs and SS7 links Enable new services like video, collaboration and presence Regional Operators Encounter Specific Challenges Economies of scale, Turnkey Solutions Enable cooperative application development and delivery – History of ILEC market shows this is critical to success

16 Elements of Peering: Routing Engine SIP Redirect Engine ENUM/DNS Interface to CCE External Callouts (SIP or ENUM) Number Analysis and Normalization (e.164 or URL) TN Discovery TN Exists? Yes= BE RouteList External Callout Engine *LNP *CNAM *Carrier Select (ENUM or SIP) Route Engine TN To BE Route List Proportional Route Splay Route ToD/DoW Engine Class 4 Route Default (Trunk Group, PSTN Ctvty) Route Propagation: TGREP/TRIP/Manual Provisioning

17 Elements of Peering: Subscriber Profiling Subscriber Data Address of Record Address Type Trans ID Accnt Status Services References Contact IDs Contact Contact URI Sequence Expiration Call ID Priority Secure Authentication Presence Server SIMPLE ENUM SIP Redirect Policy Engine

18 Role of ENUM Provides protocol and architecture to discover if a given phone call is IP-IP Returns carrier domain of destination number Allows end-to-end VoIP interconnection However: ENUM is not widely deployed on SS, BE or SIP Proxy infrastructure ENUM does not solve the entire problem – directory of destinations is just one piece in secure peering ENUM has become very political

19 Simple Peering Architecture PSTN Media Gateway CallAgent Directory SIP/ENUM Service Broker Inter-Carrier Settlement (??) Subscriber Portal ASP Domain Applications/Services MSO A CallAgent CMTS CallAgent DSLAM VoIP Operator IP Core Border Element Border Element

20 Peering Architectural Components Core VoIP directory provides ENUM and/or SIP resolution of queries Returns domain/IP of the partner that owns the subscriber Admin portal allows operators to monitor and access their own data in real time Management of Network Border Border and Firewall management NAT Transversal and Pinhole Management Firewall Integrity and Intrusion Detection Billing and Settlement between VoIP Carriers Open questions on settlement: Will there be Compensation? What is the Service Model (per registration, per transaction, per termination) Even with “bill and keep” settlement, call record exchange will be necessary for traffic engineering purposes Application Sharing

21 LNP CNAP DNC Toll-Free SS7 The Ancillary Data Layer Sigtran DNS/ENUM SIP(CMSS) Service Delivery CORE ServiceBroker MSO Customization and Provisioning

22 Peering Architecture: Operator to Enterprise In addition to Inter-Carrier peering, Carriers will want to interconnect to other VoIP islands Enterprises Public Sector In addition to directory and security, interoperability must be addressed Enterprises are largely H.323 based today; slow migration to SIP Other carriers are running different variations of SIP Example: PrivacyID Protocol normalization will be necessary at the edge of the network to protect the application delivery function Quality of Service: Is All Routing Created Equal?

23 VoIPDirectory Full Peering Architecture Out-Of-Band Provisioning (Web Based Subscriber and Admin Portal Service Core SIP (CMSS) IP Network ASP Domain Hosted Third-Party Apps ServiceBroker Call Agent VoIP Carrier Border Element SIP (CMSS) DSLAM IPPBX Enterprise A IP-PBX Enterprise B SIP (CMSS) Border SC Firewall SIP (CMSS) H.323 Call Agent Cable MSO A CMTS MGCP/MEGACO MTA MGCP/MEGACO MTA Border Element SIP (CMSS) Work at Home Employee of Enterprise B Firewall Border SC

24 Advantages of Full Peering Model Reduces cost of calls between operators by eliminating need to hand off to IXC/PSTN Creates end-to-end VoIP network to enable shared value-added services Provides highly predictable network cost model Maintains complete perimeter security Maintains a SIP core network while enabling carriers to connect to every other VoIP operator in the world Allows operators to Address Key Subscriber Demographics Teleworkers Demographic

25 Bridging VoIP Islands Secure interconnection Normalized to Backbone standards Robust suite of applications Interconnection Directory Benefits To Operator: Reduced Operations Costs Reduced Capital Outlays Network Flexibility Support for New Services Rapid Application Introduction Summary: Elements of Peering Secure, Reliable, End-to-End VoIP NetworkCore Security Assets Value-added Services SignalingInfrastructure Billing, Mediation and Settlement Directory Capability Inter- operability Security Applications Directory

Thank You!