1 / 11

Industry Numbering Committee (INC) Report to the NANC

Industry Numbering Committee (INC) Report to the NANC. October 15, 2009 Adam Newman, INC Chair Natalie McNamer, INC Vice Chair. INC Meetings. INC Meetings: INC held two face to face meetings since the last NANC report. Next INC Meeting: INC 109, December 7-11, 2009

zacharee-horn
Download Presentation

Industry Numbering Committee (INC) Report to the NANC

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 October 15, 2009 Adam Newman, INC Chair Natalie McNamer, INC Vice Chair

  2. INC Meetings • INC Meetings: INC held two face to face meetings since the last NANC report. • Next INC Meeting: INC 109, December 7-11, 2009 Details on all future meetings can be found at: www.atis.org/inc/calendar.asp

  3. NPA SubcommitteeIssue 628 – Clarification of elimination of 7-digit Dialing between states during implementation of an overlay • The NPA Relief Planning Guidelines direct that the use of protected codes (NXXs), which permits 7-digit dialing across NPA boundaries, should be eliminated as part of the NPA code relief planning process unless a state commission has directed otherwise. This direction was added to the guidelines per a 1997 letter from the NANC Chairman to the INC Moderator. • Issue 628 provides further clarification to address protected code arrangements that allow 7-digit dialing from an adjacent NPA, both intra or interstate when an overlay is being implemented. • Issue 628 also provides an expanded definition of the use of protected codes to also include protected routes.

  4. NPA SubcommitteeIssue 628 – Clarification of elimination of 7-digit Dialing between states during implementation of an overlay • A protected code has been defined to be a central office code assigned in one NPA that is not available for assignment in an adjacent NPA in order to permit 7 digit dialing across the NPA boundary. • A protected route has been defined as a route where the local calling scope from one or more rate centers to other rate centers across NPA boundaries permits either 7 or 7 and 10 digit dialing across the NPA boundary. In the case of a protected route with 7 digit dialing, a central office code assigned in one specific geographic area of an NPA is not available for assignment in a specific geographic area of an adjacent NPA, but the code may be assigned outside the identified geographic area of the adjacent NPA or local calling scope.

  5. NPA SubcommitteeIssue 619 – Establish NPA Code Relief Implementation Practices to address the technical and customer education issues during the implementation of an NPA Split or an Overlay • The INC NPA Code Relief Planning and Notification Guidelines provide guidelines for the relief planning process, industry notification process and NANPA’s responsibilities to affected parties and applicable regulatory authorities within the North American Numbering Plan. • The resolution of Issue 619 creates a new Appendix G: Technical Considerations. This Appendix identifies many of the technical activities and their applicability to a split or an overlay, to provide NPA relief implementation guidance to service providers. • The INC discussed inclusion of customer education guidance, but determined that this was best left to the local industry and state commissions.

  6. NPA SubcommitteeIssue 598: Add appropriate references in guidelines to ITU-T Mis-Use documents • The INC has reviewed the ITU-T Recommendation “Guidelines for ITU-T action on reported misuse of E.164 number resources” and the “Best Practice Guide on Countering Misuse Supplement 1” and determined that the information within these documents is relevant to many of the INC number administration guidelines. • A mis-use of an E.164 international numbering resource occurs where the use of that numbering resource does not conform to the relevant ITU-T Recommendation(s) assignment criteria for which it was assigned or when an unassigned numbering resource is used in the provision of a telecommunication service. • Those INC guidelines that involve administration of E.164 number resources, have been updated to reference the ITU-T principles with regard to mis-use of E.164 number resources and to report mis-use to NANPA.

  7. LNPA SubcommitteeIssue 644: Remove Exception For an Additional LRN When a Switch Serves Multiple NPAC Regions • Under Issue 416, INC documented three instances in the Thousands-Block Pooling Guidelines and the LRN Assignment Practices where the PA was allowed to assign an NXX for LRN purposes to an SP when the SP meets the requirements for a block assignment and already has an LRN associated with that particular switch/POI in that LATA. • One of those three instances was a technical limitation where a unique LRN was required for each NPAC region within a single LATA for a single switch serving multiple NPAC regions. • Since that technical limitation no longer exists, the INC agreed to remove the instance from the Thousands-Block Pooling Guidelines and the LRN Assignment Practices to prevent SPs from opening new NXXs for LRN purposes unnecessarily.

  8. Issues Remaining in Initial Pending • Issue 534: The Development of pANI Guidelines • Issue 611: Augmenting the NRUF Verification Procedures • Issue 632: Updates to the Dedicated Code section of the TBPAG and COCAG

  9. Issues in Final Closure • Issue 579: NPA Relief and p-ANI Resources • Issue 598: Add appropriate references in guidelines to ITU-T Mis-Use documents • Issue 592: Changes to the TBPAG and COCAG for Mass Update Modifications • Issue 602: Checking returned block in the NPAC • Issue 619: Establish NPA Code Relief Implementation Practices to address the technical and customer education issues during the implementation of an NPA Split or an Overlay • Issue 622: Enhance TBPAG To Address “Red” Blocks (Verification of Activation in PSTN is Pending) • Issue 623: Enhance TBPAG and COCAG to Address Opening of NXX Codes in NPAC During NPA Splits • Issue 626: Check Porting on All Code Returns • Issue 628: Clarification of elimination of 7-digit Dialing between states during implementation of an overlay • 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)

  10. Issues in Final Closure • Issue 641: Modify CIC Assignment Guidelines by removing Sections 2.3 and 3.2 • Issue 642:  Remove COCUS References in the NPAC Allocation Guidelines, NPAC Relief Guidelines and the TBPAG  • Issue 643:  Add 24x7 Emergency Contact Number to the p-ANI Part 1 Form • Issue 644: Remove exception for an additional LRN when a switch serves multiple NPAC regions • Issue 645: Clarify the PA responsibilities for pool replenishment • Issue 646:  Modify Sections in the Personal Communication Services (PCS) 5YY NXX Code Assignment Guidelines that address implementation intervals • Issue 647: Update CIC Overview Document and Reporting Forms

  11. 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

More Related