June 2024

Committee Reports

Click on a committee name below to display this month's issues.

• INC: Industry Numbering Committee
  • Issue: 0979
  • Title: Update the ATIS-0300068, North American Numbering Plan Numbering Utilization/Forecast Guidelines for the combined NANP Administration System (NAS)
  • Statement: A few changes need to be made to ATIS-0300068, North American Numbering Plan Numbering Utilization/Forecast (NRUF) Guidelines to align with changes in the combined NANP Administration System (NAS). These changes include: • Changing references of PA to NANPA or Thousands-Block Pooling (as appropriate) • NXX to Central Office (CO) Code (NXX) or CO Code (NXX) as appropriate • Capitalized glossary terms to align with other guidelines • Spelled out first instance of acronyms
  • Resolution:
  • Status: New Issue

  • Issue: 0980
  • Title: Update the ATIS-0300061, NPA Code Relief Planning and Notification Guidelines for the combined NANP Administration System (NAS)
  • Statement: A few changes need to be made to ATIS-0300061, NPA Code Relief Planning and Notification Guidelines to align with changes in the combined NANP Administration System (NAS). These changes include: • Changing references of PA to NANPA (as appropriate) • NXX to Central Office (CO) Code (NXX) or CO Code as appropriate • Block to Thousands-Block • Capitalized glossary terms to align with other guidelines • Spelled out first instance of acronyms to align with other guidelines
  • Resolution:
  • Status: New Issue

  • Issue: 0981
  • Title: Update the ATIS-0300055, NPA Allocation Plan and Assignment Guidelines for the combined NANP Administration System (NAS)
  • Statement: A few changes need to be made to ATIS-0300055, NPA Allocation Plan and Assignment Guidelines to align with changes in the combined NANP Administration System (NAS). These changes include: • Changing references of PA to NANPA (as appropriate) • NXX to Central Office (CO) Code (NXX) or CO Code as appropriate • Capitalized glossary terms to align with other guidelines • Spelled out first instance of acronyms to align with other guidelines
  • Resolution:
  • Status: New Issue

  • Issue: 0982
  • Title: Update the ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) for the combined NANP Administration System (NAS)
  • Statement: Several changes need to be made to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG) to align with changes in the combined NANP Administration System (NAS). These changes include: • Updating form name references as agreed to by INC • Changing references of PA to NANPA (as appropriate) • Updating all processing times to 7 calendar days • Remove need for appendix 2 for an Initial Dedicated Customer (Issue 920) • Update language relating to cancellation of Thousands-Blocks and CO Codes (Issue 918) • Modifying Section 13 Intra-Service Provider (ISP) Block Porting to align with changes to processing in the combined NAS and Initial Pending issues (Issue 913 and Issue 927)
  • Resolution:
  • Status: New Issue

  • Issue: 0983
  • Title: Update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office (CO) Code (NPA-NXX) Administration Guidelines (TBCOCAG) To Make Disconnected Thousands-Blocks Available for Reassignment After 30 Calendar Days
  • Statement: Today when a service provider returns/donates a thousands-block to the pool and NANPA approves it, NANPA adds the thousands-block to the pool inventory immediately, but with a future “Block Available Date” that must be at least 45 calendar days after the thousands-block’s disconnect effective date entered on the Part 3 approval. This 45-day timeframe is documented in section 11.1.11.5 of the Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines. The 45-day timeframe exists to give the code holder time to make translations updates, if needed, to provide vacant number treatment for the numbers within that thousands-block while the block is in the pool. It is unclear whether code holders still make such translations updates, but all monthly LERGTM Routing Guide recipients can subscribe to the LERGTM One-Day Changes Process at no additional charge. Reducing the 45 calendar days timeframe down to 30 calendar days will make thousands-blocks available for reuse more quickly.
  • Resolution:
  • Status: New Issue

  • Issue: 0984
  • Title: Remove language in Section 11.2.12.2.2 of the TBCOCAG allowing SPs with only ported TNs to become the new CO Code holder when there are block holders in the impacted CO Code
  • Statement: Section 11.2.12.2.2 subsections g-l allow for Service Providers (SPs) with only ported TNs to become the new CO Code Holder if no block holder responds to NANPA’s request for a new Code Holder. Since a SP becoming a Code Holder must fulfill code holder responsibilities it falls on the block holders to submit the Part 1 to NANPA. A SP may not be able to obtain a block in the resource and therefore cannot fulfill the applicable responsibilities.
  • Resolution:
  • Status: New Issue

  • Issue: 985
  • Title: Add language to Section 11.2.12.1.1 of the TBCOCAG allowing for a Service Provider (SP) to bypass Utilization & MTE requirements for a thousands-block when certain conditions are met due to a CO Code Transfer
  • Statement: Section 11.2.12.1.1 of the TBCOCAG allows SPs with only ported TNs to become the CO Code Holder when there are no block holders. If a SP with ported TNs agrees to become the Code Holder, they are subject to default routing requirements and other Code Holder responsibilities. Since the new SP does not have a block in the transferred CO Code they are subject to utilization and MTE requirements to obtain a thousands-block to fulfill code holder responsibilities. For example, without a block the new SP cannot assign a test TN to ensure default routing is working properly.
  • Resolution:
  • Status: New Issue

  • Issue: 0969
  • Title: Updates to ATIS-0300060 9YY NXX Code Assignment Guidelines and forms for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-03000060, 9YY NXX Code Assignment Guidelines, the 9YY NXX Code Application Form – Part 1 to align with the combined NANP Administration System (NAS): • Update processing times to 7 calendar days • Update form references to new form names • Update the 9YY NXX Code Application Form Part 1 to remove Explanation field
  • Resolution: INC agreed to update ATIS-0300060 9YY NXX Code Assignment Guidelines and forms for the combined NANP Administration System, with the changes reflected in INC-2024-00013R00X and INC-2024-00014R001. This Issue will be in Initial Pending until the implementation of the combined NAS.NANPA has notified INC that Section 10.4.6 Alternate Data Capabilities of the TRD corresponds with the updates reflected in this Issue.
  • Status: Initial Closure

  • Issue: 0970
  • Title: Updates to ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines to align with the combined NANP Administration System (NAS): • Update processing times to 7 calendar days • Update form references to new form names
  • Resolution: INC agreed to update ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines with the changes reflected in INC-2024-00016R003. This Issue will remain in Initial Pending until the implementation of the combined NAS. NANPA notified INC that the 10.4.6 Alternate Data Capabilities section of the TRD corresponds with the accepted changes.
  • Status: Initial Closure

  • Issue: 0951
  • Title: Review the Unassignable Special Use NXXs in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines
  • Statement: The NANC’s Report and Recommendation on the Feasibility on ITN Pooling Trials and Alternative Means for Conserving Numbering Resources (Feb 2023) recommends: “ATIS’ Industry Numbering Committee (INC) (and other ATIS committees as needed) should review all unassignable special use NXX codes to determine if any can be released now, and/or if nationwide 10-digit dialing is implemented.”
  • Resolution: INC reviewed the unassignable special use NXXs in ATIS-0300119, TBCOCAG and provided the NAOWG with a recommendation given their findings and numbering expertise. This recommendation can be found as INC-2024-00065R003.
  • Status: Final Closure

  • Issue: 0971
  • Title: Updates to ATIS-0300089, p-ANI Administration Guidelines for the combined NANP Administration System (NAS)
  • Statement: NANPA has identified the following changes to ATIS-0300089, p-ANI Administration Guidelines to align with the combined NANP Administration System (NAS): • Update processing times to 7 calendar days • Update system to NAS and website to nanpa.com
  • Resolution: INC agreed to update ATIS-0300089, p-ANI Administration Guidelines for the combined NANP Administration System, with the changes reflected in INC-2024-00018R004. This Issue will be in Initial Pending until the implementation of the combined NAS. NANPA has notified INC that Section 10.4.6 Alternate Data Capabilities of the TRD corresponds with the updates reflected in this Issue.
  • Status: Initial Pending

  For more information, visit the INC home page or contact .

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0072
  • Title: Additions to ATIS-0300116 of Other Fraud Prevention Obligations
  • Statement: There is a need to update ATIS-0300116, Interoperability Standards between Next Generation Networks (NGN) for Signature-based Handling of Asserted information using ToKENs (SHAKEN). These updates will consist of RMD additions, STI-GA policy links, Certificate Authority links, and references to the IP Interconnection CATA Working Group document.
  • Resolution: ATIS-0300116, Interoperability Standards between Next Generation Networks (NGN) for Signature-based Handling of Asserted information using ToKENs (SHAKEN) was updated with RMD additions and STI-GA policy links.
  • Status: Initial Closure

  For more information, visit the NGIIF home page or contact Mignot Asefa.

