1 / 22

ENUM, VoIP, and “Gangsta Rap” How They All Come Together….

ENUM, VoIP, and “Gangsta Rap” How They All Come Together…. Tom Kershaw Vice President, VoIP VeriSign. What Is ENUM?. ENUM is a protocol Born in the IETF Simple Concept: Use DNS to resolve addresses for VoIP Approved, Done, and Nothing Controversial ENUM is a Political Movement

elpida
Download Presentation

ENUM, VoIP, and “Gangsta Rap” How They All Come Together….

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. ENUM, VoIP, and “Gangsta Rap”How They All Come Together…. Tom Kershaw Vice President, VoIP VeriSign

  2. What Is ENUM? • ENUM is a protocol • Born in the IETF • Simple Concept: Use DNS to resolve addresses for VoIP • Approved, Done, and Nothing Controversial • ENUM is a Political Movement • Ownership of Addresses • National Sovereignty • Global Disarmament • Etc. • There is a strong need to separate the protocol/implementation issues from the public policy issues

  3. Some Initial Comments on ENUM • Private (Carrier) ENUM v. Public (User) ENUM • Debates, Controversy, Confusion • The Key Points: • Carrier and User ENUM are different and should have different structures • Carrier and User ENUM are consistent and can co-exist peacefully • There is no clear agreement on what ENUM is for: • The wonderful world of the Internet • The wonderful world of the PSTN • The alleged convergence of these two things • OR….Something totally different

  4. Current State of ENUM • Public ENUM trials and “production” environments • Austria, Australia, Korea are leading • Volume is very small • Driven by the Internet Community • Dependent on users actually caring • Public ENUM Regulatory Bodies • U.S., Japan • Driven by the PTTs • User involvement is little to none • Private ENUM efforts • Cable • Mobile Operators

  5. Drivers for ENUM • The Driver Matters – Results are Different • Internet Community Driven • PTT Driven • Mobile Content Driven • What is the Goal of ENUM – To Drive IP-to-IP Communications that goes beyond traditional voice • People assume that VoIP operators and users are driving ENUM – but they are not

  6. Who Cares About ENUM? What are you talking about? I love ENUM! I have all of his CDs! I don’t care about ENUM!

  7. VoIP and ENUM • ENUM is not relevant to VoIP yet • Volumes are too small • Japan Case • 10 million VoIP endpoints • 10% x 10% = 5% of calls are IP to IP • Benefits of the query with a 5% resolution rate is questionable • ENUM matters only when you can drive res rates above 25% • Enterprise Verticals • Communities of Interest • Peered Private-Public ENUM structures • IE – we have to drive volume and drive resolution rates up collectively rather than pursuing our own private interests

  8. Conclusion: VoIP operators and users do not care about ENUM at present • But there is someone who does care about ENUM…..

  9. Who Cares About ENUM? I Love ENUM! ENUM is great! It makes me money.

  10. U.S. Case: ENUM and Mobile Content • In the U.S. what is driving ENUM is mobile content • 50 Cent makes more money off of ENUM than all the VoIP operators combined • When a user downloads a ringtone, it is sent to the destination MMSC using SMPP • SMPP requires a mailto: address • ENUM is used to discover the mailto: address of the destination • This application leads to some perverse results • how to you map the phone number to the correct mailto: • what if the number is ported? • what is the number is issued under an MVNO?

  11. 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: • Several valid country specific public trials – Austria is leading • U.S. has decided to issue a tender for CC1, split into to administrative domains • Lot’s of Boring Trials Going on Now • Tier II: • A Few Interesting Trials Underway • Every Carrier and Cooperative will have a Root • VoIP Tier IIs brag about 500K users; Mobile will be in the 50 Millions soon

  12. 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 • Mobile Content application is creating a critical mass in ENUM that is not necessarily consistent with the VoIP application

  13. 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)

  14. Private IP Backbone Private Peering: Real World Example • IN NAPTR 10 10 "u" "E2U+sip" “!^.*$!sip:tkershaw@verisign.com!” • IN NAPTR 10 10 "u" “E2U+mailto" “!^.*$!mailto:tkershaw@verisign.com VeriSign Private Root Private ENUM Enterprise Location Server Call Control Call Control Call Control Call Control

  15. Solving the Underlying Network Problem • Many Carriers & Enterprises utilize MPLS for Real-Time Transport • Connection oriented traffic engineering with bandwidth protection • Quality-of-Service mechanisms (e.g. voice prioritization) • Secure MPLS Tunnels/MPLS Virtual Private Networking • Problem: No Exit • MPLS protects the on-net traffic • There is no way off • Firewalls are never touched Federated Extranet (Domain Bridging NAP) NRD THIG Redundant carrier-grade THIGs utilized by one or more federation members Internet Gateway VoIP Gateway MPLS CORE INTERNET PSTN SITE A SITE B • Internet/External connectivity is a completely separate connection Signaling Bearer

  16. MPLS and ENUM Federated Extranet (Domain Bridging NAP) DNS SS7 INTERNET NRD ENUM PSTN THIG MPLS Carrier A MPLS Carrier B DA Corporation A (MPLS VPN A) Corporation B (MPLS VPN B) Corporation B (MPLS VPN B) Corporation A (MPLS VPN A) Signaling Bearer

  17. Private IP Backbone Public IP Backbone Public and Private: A Real Example • IN NAPTR 10 10 "u" "E2U+sip" “!^.*$!sip:tkershaw@verisign.com!” • IN NAPTR 10 10 "u" “E2U+mailto" “!^.*$!mailto:tkershaw@verisign.com Austrian Public Root VeriSign Private Root Company 2 Company 1

  18. Option 1 Option 2 Option 3 Extending ENUM: EREG, DNS Extensions, etc. EREG • IN NAPTR 10 10 "u" "E2U+sip" “!^.*$!sip:tkershaw@verisign.com!” • IN NAPTR 10 10 "u" “E2U+mailto" “!^.*$!mailto:tkershaw@verisign.com Tier 1 ENUM Device Resources Tier 2 ENUM Location Server/Registrar Call Control Call Control Call Control Call Control Perimeter Security and Interop Resources

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

  20. Conclusions • ENUM is currently a mess • Private, Public, Mobile applications are uncoordinated and there is mass confusion • Keep the end goal in mind – creating a public IP infrastructure for applications (voice, video, IM, gaming, etc) • Opt-Out of Opt-In • First to 30 million wins • Anyone doing Private ENUM that is not peering is being short-sighted • And finally…

  21. ENUM: The Preferred Protocol of Gangsta Rap

  22. Thank You! tkershaw@verisign.com 703-948-4509

More Related