January 2026

Committee Reports

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0175
  • Title: Investigate Out-of-Band SHAKEN architecture that uses STI-CPS discovery
  • Statement: While there are no documented issues with hop-to-hop Out-of-Band (OOB) SHAKEN, an alternative OOB SHAKEN architecture that uses a single Secure Telephone Identity Call Placement Service (STI-CPS) per call with STI-CPS discovery instead of hop-to-hop may be possible.
  • Resolution: This Issue was closed with the publication of the following ATIS standards: • ATIS-1000107, Signature-Based Handling of Asserted information using toKENs (SHAKEN): STI-CPS Discovery for Out-of-Band PASSporT Transmission Involving TDM Networks • ATIS-1000097.v004, Alternatives for Call Authentication for Non-IP Traffic • ATIS-1000106.v002, Viability of Non-IP Call Authentication Standards
  • Status: Final Closure

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

• STEP: Sustainability in Telecom: Energy and Protection Committee
  • Issue: 0220
  • Title: Introduce a new test for equipment with lithium-ion batteries within the chassis within ATIS-0600307, Fire Resistance Criteria - Ignitability Requirements for Equipment Assemblies, and Fire Spread Requirements for Wire and Cable
  • Statement: An in-situ test of lithium-ion batteries is needed in order to analyze the flame propagation and potential for using lithium-ion batteries mounted within ICT equipment.
  • Resolution:
  • Status: New Issue

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

• WTSC: Wireless Technologies and Systems Committee
  • Issue: 112
  • Title: Multilingual Templates for WEA
  • Statement: On December 10, 2025, the Federal Communications Commission’s Public Safety and Homeland Security Bureau (Bureau) published its Report and Order amending the Commission’s Wireless Emergency Alert (WEA) rules for multilingual templates that alert originators can choose to send during life-threatening emergencies in the Federal Register. The new rules require commercial mobile service providers who participate in WEA (Participating CMS Providers) to support multilingual templates for the most commonly issued and most time-sensitive types of alerts in English, the next thirteen most commonly spoken languages in the United States, and American Sign Language (ASL). In addition, the non-ASL templates must be customizable with event-specific information that utilize four fillable elements: the name of the sending agency, the location, the time, and an optional URL. The adopted rules will be effective June 12, 2028, thirty months from the date of the rule’s publication in the Federal Register. The adopted rules are as follows: Final Rules For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 10 as follows: PART 10—WIRELESS EMERGENCY ALERTS 1. The authority citation for part 10 continues to read as follows: Authority: 47 U.S.C. 151, 152, 154(i), 154(n), 201, 301, 303(b), 303(e), 303(g), 303(j), 303(r), 307, 309, 316, 403, 544(g), 606, 1201, 1202, 1203, 1204, and 1206. 2. amend § 10.480 by adding paragraphs (c) through (f) to read as follows: § 10.480 Language support. * * * * * (c) Participating CMS Providers shall support pre-scripted alert templates for the following events: tornado emergency, tornado warning, flash flood emergency, flash flood warning, severe thunderstorm, snow squall, dust storm, hurricane, storm surge, extreme wind, test alert, fire, tsunami, earthquake, boil water, avalanche, hazardous materials, and 911 outage. (d) Participating CMS Providers shall support the pre-scripted alert templates listed in paragraph (c) of this section for English, Arabic, Chinese (simplified and traditional), French, German, Haitian Creole, Hindi, Italian, Korean, Portuguese, Russian, Spanish, Tagalog, and Vietnamese. The language of the templates that Participating CMS Providers must support is provided at: https://www.fcc.gov/sites/default/files/FillableAlertTemplates-WEA-MultilingualOrder.pdf. (e) Participating CMS Providers shall support the inclusion of four fillable elements that customize the pre-scripted alert templates for the languages listed in paragraph (d) of this section. Alert Messages that use the pre-scripted alert templates shall display, as specified by the originator: (1) In the [SENDING AGENCY] field, the name of the agency originating the alert; (2) In the [LOCATION] field, the name of the geographic area pertaining to the alert message; (3) In the [TIME] field, the time when the emergency conditions described in the alert are expected to end; (4) In the [URL] field, a Uniform Resource Locator (URL), if included by the alert originator. (f) Participating CMS Providers shall support static, pre-scripted alert templates for American Sign Language (ASL) for each of the events listed in paragraph (c) of this section. The pre-scripted video templates that Participating CMS Providers must support are provided at: https://www.fcc.gov/WirelessEmergencyAlert-Templates-ASL. 3. amend § 10.500 by adding paragraph (e)(3) as follows: § 10.500 General requirements. * * * * * (e) * * * (3) Displaying the corresponding pre-scripted Alert Messages in English following the display of each Alert Message that uses a pre-scripted alert template in a non-English language. * * * * *
  • Resolution:
  • Status: New Issue

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

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

INC

• Date: 01/07/2026
• Description: Response to Somos, Inc. Petition for Rulemaking for Updating and Consolidating Telephone Numbering and Routing Systems for an Efficient IP Transition
• View filing

PTSC

• Date: 01/05/2026
• Description: Comments in Response to FCC FNPRM for Improving Verification and Presentation of Caller Identification Information (ATIS/SIP Forum IP-NNI)
• View filing
• Date: 01/20/2026
• Description: Comments in Response to FCC NPRM for Advanced IP Interconnection (ATIS/SIP Forum IP-NNI)
• View filing