1 / 26

Industry Numbering Committee Report to the NANC - July 16, 2009

This report provides updates on various issues discussed by the Industry Numbering Committee (INC) during their meetings, including Sint Maarten's application to join the NANP, NPA code relief planning guidelines, p-ANI resources, limit test numbers, and NRUF verification procedures.

cnicole
Download Presentation

Industry Numbering Committee Report to the NANC - July 16, 2009

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. Industry Numbering Committee (INC) Report to the NANC July 16, 2009 Adam Newman, INC Chair Natalie McNamer, INC Vice Chair INC Report to the NANC 07/16/2009

  2. INC Meetings • INC Meetings: INC held seven face to face meetings since the last NANC report. • Next INC Meeting: INC 107, August 10-14, 2009 Details on all future meetings can be found at: www.atis.org/inc/calendar.asp INC Report to the NANC 07/16/2009

  3. NPA SubcommitteeIssue 589 – Sint Maarten Application to Join the NANP Per the NPA Allocation Plan and Assignment Guidelines, Sint Maarten applied to the NANPA for admittance to and participation in the NANP on April 18, 2008. The application was submitted to the INC for its review and recommendation. Per the guidelines, NANPA sought input on the application from NANP members and other industry forums. While there was no objection to the application, a number of parties were concerned with the impact to number optimization and NANP exhaust. Some parties suggested that Sint Maarten be asked to share an NPA Code assignment with some future NANP entrant. 3 INC Report to the NANC 07/16/2009

  4. NPA SubcommitteeIssue 589 – Sint Maarten Application to Join the NANP 4 INC Report to the NANC 07/16/2009 • Although Sint Maarten is unlikely to utilize all of the 7.92 million telephone numbers available for assignment in an NPA, the INC could not justify asking Sint Maarten to share an NPA, as sharing an NPA is not currently addressed in the guidelines. • INC determined that the application met all the guideline criteria required for a request received from a country not currently a participant in the NANP.

  5. NPA SubcommitteeIssue 559 – Revise NPA Code Relief Planning Guidelines to address Customer Complaints 5 INC Report to the NANC 07/16/2009 • Implementation of an area code split is one of the most complex endeavors. Due to issues that surfaced as a result of a geographic split, Issue 559 was introduced in order to provide greater detail to the NPA Code Relief Planning and Notification Guidelines. • INC created a new Appendix F: Issues to Be Considered During Relief Implementation, in order to address potential customer issues that the telecommunications industry might experience with the introduction of a new area code whether it is a result of a split or an overlay. • Appendix F contains Table 1 to address an area code split and Table 2 to address an area code overlay. Both tables list potential customer issues, possible causes that can generate these issues, and possible remedies.

  6. NPA SubcommitteeIssue 579: NPA Relief and p-ANI Resources • INC added new guideline language to both the p-ANI Administration Guidelines and the NPA Relief Planning and Notification Guidelines to address required relief planning functions that the Routing Number Administrator (RNA) performs in conjunction with non-dialable pseudo-ANI (p-ANI) assignments. • The functions include tracking p-ANI assignments within NPAs to ensure effective and efficient use of numbering resources, participating in any NPA relief E9-1-1 task force meetings, and providing updates to E9-1-1 Service Providers, Mobile Positioning Centers, VoIP Positioning Centers, Wireless Service Providers and PSAPs when necessary.  • Implementation is pending approval by the FCC of a PA Change Order for permanent p-ANI administration. INC Report to the NANC 07/16/2009

  7. CO/NXX SubcommitteeIssue 577 – Limit Test Numbers to Assigned Blocks • The objective of Issue 577 is to ensure that a Code Holder/LERG assignee establish a test number only from a block that is assigned to or retained by that Code Holder/LERG Assignee, and to prevent test numbers from being assigned to customers. • This issue is associated with Common Interest Group on Rating and Routing (CIGRR) Issue 159 that seeks to implement related edits in Business Integrated Routing and Rating Database System (BIRRDS) to ensure that the test line number is populated with a number within a retained or assigned block. • Text was included in the LRN Assignment Practices and Thousands-Block Pooling Administration Guidelines (TBPAG) to encourage the consolidation of administrative numbers in blocks retained by or assigned to the Code Holder/LERG Assignee, and to require that Service Providers disconnect test numbers and/or LRNs in a block before donating or returning that block. INC Report to the NANC 07/16/2009

  8. CO/NXX SubcommitteeIssue 611: Augmenting the NRUF Verification Procedures • The NRUF Guidelines required modification to improve the verification procedures to ensure that all assigned resources are reported. • The INC made changes to the NRUF Guidelines to clarify SP and NANPA responsibilities for reporting and verification of all allocated codes and blocks. • NANPA submitted Change Order 18 to implement these changes. • The INC determined that no changes to the NRUF Guidelines are required for the reporting of intermediate numbers. INC Report to the NANC 07/16/2009

  9. CO/NXX SubcommitteeIssue 584 – Updates to the p-ANI Guidelines • The FCC requested a change order from the Pooling Administrator (PA) to address permanent p-ANI administration. • A review of the FCC request for the change order by the PA indicated a need for clarification to the guidelines that resulted in this issue. The affected areas in the guidelines included: p-ANI forecast, RNA reporting process, RNA appeals report data, p-ANI pool, references to p-ANI transfers, revisions to Part 1 form to include the type of SP, and revisions to the Part 3 form to include a section to withdraw request for p-ANI. • The INC, with input from ATIS ESIF, clarified and modified the p-ANI Administration Guidelines and attachments. • The PA also has submitted questions on several issues to the FCC. Responses to those questions and the submittal of the change order are still outstanding. • The PA plans to submit a change order with a number of assumptions regarding the issues raised with the FCC. INC Report to the NANC 07/16/2009

  10. CO/NXX SubcommitteeIssue 596 – Request to set aside a new NXX for p-ANI Administration • Because the permanent p-ANI administration is not in place, the RNA can not maintain accurate and complete forecast and inventory information. Therefore the RNA cannot determine the nearness of p-ANI exhaust in various NPAs. It is prudent for the RNA to have the next NXX available should exhaust of NPA-211 and NPA-511 be imminent. • After receiving concurrence from the ATIS ESIF, INC determined that there were no reasons that would preclude the use of the 311 NXX and set aside the 311 NXX as the next p-ANI resource. INC Report to the NANC 07/16/2009

  11. CO/NXX SubcommitteeIssue 627: Update Section 5.7 of the p-ANI guidelines to include steps for notification of a new NXX as outlined in correspondence from ESIF (ESIF-2008-034) • As a follow up to INC Issue 596, the INC worked with the ESIF to determine what is necessary for the RNA to implement the next p-ANI resource (NXX) 311. • The RNA will notify all applicable parties no less than 12 months prior to the implementation of a new p-ANI NXX in the US and Puerto Rico. • The INC added this guidance to the Permanent P-ANI Guidelines. INC Report to the NANC 07/16/2009

  12. CO/NXX SubcommitteeIssue 591 – Change Timeline of Part 1/Part 3 Processing for NANPA • Implementation of the PAS-NAS interface enabled submission of this issue that reduced the NANPA processing time from 14 to 7 calendar days. • INC updated the COCAG and TBPAG to reflect the reduction in processing time. • In addition, INC added a checkbox to the Part 1 and Part 1A which allows SPs to indicate a request for the earliest standard Effective Date. INC Report to the NANC 07/16/2009

  13. LNPA SubcommitteeIssue 407: Treatment of Dedicated Codes for Single Customers in a Pooling Environment • Issue 407 had been in Initial Pending since the FCC rejection of the related NANPA Change Order and the NANC recommendation for a rule change. • While Issue 407 was in Initial Pending, the following INC Issues were resolved and actions have occurred which have addressed all but one of the items in Issue 407: • Issue 440: resulted in COCAG and TBPAG changes that gave SPs the option to request an NXX be marked as non-pooled in BIRRDS in the case of a dedicated code in a pooling environment • Issue 522: resulted in COCAG and TBPAG changes that gave SPs the option to submit the Part 4 in service confirmation form directly to the NANPA in the case in which a code is classified as non-pooled for a dedicated customer in a pooling environment • In June 2008, the PAS-NAS interface was implemented. In addition, the ability for SPs to enter Part 1 and Part 4 forms directly into the PAS system was implemented in February 2008. Together these replace the former requirement for an SP to manually fill out a form and fax/e-mail it to the PA for forwarding to the NANPA, which had added PA processing time to NANPA processing time • Issue 591 reduced the NANPA processing time from 14 to 7 calendar days. • As a result, the adverse impact of requiring pooling SPs to submit all applications to the PA is minimized and Issue 407 was resolved with no guideline changes. INC Report to the NANC 07/16/2009

  14. LNPA SubcommitteeIssue 585 – Blocks with Over 10% Contamination • INC developed a new process that helps remove over-contaminated blocks from the pool when such blocks are identified in the pool. • When a block is identified as being more than 10% contaminated, the PA shall find a new block holder for the over-contaminated block, and shall not place the over-contaminated block in the pool. • If the contaminating ports belong to only the LERG Assignee, the PA shall ask the LERG Assignee to place the block back into its inventory. • If the contaminating ports belong to multiple service providers, the PA shall ask the service provider with the most ports to become the new block holder. • If the service provider with the most ports does not submit a Part 1A to become the new block holder, the PA shall ask all service providers with contaminating ports to submit a Part 1A to become the new block holder. • If no service provider with contaminating ports submits a Part 1A to become the new block holder, the PA shall ask the appropriate regulatory authority to approve, within 30 days, the disconnect of all contaminating ports so that the PA may place the pristine block back in the pool. INC Report to the NANC 07/16/2009

  15. LNPA SubcommitteeIssue 602 – Checking Returned Block in the NPAC • To prevent a returned block that is more than 10% contaminated from being placed into the pool, the PA shall request an NPAC ad hoc report to determine the contamination level of every returned block. • Service Providers exiting the market may return over-contaminated blocks so that the PA can find a new block holder. • Service Providers not exiting the market may not return over-contaminated blocks; the PA shall deny the return. • The INC requested and the NAPM LLC approved the PA receiving Ad Hoc reports from NPAC for all returned blocks. • This new proactive process helps eliminate over-contaminated blocks from being placed into the pool. INC Report to the NANC 07/16/2009

  16. LNPA SubcommitteeIssue 614: Handling Block Reservations in Jeopardy Situations • Service providers may reserve a thousands-block only when seeking a safety valve waiver. • The Thousands-Block Pooling Guidelines did not specify how thousands-block reservations should be addressed when an NPA is declared in jeopardy. • In most jeopardy situations, NXX codes are set aside for the PA and are not subject to NXX code lotteries or rationing, and all NXX code reservations are cancelled automatically. • INC agreed that because block reservations are limited, the PA should maintain block reservations during a jeopardy situation. • INC added text to the Pooling Guidelines to allow block reservations to be maintained during a jeopardy situation. INC Report to the NANC 07/16/2009

  17. INC VoIP SubcommitteeIssue 497: Identify Potential Changes to INC Guidelines Based on NANC’s Report and Recommendation • Per the NANC action item, INC reviewed the NANC’s report (VoIP Service Providers’ Access Requirements for NANP Resource Assignments – NANC Report and Recommendation by the Future of Numbering Working Group – July 2005) and crafted changes to relevant sections within four INC documents that may require modifications should the FCC issue an order addressing VoIP provider access to numbers. • INC also reached out to other ATIS committees asking them to do the same. • In June 2008, INC tabled this Issue until action is taken by the FCC. INC Report to the NANC 07/16/2009

  18. Issues Remaining in Initial Pending • Issue 534: The Development of pANI Guidelines • Issue 592: Changes to the TBPAG and COCAG for Mass Update Modifications • Issue 602: Checking returned block in the NPAC • Issue 611: Augmenting the NRUF Verification Procedures • Issue 628: Clarification of elimination of 7-digit Dialing between states during implementation of an overlay INC Report to the NANC 07/16/2009

  19. Issues in Initial Closure • Issue 579: NPA Relief and p-ANI Resources • Issue 623: Enhance TBPAG and COCAG to Address Opening of NXX Codes in NPAC During NPA Splits • Issue 632: Updates to the Dedicated Code section of the TBPAG and COCAG • Issue 633: Remove NRUF reporting process from the TBPAG • Issue 634: Clarify transfer section regarding mutually agreed to transfers • Issue 635: Clarify which NENA ID should be used by p-ANI applicants • Issue 640: Amend the 555 In-Service Certification Form (Part 3) INC Report to the NANC 07/16/2009

  20. Issues in Final Closure • Issue 407: Treatment of Dedicated Codes for Single Customers in a Pooling Environment • Issue 510: Internet-Based Relay Services and Interoperability • Issue 555: Change to the PCS 5YY NXX Part C Code Confirmation of Code Activation Form • Issue 556: Change to the Part C Confirmation of 900-NXX Code In Service Form • Issue 557: Edit Section 4.1 of COCAG Appendix C-Voluntary Return of Pooled NXX Codes Containing Assigned Blocks/Ported Numbers • Issue 559: Revise NPA Code Relief Planning Guidelines to address Customer Complaints • Issue 560: Miscellaneous Edits to NPA Code Relief Planning and Notification Guidelines • Issue 563: Update PA Change Order Timeline • Issue 566: Changes to PAR – Election Nomination Process • Issue 567: Changes to Footnote #9 (Section 3.1) in the CIC Assignment Guidelines • Issue 568: Update the Uniform Dialing Plan Document and Attachment “A” and “B” INC Report to the NANC 07/16/2009

  21. Issues in Final Closure (cont) • Issue 569: LRN Data for NANPA & PA To Process Voluntary Code Returns or Abandoned Codes • Issue 570: Update the INC Guidelines as needed as a result of FCC 07-188 Order, Declaratory Ruling and Order on Remand related to Number Portability • Issue 571: INC Form Changes to synchronize with the release of the new PAS • Issue 572: Update the TBPAG to reflect the TRD requirement that the Part 1B form not be required for pooled CO code requests • Issue 573: Handling Block Transfers When Blocks Are in Reclamation • Issue 574: Update the pooling milestones to include supplemental pooling • Issue 575: Review INC Documents (last update for each documents from 1995 – 1999) to determine whether it is appropriate to leave on the INC Documents web page • Issue 576: Amend TBPAG to Clarify Double-Assignment of Pooled TNs • Issue 577: Limit Test Numbers to Assigned Blocks • Issue 578: Update TBPAG to Limit Timeframe for Block Reservations • Issue 580: Clarification on Block Exchanges • Issue 581: Correct language consistency in the COCAG and COCAG Appendix C relative to active ports, pending ports, and BIRRDS references INC Report to the NANC 07/16/2009

  22. Issues in Final Closure (cont) • Issue 582: Update all references to Intra-Service Provider Ports in the TBPAG and COCAG Appendix C to match the glossary term • Issue 583: Update MTE Form to clarify excluded numbers • Issue 584: Updates to the p-ANI Guidelines • Issue 585: Blocks with Over 10% Contamination • Issue 586: Add PSTN Acknowledgement to the Part 1A Form • Issue 587: Revise NPA Relief Planning Guidelines to address posting a planning letter to the NANPA website after a regulatory change order is issued • Issue 588: Amend Section 2.14 of the COCAG Appendix C • Issue 589: Sint Maarten Application to Join the NANP • Issue 590: Discrepancy Between COCAG Appendix B (MTE) & NAS Instructions • Issue 591: Change Timeline of Part 1 / Part 3 Processing for NANPA • Issue 593: Clarify COCAG Appendix C Sections 2.11 and 2.12 • Issue 594: Update to the Non-pooled Dedicated Customer Request Process • Issue 595: Specify that test numbers are non-charge • Issue 596: Request to set aside a new NXX for p-ANI Administration • Issue 597: Revise CO Code (NXX) Assignment Guidelines to address use of the home NPA-NXX Code INC Report to the NANC 07/16/2009

  23. Issues in Final Closure (cont) • Issue 599: Updates to the block reservation process • Issue 600: Clarify voluntary return of over contaminated blocks • Issue 601: NIIF Proposals to modifications to INC Definitions • Issue 603: Revise COCAG to address notification of NPA data sent to TRA • Issue 605: Clarify Block Expedites in TBPAG • Issue 606: Amendments to Section 7.2 of the CO Code (NXX) Guidelines • Issue 607: Update 900 NXX Code Assignment Guidelines with 9YY to be consistent with the Personal Communications Service (PCS) 5YY NXX Code Assignment Guidelines • Issue 608: Notification to SMS/800 Help Desk of ANI conversion completion for NPA Split • Issue 609: Remove reference to the exceptions of the 75% Utilization threshold • Issue 610: Update Reclamation direction in TBPAG • Issue 612: Submission of NPA Split List to NECA • Issue 613: Notification of an SP missing the Part 4 Due Date • Issue 614: Handling Block Reservations in Jeopardy Situations • Issue 615: Updating TBPAG for Notifications for Rate Center Consolidations • Issue 616: Updating Section 7.4.3 of the TBPAG deleting reference to NXX codes INC Report to the NANC 07/16/2009

  24. Issues in Final Closure (cont) • Issue 617: Update Assignment Practices in the TBPAG to Remove Tandem Homing ID References • Issue 618: Update Section 9.2.4 of the TBPAG removing language for returned blocks • Issue 620: Update PAR to clarify various procedures including document production process • Issue 621: Clarify TBPAG Section 2.18 • Issue 624: Clarify TBPAG block activation timeframes • Issue 625: Update transfer sections of TBPAG to include initial resource documentation • Issue 627: Update Section 5.7 of the p-ANI guidelines to include steps for notification of a new NXX as outlined in correspondence from ESIF (ESIF-2008-034) • Issue 629: The addition of the terms NECA and NECA Tariff FCC No. 4 to glossaries in INC documents • Issue 631: Addition of terms to P-ANI Administration Guidelines • Issue 636: Clarify that each NPA will be a separate p-ANI pool even in overlay situations INC Report to the NANC 07/16/2009

  25. Issues in Final Closure (cont) • Issue 637: Update the definition of p-ANI In Use Deadline • Issue 638: Amend CIC Assignment Guidelines to Require Submission of CIC Activation Form • Issue 639: Amend CIC Assignment Guidelines to specify that CIC must be put into service within 6 months from assignment date (Sections 4.1, 6.1 and 6.2) INC Report to the NANC 07/16/2009

  26. Relevant INC Web Pages • INC Homepage (front page to all INC links): http://www.atis.org/inc/index.asp • INC Calendar (future 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/docs.asp INC Report to the NANC 07/16/2009

More Related