September 2025

Committee Reports

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

• ESIF: Emergency Services Interconnection Forum
  • Issue: 0123
  • Title: Update ATIS-0500048 9-1-1 Authority Readiness Guidelines for NG9-1-1 Connectivity
  • Statement: ATIS, in partnership with NENA, drafted the ATIS-0500048 9-1-1 Authority Readiness Guidelines for NG9-1-1 Connectivity. This document provides a description of the FCC NG9-1-1 Transition Order and the Valid Request framework. It includes a practical advice for making Valid Requests, checklists, and technical information. However, this document was based on the Transition Order before it was finally published in the Federal Register, and is framed as preparation for an “early” Valid Request framework. The Commission’s NG911 rules took effect on November 25, 2024, and the document needs to be updated.
  • Resolution:
  • Status: New Issue

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

• INC: Industry Numbering Committee
  • Issue: 1002
  • Title: Update TBCOCAG to Modify Thousands-Block Disconnect Steps in BIRRDS
  • Statement: An action item was taken at the July 2025 CIGRR meeting while discussing CIGRR Issue C333 - Address/Update NXD Disconnect Functionality for Tara Farquhar, Connie Hartman, and Allyson Blevins to bring this issue to ATIS-INC. CIGRR reviewed the current BIRRDS processes where an NXD record for Central Office Codes cannot be disconnected unless NANPA has already disconnected the ACD record. However, that is not the case for a thousands-block NXD records. BIRRDS has no edit as to whether the BCR should be disconnected first nor whether the NXD should be disconnected first. The TBCOCAG currently states that the NXD for a thousands-block should be disconnected prior to the return of the block to NANPA. When an SP or its AOCN disconnects an NXD thousands-block record prior to NANPA processing the return, it can result in a return denial and instead a block transfer. In this case, if the NXD disconnect effective date has passed, the new block assignee, cannot modify the NXD and instead requires a manual process between NANPA and TRA that results in changes to block effective dates and incorrect data being published in the LERG. CIGRR is requesting that the same process be defined in the TBCOCAG for thousands-blocks that applies to CO Codes today. The intent is to ensure that only blocks returned to NANPA are being disconnected in BIRRDS. It will also provide a better cross-check between NXD and BCR disconnects to ensure consistency. If ATIS-INC modifies the TBCOCAG, then CIGRR would request that TRA implement the corresponding restrictions in BIRRDS. Resolution: ATIS-INC updated ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Section 11.1.5 to modify Thousands-Block disconnect steps in BIRRDS to require NANPA to disconnect the BCR prior to the SP disconnecting the NXD as shown in INC-2025-00101R000. This Issue will be in Initial Pending until BIRRDS modifications are implemented.
  • Resolution: ATIS-INC updated ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Section 11.1.5 to modify Thousands-Block disconnect steps in BIRRDS to require NANPA to disconnect the BCR prior to the SP disconnecting the NXD as shown in INC-2025-00101R000. This Issue will be in Initial Pending until BIRRDS modifications are implemented.
  • Status: Initial Pending

  • Issue: 0997
  • Title: Update Section 18 Rate Center Consolidations/Changes of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines with consistency edits and to provide NANPA direction when a rate center consolidation is initiated by the regulator
  • Statement: Section 18 Rate Center Consolidations/Changes of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines only provides direction when a rate center consolidation is initiated by the Service Provider that files a tariff in regulated states and deregulated states. The Maine Public Utilities Commission has initiated a rate center consolidation, the guidelines currently do not address NANPA’s role in a regulatory initiated consolidation. NANPA suggests adding a new section to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines outlining NANPAs role when a regulator initiates a rate center consolidation. In addition, NANPA suggest consistency edits regarding NANPA’s coordination with iconectiv’s Telecom Routing Administration (TRA).
  • Resolution: INC updated ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines to include direction for NANPA when a regulator initiates a rate center consolidation as shown in INC-2025-00054R0002.
  • Status: New Issue

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

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0075
  • Title: ATIS-1000092, Signature-based Handling of Asserted information using toKENs (SHAKEN): Delegate Certificates; ATIS-0300037, NGIIF Intercompany Responsibilities Within the Telecommunications Industry (Revision 2), ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook (Revision 10); and ATIS-0300046, Recommended Notification Procedures to Industry for Changes in Access Network Architecture (Revision 1) IPNNI-2025-00001R005 impacts on NGIIF best practices
  • Statement: Some Service Providers are not implementing newly assigned or modified numbering resources (NPA-NXX or NPA-NXX-X) in accordance with the published Effective Dates in the LERG. Instead of following the industry standard of using BIRRDS/LERG to obtain information on new codes and their Effective Dates for activating and updating routing, these carriers rely on internal processes and timelines. This lack of alignment can lead to inconsistent provisioning across networks, resulting in call completion failures, premature call blocking, and overall disruption to customers and inter-carrier operations.
  • Resolution: NGIIF updated ATIS-1000092, Signature-based Handling of Asserted information using toKENs (SHAKEN): Delegate Certificates; ATIS-0300037, NGIIF Intercompany Responsibilities Within the Telecommunications Industry (Revision 2), ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook (Revision 10); and ATIS-0300046, Recommended Notification Procedures to Industry for Changes in Access Network Architecture (Revision 1) impacts on NGIIF best practices to help ensure consistent implementation, minimize call failures, and support reliable activation of new and modified codes across the industry. Note: ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook contains changes from Issues 0074 and Issue 0075, and will be published with the closure of Issue 0074.
  • Status: Final Closure

  • Issue: 0074
  • Title: Revisions to ATIS-0300106 (Intercarrier Call Completion/Call Termination Handbook) and ATIS-0300116 (NGN Interoperability for SHAKEN)
  • Statement: As the SHAKEN framework evolves to incorporate new identity authentication mechanisms, including the use of delegate certificates defined in ATIS-1000092, it is important to ensure consistency and interoperability across all relevant NGIIF ATIS best practices. Currently, key ATIS documents – ATIS-0300106 (Intercarrier Call Completion/Call Termination Handbook) and ATIS-0300116 (NGN Interoperability for SHAKEN) – do not reference or account for delegate certificate guidance. To support accurate call validation, fraud mitigation, and seamless call termination across networks, these documents should be updated to acknowledge and align with the expanded SHAKEN delegate certificate procedures. This ensures that service providers can appropriately hand identity assertions, enhance trust, and maintain compliance as SHAKEN use cases broaden.
  • Resolution: ATIS-0300106 and ATIS-0300116 have been updated to reference ATIS-1000092, the SHAKEN delegate certificate specification. Note: ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook contains changes from Issues 0074 and Issue 0075, and will be published with the closure of Issue 0074.
  • Status: Final Closure

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

• OBF: Ordering and Billing Forum
  • Issue: 3668
  • Title: Access Service Ordering Guidelines (ASOG) – Change all instances of Telcordia Technologies to “iconectiv®, LLC”
  • Statement: There is a business need to update the legal entity name of Telcordia Technologies to iconectiv®, LLC throughout all ASOG & UOM practices, forms, etc. Resolution: Globally changed all instances of “Telcordia Technologies”, “Telcordia Technologies, Inc”, “Telcordia” to “iconectiv®, LLC”.
  • Resolution: Globally changed all instances of “Telcordia Technologies”, “Telcordia Technologies, Inc”, “Telcordia” to “iconectiv®, LLC”.
  • Status: Final Closure

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0181
  • Title: Add “iat” and “sub” claims to SPC Token and update allowed certificate signature algorithms and curves
  • Statement: STI-CAs verify that the SPC Token has not expired by looking at the “exp” claim. However, STI-CAs have no way of knowing when the SPC Token was issued. This prevents STI-CAs from enforcing stricter policies, for example, that SPC Tokens must be short lived (e.g., 1-day). The STI-PA could include an “iat” claim which would enable STI-CAs to determine if an SPC Token is short lived or not. STI-CAs are required to put the name of the entity they issued the certificate to in the certificate’s subject organization name. However, in practice this name often does not match the name the STI-PA uses to identify the service provider, which causes confusion. If the STI-PA included a “sub” claim in the SPC Token, the STI-CA could use this name which would ensure the names used by the STI-CA and STI-PA match. The STI-PA already collects the name of each service provider.
  • Resolution: This Issue was closed with the publication of ATIS-1000080.v006, which was approved at the IP-NNI TF meeting on September 15, 2025.
  • Status: Final Closure

  For more information, visit the PTSC home page or contact Anna Karditzas.

• SYNC: Synchronization Committee
  • Issue: 0015
  • Title: Resilient timing plans for critical infrastructure operators
  • Statement: Resilient timing plans for critical infrastructure operators to reduce or eliminate the reliance on GPS as a primary source of time and frequency reference for telecommunications networks are needed. The U.S. DOD-operated GPS system has been the subject of interference, both intentional and purposeful, around the globe. Almost daily occurrences of jamming and spoofing are being reported. Telecommunication networks use, almost exclusively, the signals from GPS satellites to generate time and frequency information for cellular mobile and wireline infrastructure. Outages of GPS can disrupt the operational aspects of mobile networks in as few as 30 minutes and outages of more than 72 hours could be catastrophic.
  • Resolution: SYNC developed a technical report, ATIS-0900006, Resilient Timing Architecture for 5G Communications Networks.
  • Status: Final Closure

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

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

NGIIF

• Document Number: ATIS-0300037
• Title: Next Generation Interconnection Interoperability Forum (NGIIF) - Network Routing Resources Educational Document: Intercompany Responsibilities in the Telecommunications Industry
• Type: Revision
• View Here
• Document Number: ATIS-0300046
• Title: Recommended Notification Procedures to Industry for Changes in Network Routing Architecture
• Type: Revision
• View Here

SYNC

• Document Number: ATIS-0900006
• Title: Resilient Timing Architecture for 5G Communications Networks
• Type: New
• View Here

WTSC

• Document Number: ATIS-0700053
• Title: Emergency Location Spoofing Mitigation Study
• Type: New
• View Here

Recent Policy Filings

ESIF, NRSC

• Date: 09/17/2025
• Description: Reply Comments in Response to FCC FNPRM for Facilitating Implementation of Next Generation 911 Services (NG911)
• View filing

INC

• Date: 09/22/2025
• Description: Comments in Response to FCC NPRM for Protecting Consumers from Unauthorized Carrier Changes and Related Unauthorized Charges; Truth-in-Billing and Billing Format
• View filing

SNAC

• Date: 09/23/2025
• Description: Ex Parte Filing re: Assignment of Toll-Free Numbers in the 833 NPA
• View filing

WTSC

• Date: 09/25/2025
• Description: Comments in Response to FCC Eleventh FNPRM for Modernization of the Nation’s Alerting Systems
• View filing