VoIP, Portability, and the Evolution of Addressing


Published on

LNPA & Future of Numbering Working Groups

Published in: Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Number must be in full E.164 format including Country Code
  • VoIP, Portability, and the Evolution of Addressing

    1. 1. VoIP, Portability, and the Evolution of Addressing LNPA & Future of Numbering Working Groups April 14, 2005 Presented by Penn Pfautz
    2. 2. <ul><li>In a pre-LNP environment, call routing based on 6-digit (NPA-NXX) translation of destination number from LERG. </li></ul><ul><li>In an LNP environment, call routing based on 6-digit (NPA-NXX) translation of a Location Routing Number (LRN). </li></ul>PSTN Routing Regional NPAC SMS Carrier LSMS LNP SCP Porting Carrier Switch NPA-NXX Routing tables Dialed Number LRN Telcordia LERG™ industry broadcast record update Carrier OSS NPA-NXX CLLI Assoc. Trunk Selection Trunking data
    3. 3. Problem Statement & Solution Path <ul><li>As carrier networks evolve to IP how should routing (including portability) be handled? </li></ul><ul><ul><li>SIP is signaling protocol of choice; URIs which can be resolved to IP addresses are the elements of address specification </li></ul></ul><ul><ul><li>Unification of routing functions for all numbers (including portability) should be the objective so as to minimize service provider costs </li></ul></ul><ul><li>Evolution of voice networks to IP and IP interconnection argues for an IP-based solution – e.g. some form of ENUM which was specifically designed to map E.164 numbers into URIs </li></ul><ul><ul><li>Current ATIS PTSC NI-NI document envisions ENUM as target </li></ul></ul><ul><ul><li>Supports evolution away from code-based routing and associated limitations on numbering resource optimization </li></ul></ul>
    4. 4. What is ENUM? <ul><li>Provides mapping from E.164 numbers to IP resources </li></ul><ul><ul><li>Defined by IETF in RFC 3761 </li></ul></ul><ul><ul><li>Telephone number as domain name </li></ul></ul><ul><ul><li>Built on top of DNS </li></ul></ul><ul><ul><li>Look up returns URI </li></ul></ul><ul><ul><li>Example: +1-973-236-6797 </li></ul></ul>DNS Lookup sip:sfisher@att.net sip: sfisher@verizon.com mailto:sfisher1@att.com mailto:steve_fisher@yahoo.com
    5. 5. The Public ENUM Infrastructure $ORIGIN e164.arpa. IN NS nsnanp.enum.com . 4.4 IN NS sweden_enum.com . … $ORIGIN IN NS e164.att.net . IN NS e164.xyz.com . … $ORIGIN IN NAPTR 100 10 &quot;u&quot; &quot;E2U+SIP&quot; &quot;!^.*$!sip:19732366797@att.net!&quot; . e164.arpa Tier 0 (Country Code Registry) Tier 1 (Telephone Number Registry) Tier 2 (Application Information) International Implementation worked in IETF and ITU-T National Implementation worked in CC1 ENUM LLC and ENUM Forum (US) … nsnanp.enum.com ( e164.att.net sweden_enum.com (4.4.e164.arpa)
    6. 6. ENUM Call Flow Internet 794-867-5309 sip:7948675309@carrierc.net mms:7948675309@carrierc.net DNS MSC Carrier C MMSC Carrier A
    7. 7. Why ENUM? <ul><li>Built on fundamental IP technology – not legacy foundation </li></ul><ul><ul><li>Queries for URIs will come from IP network elements </li></ul></ul><ul><ul><li>No plans exist to update existing NP architecture (e.g. TRQ1-3) to make use of URIs </li></ul></ul><ul><li>Distributed database, not SMS download </li></ul><ul><li>ENUM operates at a 10-digit level obviating the need for a separate portability correction </li></ul><ul><li>ENUM can support both end user and carrier provision of IP routing info </li></ul><ul><ul><li>Many VoIP providers do not directly obtain numbering resources and so, not being code or block holders, cannot provision the NPAC or LERG </li></ul></ul><ul><ul><li>These are the carriers most likely to desire VoIP interconnection so their exclusion significantly limits scope of solution </li></ul></ul><ul><ul><ul><li>FCC SBCIS decision could alter this but may not given the uncertainties surrounding its implementation (terms & costs of interconnection; qualification for the ESP exemption </li></ul></ul></ul><ul><li>ENUM can support both carrier specific interconnection and general “Internet” interconnection </li></ul>
    8. 8. ENUM Status <ul><li>Country Code 1 ENUM LLC planning RFP for Tier 1 Registry operator to be in service mid 2006 </li></ul><ul><li>Country Code 1 ENUM LLC members include AT&T, GoDaddy.com, MCI, SBC Laboratories, Sprint, Verizon, and BellSouth </li></ul><ul><li>ENUM in a domain other than e164.arpa can be rapidly implemented by a group of carriers should the public ENUM effort encounter difficulties </li></ul><ul><li>Some wireless carriers use private ENUM for message center identification today. </li></ul><ul><li>Other private ENUM implementations also exist </li></ul>
    9. 9. Alternatives to ENUM <ul><li>As long as code-based routing remains, more efficient to tie specification of IP Point-of-Interface to CO code or switch CLLI and let LNP function normally to identify CO Code to be used in routing </li></ul><ul><li>This could be done as enhancement of LERG or via other processes </li></ul>