• OBF: Ordering and Billing Forum
  • Issue: 3667
  • Title: Access Service Ordering Guidelines (ASOG) – Expand the Error Message field (Practice 10) an additional 60 characters
  • Statement: There is a business need to expand the ERROR MESSAGE field from the current 120 alphanumeric characters to 180 alphanumeric characters to allow for additional text/information being sent to the customer to better explain the reason for the ERROR MESSAGE.
  • Resolution:
  • Status: New Issue

  • Issue: 3666
  • Title: Modify the New Local Service Provider (NLSP) and Old Local Service Provider (OLSP) Valid values
  • Statement: When the WICIS specifications were first agreed to the goal was for every network service provider to eventually have their resellers (MVNOs) obtain a valid OCN to be used in the NLSP and OLSP fields. For those MVNOs who were not able to obtain a valid OCN it was agreed that a generic code of ZZZZ could be used. Today: Almost no wireless carrier has required their MVNOs to obtain an OCN and thus utilize the generic code of ZZZZ to populate the NLSP field on a port in request and the OLSP field on a port out response. Due to some service provider system limitations and the inability for resellers/MVNOs to obtain more than one OCN per company category, the ability to use ZZZZ for multiple MVNOs doesn’t always work. Additionally, the use of a single generic code doesn’t allow for the segregation of port requests across different MVNOs within a single network provider.
  • Resolution: Modified the data dictionary definition Valid Values for the NLSP and OLSP data elements.
  • Status: Initial Closure

  For more information, visit the OBF home page or contact Drew Greco.

