Presentation on theme: "Industry Numbering Committee (INC) Report to the NANC June 7, 2012 Natalie McNamer, INC Chair Dana Crandall, INC Vice Chair."— Presentation transcript:
Industry Numbering Committee (INC) Report to the NANC June 7, 2012 Natalie McNamer, INC Chair Dana Crandall, INC Vice Chair
INC Report to the NANC June 7, INC Meetings INC Meetings: INC held one face-to-face meeting since the last NANC report. –Next INC Meeting: Week of June 25, 2012 (Sterling, VA) Details on all future meetings can be found at:
INC Report to the NANC June 7, Non-Geographic 5YY-NXX Codes (Issues 692 and 702) INC continues to work Issue 692 and Issue 702 to significantly revise the 5YY-NXX Code Assignment Guidelines, including an update of the service description for these resources to better reflect their use for machine-type communications and applications (i.e. M2M). INC is tightening the requirements for SPs to be assigned growth resources by: Requiring SPs to meet 75% utilization before an SP is eligible for growth resources; and Requiring SPs to demonstrate, via monthly forecast data, that existing resources will exhaust within 6 months. As the growth of M2M applications is expected to increase dramatically in the next several years, it is anticipated that the exhaust of the 29 designated 5XX NPAs will accelerate until a long-term solution is developed by standards bodies. INC is monitoring the assignment rate closely to ensure that the negative effects on the life of the NANP are minimized.
INC Report to the NANC June 7, Issue 731: Resolving Conflicts of Duplicate or Overlapping p-ANI Ranges The RNA has identified approximately 270 p-ANI ranges that are reported to be in use by more than one service provider. INC met with the ATIS Emergency Services Interconnection Forum (ESIF) on April 17, 2012, to discuss this issue. It was determined that duplicate assignments can only occur when a p-ANI or p-ANI range is assigned to different service providers routing to different PSAPs through different selective routers. Duplicate assignments could result in a delay of emergency response because: 911 calls could be routed to the wrong PSAP. 911 location information could be incorrect. PSAPs that transfer ALI location and p-ANI information to another PSAP that uses a different selective router could then provide incorrect information to the other PSAP. INC and ESIF have identified steps a service provider would need to take in order to resolve a duplicate or overlapping p-ANI or p-ANI range and notify the RNA. INC and ESIF agreed on a process to resolve the duplicate or overlapping p-ANI or p- ANI ranges, which will require the affected service providers to cooperate to resolve the issue. INC is currently working to determine a timeframe for each of the steps involved in the resolution.
INC Report to the NANC June 7, Issues in Initial Pending Issue 698: Auto-Populate Total Numbering Resources on TBPAG MTE Form Issue 710: NANC Action Item “multi-OCN Issue” Issue 715: Update TBPAG For Retrieving a Block Donated/Returned in Error
INC Report to the NANC June 7, Issues in Final Closure Issue 729: Updates to CIC Assignment Guidelines Issue 732: Update COCAG Part 2 Forms – Form 1, Form 2, Form 6, Form 7, Form 8 and TBPAG Part 2A Form 1
INC Report to the NANC June 7, Relevant INC Web Pages INC Homepage (front page to all INC links): INC Calendar (future meeting logistics/agendas): INC Issues (historical and active): INC Meeting Records: INC Published Documents: