February 2026

Committee Reports

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

• ESIF: Emergency Services Interconnection Forum

  • Issue: 0120
  • Title: NG911 Text Messaging
  • Statement: Emergency services in the United States require a standards-compliant NG911 solution that allows individuals to request help through voice calls, text messages, or other multimedia. Existing solutions for requesting emergency assistance via text in the United States rely on the interim J-STD-110.v002 standard, which defines the Joint ATIS/TIA requirements and architecture for native SMS/MMS Text-to-911. The advent and growing adoption of NG911 voice delivery mark a pivotal moment for modernizing emergency communications. With NG911 deployments now supporting IP-based, standards-compliant voice calls, the time is right to evolve the delivery of all multimedia emergency requests—starting with text messaging. Leveraging 3GPP and NG911 standards ensures that emergency text and other multimedia communications, such as images, video, and real-time data sharing, are as seamless, reliable, and interoperable as voice. As NG911 text messaging evolves, specifications and solutions are needed to ensure seamless backward compatibility with interim SMS Text-to-911. Interim Text-to-911 implementations rely on Text Control Centers (TCCs) as defined in the J-STD-110.v002 architecture, which serve as gateways for message delivery to PSAPs. To maintain reliable emergency communication during the transition to full NG911 deployment, new solutions must continue support interoperability with both legacy E911 and NG911 infrastructures, ensuring that all text messages are properly routed, received, and processed by Public Safety Answering Points (PSAPs) without service degradation.
  • Resolution: Publication of ATIS-0700015.v006, ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination.
  • Status: Final Closure

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

• INC: Industry Numbering Committee

  • Issue: 1011
  • Title: Update INC Guidelines (ATIS-0300119, ATIS-0300070) stating Service Providers to verify numbering resources prior to assigning telephone numbers
  • Statement: The current ATIS-03000119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines states service providers should check NPAC prior to assigning telephone numbers from contaminated thousands-blocks. NANPA suggests updating the language in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines and adding language to ATIS-0300070, Guidelines for the Administration of Telephone Numbers stating service providers should verify it is the Thousands-Block Holder prior to opening a new resource for assignment and check NPAC for ported TNs prior to assigning telephone numbers to assist in the prevention of double assignments.
  • Resolution:
  • Status: New Issue

  • Issue: 1012
  • Title: Update TBCOCAG Mass Modification Process to Exclude BIRRDS Updates
  • Statement: Currently, the TBCOCAG requires that the Service Provider (or its AOCN) provide TRA with a spreadsheet from NANPA to have BIRRDS ACD and BCR records updated based on a Mass Modification submitted via NAS. Now that NANPA has implemented a mechanized interface from NAS to BIRRDS eliminating NANPA manual data entry into BIRRDS, ACD and BCR record updates based on a Mass Modification should use the mechanized interface to BIRRDS. Service Providers should no longer be required to request that TRA process a utility for the ACD and BCR updates.
  • Resolution:
  • Status: New Issue

  • Issue: 1013
  • Title: Clarification of Service Provider Responsibilities When Assuming CO Code Holder Status Due to Ported Telephone Numbers
  • Statement: This Issue seeks to clarify how numbering assignment criteria and regulatory waiver processes should be addressed when CO Code Holder status results from ported TN reassignment rather than voluntary resource request. When a Service Provider becomes a CO Code Holder due to abandonment of a pooled or non-pooled CO Code with ported TNs, the TBCOCAG describes the procedural reassignment steps but does not address potential conflicts with standard numbering assignment criteria. An SP assuming CO Code Holder status under these circumstances may: Be required to seek state commission waiver or to obtain additional Thousands-Blocks or CO Codes necessary to perform CO Code Holder responsibilities due to not meeting Months-to-Exhaust (MTE) or 75% utilization thresholds required for Growth assignments. Sections 12 (Abandoned Numbering Resources) and 19.2 (Safety Valve Process) may need modifications
  • Resolution:
  • Status: New Issue

  • Issue: 1014
  • Title: Create a single combined INC glossary of terms
  • Statement: Per an INC action item, this issue is being proposed for INC to create a single glossary of terms of all INC terms across all INC documents. Historically, when the definition of a term has been updated for one INC document, INC has not always reviewed all documents where the term is located to ensure that the definition is consistent across documents. Having a single combined glossary would prevent this from happening.
  • Resolution:
  • Status: New Issue

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

• NRSC: Network Reliability Steering Committee

  • Issue: 0060
  • Title: NORS Root and Direct Cause Review and Recommendations
  • Statement: In the years since NORS’ inception, the industry has experienced various outage signatures. Many of these signatures are represented adequately in existing causation options listed by the FCC; however, recent concerns by the FCC have indicated a necessity for additional details that are germane to modern outages.
  • Resolution:
  • Status: New Issue

  • Issue: 0061
  • Title: 988 Designated Point of Contact Recertification 2026
  • Statement: FCC requirement for annual DPOC audit and recertification by the NRSC Regulatory team. (FCC 23-57)
  • Resolution:
  • Status: New Issue

  For more information, visit the NRSC home page.

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

TOPS

• Document Number: ATIS-I-0000110
• Title: Entropy Quality and the Security of AES-128 in Classical and Quantum Contexts
• Type: New
• View Here

WTSC

• Document Number: ATIS-0700015.v006
• Title: ATIS Standard for Implementation of 3GPP Common IMS Emergency Procedures for IMS Origination and ESInet/Legacy Selective Router Termination
• Type: Revision
• View Here

Recent Policy Filings

ATIS

• Date: 02/09/2026
• Description: Comments in Response to U.S. Customs and Border Protection for Proposed Modifications to the Electronic System for Travel Authorization
• View filing

ATIS

• Date: 02/03/2026
• Description: INC, IP-NNI TF: Reply Comments in Response to FCC FNPRM for Advanced Methods to Target and Eliminate Unlawful Robocalls
• View filing
• Date: 02/06/2026
• Description: Reply Comments in Response to Comments on the Somos Petition
• View filing
• Date: 02/19/2026
• Description: Reply Comments in Response to FCC NPRM for Advancing IP Interconnection
• View filing

ATIS

• Date: 02/03/2026
• Description: INC, IP-NNI TF: Reply Comments in Response to FCC FNPRM for Advanced Methods to Target and Eliminate Unlawful Robocalls
• View filing