• SNAC: SMS/800 Number Administration Committee
  • Issue: 3444
  • Title: Review and Update ATIS-0417001-004, Industry Guidelines for Toll-Free Number Administration
  • Statement: It has been brought to SNAC’s attention that the ATIS-0417001-004, Industry Guidelines for Toll-Free Number Administration’s glossary is out of date. The SNAC will review the document and glossary, and make updates as needed.
  • Resolution:
  • Status: New Issue

  For more information, visit the SNAC home page or contact .

Definitions

• New Issue: Business, operational, or technical needs that a committee has reached consensus to address.
• Issue in Initial Closure: Issues for which a committee has reached consensus on a proposed resolution. The industry has a 21 calendar day period to review and comment on the consensus resolution developed by the committee. The committee's consensus resolution concludes its work on an issue unless new or substantive information is brought forth. During the 21 day review period, comments on a consensus resolution may be provided to the committee contact and committee leaders.
• Issue in Initial Pending: Issues previously in Initial Closure for which new and substantive information impacting the consensus resolution has been received. An issue may also be in Initial Pending if output that may impact the consensus resolution is expected from another industry group, regulatory body or similar organization.
• Issue in Final Closure: Issues for which work is completed and the resolution accepted by the industry.

Recently Approved ATIS Standards

No new Standards approved this month.

Recent Policy Filings

WTSC

• Date: 06/12/2024
• Description: Comments in response to proposed rule on specific mechanisms to implement multilingual Wireless Emergency Alerts (WEA)
• View filing