Industry Numbering Committee (INC) Report to the NANC

Industry Numbering Committee (INC) Report to the NANCDyan Adams, INC Co-ChairShaunna Forshee, INC Co-Chair

September 18, 2013

INC Report to the NANCSeptember 18, 2013

2

About INC• The Industry Numbering Committee (INC)

provides an open forum to address and resolve industry-wide issues associated with planning, administration, allocation, assignment and use of North American Numbering Plan (NANP) numbering resources within the NANP area.


3

INC Meetings/Membership• Meetings

• Since the previous NANC meeting, INC held one virtual meeting on July 15, 2013 and one face-to-face meeting on August 20-22, 2013

• The next INC meeting will be held in Overland Park, KS on October 8-10, 2013

• Details on all future meetings can be found at: http://www.atis.org/inc/calendar.asp

• Membership• To become a member of INC or ATIS, see

http://www.atis.org/membership/become.asp.• To understand how INC operates, see

http://www.atis.org/legal/OP.asp

http://www.atis.org/inc/calendar.asp

http://www.atis.org/membership/become.asp

http://www.atis.org/legal/OP.asp


4

Issue 740: Allow pooled NXXs with ports to be returned via PAS (when there are blocks assigned to other SPs)• To facilitate the return of pooled codes in a process that is

efficient and consistent for SPs, INC agreed to allow a code holder to return a pooled NXX code when the code holder has ported TNs but no blocks, and blocks are assigned to other SPs.• The PA will solicit a new code holder from the existing

block holders.• If no block holder submits a Part 1 application to become

the new code holder, the PA will solicit a new code holder from the SPs with ported TNs within the code.

• If no block holder or SP with ported TNs submits a Part 1 application, the NXX code return will be denied, rather than NANPA involving a state commission.

• INC made edits to the CO Code Assignment Guidelines Appendix C (Procedures for Code Holder Exit) and the Thousands-Block Pooling Administration Guidelines to outline these changes as well as to clarify existing language.


5

Issue 748: Assess Impacts on Numbering Resources and Numbering Administration with Transition from Public Switched Telephone Network (PSTN) to Internet Protocol (IP)

• INC discussed that, during the convergence to IP, there is a need to maintain existing infrastructures and numbering databases while also developing modifications, creating new systems and databases.

• ATIS filed comments in response to the FCC’s Public Notice in GN Docket No. 13-5, Technology Transitions Policy Task Force Seeks Comment on Potential Trials, identifying INC guidelines that need to be considered and followed in the VoIP trials and to ensure that the migration to IP takes into account current systems and processes.


6

Issue 748: Assess Impacts on Numbering Resources and Numbering Administration with Transition from Public Switched Telephone Network (PSTN) to Internet Protocol (IP) (cont.)• INC discussed the proposed concept of a “Just In Time” (JIT)

numbering trial where SPs and Over the Top (VoIP) providers could obtain numbers at less than thousands block level using LNP.

• Discussion points included developing requirements for JIT numbering, assignment and provisioning timelines, establishment and replenishment of the number pool, NRUF and forecasting reports, and auditing.

• INC is developing potential guidelines, which could be used in the event that the JIT numbering concept is approved for trial.

• INC reviewed recent developments in the VoIP direct access to numbering trial, to assess the timeline of the trial and any impacts to INC guidelines.


7

Issue 758: Move the 550, 535, 536, 546, and 558 NPAs from the General Purpose Category to Set Aside for Future Non-Geographic 5XX-NXX Use• In May 2011, INC agreed to direct NANPA to set aside the 52X, 53X, 54X, and

55X series for future non-geographic 5XX-NXX code use. At that time, the 550 NPA was not available because it had been reserved to relieve a geographic NPA exhausting within 10 years, but subsequently became available. Under Issue 758 INC agreed also to set aside 550, 535, 546, and 558 NPAs for future non-geographic 5XX-NXX use.

• INC originally wanted to set aside 536; however, NANPA determined the 536 NPA is the only option for relief of a specific geographic NPA because all 187 other available NPAs would result in the need for implementation of timing delays.

• Although NPA overlays generally allow the most efficient use of resources, the complexity involved in determining relief NPAs to prevent the need to implement timing delays highlights how cross boundary 7-digit dialing for protected routes can negatively impact that efficiency. Although the introduction of an NPA overlay requires10D dialing for calls originating in the overlay, it does not necessarily mean incoming calls are dialed on a 10D basis due to the continued use of protected routes permitting 7D cross NPA dialing. Protected routes limit the availability of CO codes in relevant geography for the NPA relief area, hastening NPA exhaust.

• The practice of permitting 7D dialing into another NPA may continue unless regulatory action is taken directing all calls into and out of NPAs be on a 10D (or 1+10D) basis.


8

Issue 760: Add Clarifications to NPA Relief Planning Guidelines for Interested Party Terms and for Determining Consensus

• The NPA Relief Planning Guidelines includes terms that seem related: affected parties, members of the industry, industry participants, and interest groups.

• INC edited the guidelines to clarify that only Affected Parties have a voice considered by NANPA when determining consensus.

• Affected Parties are:• A Service Provider with resources assigned in the affected

NPA, and/or • A Service Provider with no resources assigned yet but

authorized to provide service in the affected NPA • INC modified the definition of Consensus to specify that:

• A Service Provider Consultant participating on behalf of a particular Service Provider shall identify the Service Provider it is representing as an Affected Party and have a voice in the consensus determination

• Those participating that are not Affected Parties may express views, but do not have a voice in the consensus determination


9

Issues in Initial Pending• Issue 692: Update the 5YY requirements for

resources• NANPA Change Order #1 implementation expected

on September 27, 2013• Issue 702: Update Service Description for

Use of 5YY Resources• NANPA Change Order #1 implementation expected

on September 27, 2013


10

Issues in Initial Closure• Issue 740, Allow pooled NXXs with ports to be

returned via PAS (when there are blocks assigned to other SPs)

• Issue 758, Move the 550 NPA from the General Purpose Category to Set Aside for Future Non-Geographic 5XX-NXX Use

• Issue 760, Add Clarifications to NPA Relief Planning Guidelines for Interested Party Terms and for Determining Consensus

• Issue 761, Updates to the PAR regarding pooling related issues in Initial Closure


11

Issues in Final Closure• Issue 756, Change the title of the annual RNA

report in Section 5 to the “p-ANI Activity and Exhaust Report”


12

Relevant INC Web Pages• INC Homepage (front page to all INC links):

http://www.atis.org/inc/index.asp• INC Upcoming Meetings (meeting logistics/agendas):

http://www.atis.org/inc/calendar.asp• INC Issues (historical and active):

http://www.atis.org/inc/incissue.asp• INC Meeting Records:

http://www.atis.org/inc/mtgs_current.asp• INC Published Documents:

http://www.atis.org/inc/incguides.asp• Anyone interested in information on INC or INC

documents can contact Jackie Voss, ATIS INC Manager, via email at [email protected] or (913)393-0891

http://www.atis.org/inc/index.asp

http://www.atis.org/inc/calendar.asp

http://www.atis.org/inc/incissue.asp

http://www.atis.org/inc/mtgs_current.asp

http://www.atis.org/inc/incguides.asp