Implementing Telephone Numbers for VoIP Tony Rutkowski Vice-President of Regulatory Affairs mailto:trutkowski@verisign.com...
The Relevant Immediate Requirements <ul><li>we require [VoIP E.164 number users] </li></ul><ul><ul><li>to comply with  </l...
Part 52 - Numbering
Numbering Dependencies: regulatory and operational <ul><li>National Security and Critical Infrastructure Protection </li><...
Architecting viable solutions for numbering systems NGN IP-Enabled Internet PSTN/CMRS SS7 Internet LERG Resolution Service...
Needed Numbering Related Capabilities <ul><li>In the SS7 signalling infrastructure </li></ul><ul><ul><li>Ability to discov...
Needed Steps <ul><li>ATIS Industry Numbering Committee (INC) and potentially other ATIS standards bodies to develop defini...
Numbering Developments Worldwide <ul><li>Meta </li></ul><ul><ul><li>Large-scale focus on Next Generation IP-Enabled Networ...
Upcoming SlideShare
Loading in...5
×

Mar05_VeriSign_VoIP_Presentation.ppt

243
-1

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
243
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Mar05_VeriSign_VoIP_Presentation.ppt

  1. 1. Implementing Telephone Numbers for VoIP Tony Rutkowski Vice-President of Regulatory Affairs mailto:trutkowski@verisign.com Tom Kershaw Vice-President of VoIP Services mailto:tkershaw@verisign.com presentation to North American Numbering Council 15 March 2005 Washington DC USA
  2. 2. The Relevant Immediate Requirements <ul><li>we require [VoIP E.164 number users] </li></ul><ul><ul><li>to comply with </li></ul></ul><ul><ul><ul><li>the Commission’s other numbering utilization and optimization requirements </li></ul></ul></ul><ul><ul><ul><li>numbering authority delegated to the states, and </li></ul></ul></ul><ul><ul><ul><li>industry guidelines and practices (See 47 C.F.R. Part 52) </li></ul></ul></ul><ul><ul><ul><ul><li>including filing the Numbering Resource Utilization and Forecast Report (NRUF) </li></ul></ul></ul></ul><ul><ul><li>to file any requests for numbers with the Commission and the relevant state commission at least thirty days prior to requesting numbers from the NANPA or the PA </li></ul></ul><ul><li>--FCC SBCIP Order, 1 Feb 2005 </li></ul><ul><li>Numbering Administration. 47 USC § 251(e) </li></ul>
  3. 3. Part 52 - Numbering
  4. 4. Numbering Dependencies: regulatory and operational <ul><li>National Security and Critical Infrastructure Protection </li></ul><ul><ul><li>priority access during or after disasters (NS/EP) </li></ul></ul><ul><ul><li>public safety emergency and law enforcement assistance (CALEA) </li></ul></ul><ul><ul><li>network attack mitigation (NS/EP) </li></ul></ul><ul><li>Consumer Requirements </li></ul><ul><ul><li>consumer emergency calls (E112/E911) </li></ul></ul><ul><ul><li>consumer protection and privacy (Do Not Call; CANSPAM) </li></ul></ul><ul><ul><li>authenticated caller or sender identification </li></ul></ul><ul><ul><li>disability assistance (TRS) </li></ul></ul><ul><ul><li>universal service </li></ul></ul><ul><li>Competition and Settlements Requirements </li></ul><ul><ul><li>number portability (1996 Act) </li></ul></ul><ul><ul><li>service interoperability (Computer III) </li></ul></ul><ul><ul><li>intercarrier compensation (ICF) </li></ul></ul><ul><li>Operations Requirements </li></ul><ul><ul><li>service provider coordination </li></ul></ul><ul><ul><li>fraud detection and management </li></ul></ul><ul><ul><li>default service and routing options </li></ul></ul><ul><ul><li>transaction accounting </li></ul></ul>
  5. 5. Architecting viable solutions for numbering systems NGN IP-Enabled Internet PSTN/CMRS SS7 Internet LERG Resolution Services Number Resolution Number Directories G/W 800 NPAC LIDB IRIS- EREG Others G/W Includes border gateway resolvers, ENUM resolvers, DA Resolution Services Resolution Services Resolution Services
  6. 6. Needed Numbering Related Capabilities <ul><li>In the SS7 signalling infrastructure </li></ul><ul><ul><li>Ability to discover, resolve, and use VoIP telephone numbers </li></ul></ul><ul><ul><ul><li>Need: identify the number as VoIP and propagate the gateway information </li></ul></ul></ul><ul><ul><li>Ability to discover and access VoIP number directories </li></ul></ul><ul><ul><ul><li>Need: identify the number as VoIP and propagate the directory information </li></ul></ul></ul><ul><li>In the IP-Enabled signalling infrastructure </li></ul><ul><ul><li>Ability to discover, resolve, and use VoIP telephone numbers </li></ul></ul><ul><ul><ul><li>Need: accommodate multiple platforms and implementations </li></ul></ul></ul><ul><ul><li>Ability to discover and access VoIP number directories </li></ul></ul><ul><ul><ul><li>Need: generic capability. IRIS-EREG does this, but needs North American specific regulatory and operational extensions plus explicit discovery mechanism </li></ul></ul></ul><ul><ul><ul><li>Need: gateway arrangements between IRIS and SS7 based directory systems </li></ul></ul></ul>
  7. 7. Needed Steps <ul><li>ATIS Industry Numbering Committee (INC) and potentially other ATIS standards bodies to develop definitive operational requirements </li></ul><ul><ul><li>ATIS Working Groups to develop needed standards </li></ul></ul><ul><ul><li>Most urgent standards have a high priority </li></ul></ul><ul><li>NANC review of any policy issues with INC platform, provides advice to the Commission </li></ul><ul><li>Commission adopts needed requirements in 99-200 and 04-36 proceedings </li></ul>
  8. 8. Numbering Developments Worldwide <ul><li>Meta </li></ul><ul><ul><li>Large-scale focus on Next Generation IP-Enabled Network (NGN) frameworks, capability sets, architectures, operational requirements, and standards </li></ul></ul><ul><ul><ul><li>Includes ITU-T, ETSI, 3GPP, Parlay, ATIS, TIA, Cable Labs, IETF, OASIS, etc… </li></ul></ul></ul><ul><li>Global – ITU-T </li></ul><ul><ul><li>Study Group 2 </li></ul></ul><ul><ul><ul><li>E.164 implementations </li></ul></ul></ul><ul><ul><ul><ul><li>Not much ENUM takeup, no apparent interest in “public” ENUM </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Continuing domain, security and control issues </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Significant Asia-Pacific region ENUM experiments appear to be all VPN-based, emulating existing SS7 Intelligent Network infrastructure </li></ul></ul></ul></ul><ul><ul><ul><li>Possible other number bases, e.g., E.212, could be used for communication </li></ul></ul></ul><ul><ul><ul><li>Number portability recommendation stalled </li></ul></ul></ul><ul><ul><ul><li>E.FIND directory service work approved as correspondence group (see annex) </li></ul></ul></ul><ul><ul><li>Study Groups 4 and 17 </li></ul></ul><ul><ul><ul><li>M.1400 unique global provider identifier initiative (ICC [OCC in U.S.]) – expansion to include all providers and considering “rapid resolution” capabilities </li></ul></ul></ul><ul><li>Key emerging global issue: geographic relationship of numbers </li></ul><ul><ul><li>In a nomadic as well as VoIP world, substantial geographic portability is unavoidable </li></ul></ul><ul><ul><li>Jurisdictions (countries and locals) need to consider how to accommodate and manage the use effectively </li></ul></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×