Implementing Telephone Numbers for VoIP

Tony RutkowskiVice-President of Regulatory Affairsmailto:trutkowski@verisign.com

Tom KershawVice-President of VoIP Servicesmailto:tkershaw@verisign.com

presentation to

North American Numbering Council15 March 2005Washington DC USA

2

The Relevant Immediate Requirements

+ we require [VoIP E.164 number users]▪ to comply with

– the Commission’s other numbering utilization and optimization requirements– numbering authority delegated to the states, and– industry guidelines and practices (See 47 C.F.R. Part 52)

• including filing the Numbering Resource Utilization and Forecast Report (NRUF)

▪ 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

--FCC SBCIP Order, 1 Feb 2005

+ Numbering Administration. 47 USC § 251(e)

3

Part 52 - Numbering52.1 Basis and purpose.52.3 General.52.5 Definitions.52.7 Definitions.52.9 General requirements.52.11 North American Numbering Council.52.12 North American Numbering Plan Administrator and B&C Agent.52.13 North American Numbering Plan Administrator.52.15 Central office code administration.52.16 Billing and Collection Agent.52.17 Costs of number administration.52.19 Area code relief.52.2 Thousands-block number pooling.52.21 Definitions.52.23 Deployment of long-term database methods for number portability by LECs.52.25 Database architecture and administration.52.26 NANC Recommendations on Local Number Portability Administration.52.27 Deployment of transitional measures for number portability.52.29 Cost recovery for transitional measures for number portability.52.31 Deployment of long-term database methods for number portability by CMRS providers.52.32 Allocation of the shared costs of long-term number portability.52.33 Recovery of carrier-specific costs directly related to providing long-term number portability.52.101 General definitions.52.103 Lag times.52.105 Warehousing.52.107 Hoarding.52.109 Permanent cap on number reservations.52.111 Toll free number assignment.

4

Numbering Dependencies: regulatory and operational

+ National Security and Critical Infrastructure Protection▪ priority access during or after disasters (NS/EP)▪ public safety emergency and law enforcement assistance (CALEA)▪ network attack mitigation (NS/EP)

+ Consumer Requirements▪ consumer emergency calls (E112/E911)▪ consumer protection and privacy (Do Not Call; CANSPAM)▪ authenticated caller or sender identification▪ disability assistance (TRS)▪ universal service

+ Competition and Settlements Requirements▪ number portability (1996 Act)▪ service interoperability (Computer III)▪ intercarrier compensation (ICF)

+ Operations Requirements▪ service provider coordination▪ fraud detection and management▪ default service and routing options▪ transaction accounting

5

NGN IP-Enabled InternetPSTN/CMRS SS7 Internet

Architecting viable solutions for numbering systems

LERG ResolutionServices

Number Resolution

Number Directories

G/W

800

NPAC

LIDBIRIS-EREG

Others

G/W

Includes border gateway resolvers, ENUM resolvers,

DA

ResolutionServicesResolution

ServicesResolutionServices

6

Needed Numbering Related Capabilities

+ In the SS7 signalling infrastructure▪ Ability to discover, resolve, and use VoIP telephone numbers

– Need: identify the number as VoIP and propagate the gateway information

▪ Ability to discover and access VoIP number directories– Need: identify the number as VoIP and propagate the directory information

+ In the IP-Enabled signalling infrastructure▪ Ability to discover, resolve, and use VoIP telephone numbers

– Need: accommodate multiple platforms and implementations

▪ Ability to discover and access VoIP number directories– Need: generic capability. IRIS-EREG does this, but needs North American

specific regulatory and operational extensions plus explicit discovery mechanism

– Need: gateway arrangements between IRIS and SS7 based directory systems

7

Needed Steps

+ ATIS Industry Numbering Committee (INC) and potentially other

ATIS standards bodies to develop definitive operational

requirements▪ ATIS Working Groups to develop needed standards▪ Most urgent standards have a high priority

+ NANC review of any policy issues with INC platform, provides

advice to the Commission

+ Commission adopts needed requirements in 99-200 and 04-36

proceedings

8

Numbering Developments Worldwide

+ Meta▪ Large-scale focus on Next Generation IP-Enabled Network (NGN) frameworks,

capability sets, architectures, operational requirements, and standards– Includes ITU-T, ETSI, 3GPP, Parlay, ATIS, TIA, Cable Labs, IETF, OASIS, etc…

+ Global – ITU-T▪ Study Group 2

– E.164 implementations• Not much ENUM takeup, no apparent interest in “public” ENUM• Continuing domain, security and control issues• Significant Asia-Pacific region ENUM experiments appear to be all VPN-based,

emulating existing SS7 Intelligent Network infrastructure– Possible other number bases, e.g., E.212, could be used for communication– Number portability recommendation stalled– E.FIND directory service work approved as correspondence group (see annex)

▪ Study Groups 4 and 17– M.1400 unique global provider identifier initiative (ICC [OCC in U.S.]) – expansion to

include all providers and considering “rapid resolution” capabilities

+ Key emerging global issue: geographic relationship of numbers▪ In a nomadic as well as VoIP world, substantial geographic portability is

unavoidable▪ Jurisdictions (countries and locals) need to consider how to accommodate and

manage the use effectively