Federal Communications Commission DA 25-763 DA 25-763 Released: August 27, 2025 WIRELINE COMPETITION BUREAU SEEKS COMMENT ON TWO PERIODIC TRACED ACT OBLIGATIONS REGARDING STIR/SHAKEN CALLER ID AUTHENTICATION WC Docket No. 17-97 Comments Due: (30 days after the date of publication in the Federal Register) Reply Comments Due: (45 days after the date of publication in the Federal Register) By this Public Notice, the Wireline Competition Bureau (Bureau) seeks comment concerning two recurring statutory obligations under the Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act). First, as required annually, the Bureau seeks comment on whether the extensions granted by the Commission for implementation of the STIR/SHAKEN caller ID authentication framework should be revised or extended. Second, the Bureau seeks comment to inform the Commission’s second triennial assessment of the efficacy of the STIR/SHAKEN caller ID authentication framework as a tool to combat illegal robocalls. I. COMMENTS SOUGHT ON STIR/SHAKEN IMPLEMENTATION EXTENSIONS In the TRACED Act, Congress instructed the Commission to “assess any burdens or barriers” to the implementation of STIR/SHAKEN that certain providers might face, and “upon a public finding of undue hardship,” authorized the Commission to delay STIR/SHAKEN implementation deadlines “for a reasonable period of time.” TRACED Act § 4(b)(5)(A); 47 U.S.C. § 227b(b)(5)(A). In its initial assessment conducted in 2020, the Commission granted three categorical implementation extensions based on undue hardship, See Call Authentication Trust Anchor, WC Docket No. 17-97, 36 FCC Rcd 1859, 1877-83, paras. 39-51 (2020) (Second Caller ID Authentication Report and Order) (granting extensions to: (1) small voice service providers with 100,000 or fewer voice subscriber lines; (2) providers unable to obtain the SPC token necessary to participate in STIR/SHAKEN; and (3) services scheduled for section 214 discontinuance). and it added a third undue hardship extension in 2023. Call Authentication Trust Anchor, WC Docket No. 17-97, Sixth Report and Order and Further Notice of Proposed Rulemaking, 38 FCC Rcd 2573, 2614-15, paras. 79-82 (2023) (Sixth Caller ID Authentication Order and Further Notice) (granting an extension to small voice service providers that originate calls via satellite using North American Numbering Plan (NANP) numbers). Pursuant to the TRACED Act, providers also have a continuing extension for the portions of their networks that rely on technology that cannot initiate, maintain, or terminate session internet protocol (SIP) calls. See TRACED Act § 4(b)(5)(B); 47 U.S.C. § 227b(b)(5)(B); 47 CFR § 64.6304(d); Second Caller ID Authentication Report and Order, 36 FCC Rcd at 1892-96, paras. 66-70. Because this extension was not granted on the basis of undue hardship, we do not address it further in this Public Notice. See TRACED Act § 4(b)(5)(B); 47 U.S.C. § 227b(b)(5)(B). Additionally, providers that lack control over the network infrastructure necessary to implement STIR/SHAKEN are exempt from implementing STIR/SHAKEN. See Call Authentication Trust Anchor, Implementation of TRACED Act Section 6(a)—Knowledge of Customers by Entities with Access to Numbering Resources, WC Docket Nos. 17-97 and 20-67, Report and Order and Further Notice of Proposed Rulemaking, 35 FCC Rcd 3241, 3260, para. 40 (2020) (First Caller ID Authentication Report and Order). As this is not an undue hardship extension, we also do not address it further in this Public Notice. Only two such extensions remain for (1) providers that cannot obtain the Service Provider Code (SPC) token necessary to participate in STIR/SHAKEN, and (2) small voice service providers that originate calls via satellite using North American Numbering Council (NANC) numbers. See 47 CFR § 64.6304(a). The extension for services scheduled for section 214 discontinuance expired on June 30, 2022, and the extension for non-facilities-based and facilities-based small voice service providers ended on June 30, 2022, and June 30, 2023, respectively. See id.; Second Caller ID Authentication Report and Order, 36 FCC Rcd at 1877-82, paras. 40-48; Call Authentication Trust Anchor, WC Docket No. 17-97, Fourth Report and Order, 36 FCC Rcd 17840, 17844, para. 9 (2021). The TRACED Act further instructs the Commission to annually “consider revising or extending” any extension granted due to undue hardship, including whether an extension remains necessary. See TRACED Act § 4(b)(5)(F); 47 U.S.C. § 227b(b)(5)(F). To comply, the Commission has directed the Bureau to annually “reevaluate” and “revise or extend” any such extension “as necessary.” Second Caller ID Authentication Report and Order, 36 FCC Rcd at 1897, para. 72; see also 47 CFR § 64.6304(f). As part of this evaluation, the Bureau may lengthen a granted extension and it can also decrease, but not expand, the scope of entities that are entitled to such an extension. Second Caller ID Authentication Report and Order, 36 FCC Rcd at 1897, para. 72; see also 47 CFR § 64.6304(f). Pursuant to the TRACED Act and section 64.6304(f) of the Commission’s rules, we seek comment to enable our annual reevaluation of the remaining STIR/SHAKEN undue hardship implementation extensions. When considering whether a hardship is “undue” under the TRACED Act, and whether an extension is for a “reasonable amount of time,” the Commission has found it appropriate to balance the hardship of compliance due to “the burdens and barriers to implementation” faced by a provider or class of providers with the benefit to the public of implementing STIR/SHAKEN expeditiously. Sixth Caller ID Authentication Order and Further Notice, 38 FCC Rcd at 2614, para. 80. With that in mind, we seek comment on whether the Bureau should revise or extend the two remaining extensions. Extension for Providers That Cannot Obtain an SPC Token. We seek comment on the extension for providers that cannot obtain an SPC token. To participate in STIR/SHAKEN, a provider must obtain an SPC token through the STIR/SHAKEN governance system. Call Authentication Trust Anchor, Appeals of the STIR/SHAKEN Governance Authority Token Revocation Decisions, WC Docket Nos. 17-97 and 21-291, Third Report and Order, 36 FCC Rcd 12878, 12879-81, paras. 4-6 (2021) (Third Caller ID Authentication Report and Order) (explaining the STIR/SHAKEN governance system and policy for obtaining SPC tokens). Because access to a token is necessary for participation in STIR/SHAKEN, the Commission initially granted providers unable to obtain a token an indefinite extension until they were able to receive a token. Second Caller ID Authentication Report and Order, 36 FCC Rcd at 1882-82, para. 50. In May 2021, the STIR/SHAKEN Governance Authority revised the Token Access Policy to enable more providers to obtain a token. Caller ID Authentication Governance Framework Revised to Enable Earlier Participation by Providers Without Direct Access to Telephone Numbers, WC Docket Nos. 13-97, 17-97, Public Notice, 36 FCC Rcd 8318 (WCB 2021). In its November 2024 Eighth Caller ID Authentication Report and Order, the Commission required, inter alia, that all providers with a STIR/SHAKEN implementation obligation obtain an SPC token from the STIR/SHAKEN Policy Administrator, but declined to repeal the indefinite SPC token extension. Call Authentication Trust Anchor, WC Docket No. 17-97, Eighth Report and Order, 39 FCC Rcd 12894, 12908-09, para. 20, 12915-16, para. 29 n.137 (2024) (Eighth Caller ID Authentication Report and Order). The rules adopted in the Eighth Caller ID Authentication Report and Order will go into effect on September 18, 2025. Wireline Competition Bureau Announces Effective Date for STIR/SHAKEN Rules, WC Docket No. 17-97, Public Notice, DA 25-730 (WCB rel. Aug. 19, 2025). In its most recent annual evaluation, the Bureau declined to terminate or modify the extension so staff could assess the number of providers still claiming the extension in their most recent Robocall Mitigation Database submissions and the merit of those claims. Wireline Competition Bureau Performs Required Evaluation of STIR/SHAKEN Implementation Extensions Pursuant to Section 64.6304(f) of the Commission’s Rules, WC Docket No. 17-97, Public Notice, DA 24-1252 at 7 (WCB Dec. 13, 2024). To supplement this assessment, we seek comment on the types and number of providers that remain unable to obtain a token and the barriers to token access for these providers, in light of the changes to the Token Access Policy. Is there anything that can be done to make tokens available to these providers? Does the extension remain necessary? Extension for Small Voice Service Providers Originating Calls via Satellite Using NANP Numbers. We seek comment on the Commission’s extension for small voice service providers that originate calls via satellite using North American Numbering Plan (NANP) numbers. The Commission adopted this indefinite extension concluding that the balance of benefits and burdens counseled “against requiring such providers to implement” STIR/SHAKEN. Sixth Caller ID Authentication Order and Further Notice, 38 FCC Rcd at 2614-15, para. 81 (deciding that “satellite service costs make the high-volume calling necessary for robocallers uneconomical,” there was “little evidence that satellite providers or their users are responsible for illegal robocalls,” and the number of satellite subscribers using NANP resources was “miniscule.”). We seek comment on the current benefits, burdens, and barriers to STIR/SHAKEN implementation by small voice service providers that originate calls via satellite using NANP numbers. Have these benefits, burdens, and barriers changed since the Commission adopted the extension and if so, how? Do the justifications for the extension still apply? Have any abuses occurred due to this extension, or are any abuses likely to result if the extension is continued? What impact does the extension have on the Commission’s longstanding goal of achieving ubiquitous deployment of the STIR/SHAKEN framework? Is it necessary for the extension to remain indefinite, or would it be more appropriate to modify the extension to provide a known end date? II. COMMENTS SOUGHT ON STIR/SHAKEN EFFICACY Section 4(b)(4) of the TRACED Act directs the Commission to, every three years, “assess the efficacy of the technologies used for [the] call authentication frameworks” implemented pursuant to the TRACED Act and “based on the assessment . . . revise or replace the call authentication frameworks . . . if the Commission determines it is in the public interest to do so.” TRACED Act § 4(b)(4)(A)-(B); 47 U.S.C. § 227b(b)(4)(A)-(B). The Commission must submit to Congress “a report on the findings of the assessment” and any actions taken by the Commission “to revise or replace the call authentication frameworks.” TRACED Act § 4(b)(4)(C); 47 U.S.C. § 227b(b)(4)(C). Before conducting the assessment under the TRACED Act, the Commission is required to provide public notice and an opportunity to comment. 47 U.S.C. § 227b(b)(4) The Commission submitted its first such triennial report to Congress on December 20, 2022, finding that STIR/SHAKEN is effective at authenticating caller ID information. Federal Communications Commission, Triennial Report on the Efficacy of the Technologies Used in the STIR/SHAKEN Caller ID Authentication Framework (2022), https://docs.fcc.gov/public/attachments/DOC-390474A1.pdf (First Triennial Report). Through this Public Notice, the Bureau seeks comment to inform the Commission’s second triennial assessment on the efficacy of STIR/SHAKEN, which remains the only call authentication framework currently implemented pursuant to the TRACED Act. In the First Triennial Report, the Bureau established a standard for conducting its assessment that is based on “how well [STIR/SHAKEN] effectuates the authentication of caller ID information.” Id. at 8. Although the Bureau considered applying alternative standards, such as STIR/SHAKEN’s “impact on preventing illegally spoofed robocalls, or preventing all illegal robocalls,” it agreed with the majority of commenters that assessing STIR/SHAKEN under such standards “would fail to account for the fact that, while a critical tool in protecting consumers from illegal spoofing, the STIR/SHAKEN framework is only one facet of the larger campaign by the Commission and industry to combat illegal robocalls.” Id. at 8. The Bureau seeks comment on whether it should maintain, revise, or replace this standard for its second assessment of the efficacy of STIR/SHAKEN. In the three years that have passed since the Commission conducted its first triennial assessment, providers have gained more experience implementing the STIR/SHAKEN framework. The Commission has also adopted rules expanding STIR/SHAKEN implementation obligations to cover gateway providers and non-gateway intermediate providers, in addition to voice service providers. Gateway providers were required to implement STIR/SHAKEN by June 30, 2023, and non-gateway intermediate providers that receive unauthenticated calls directly from domestic originating providers were required to authenticate those calls using STIR/SHAKEN as of December 31, 2023. See Advanced Methods to Target and Eliminate Unlawful Robocalls, Call Authentication Trust Anchor, CG Docket No. 17-59, WC Docket No. 17-97, Sixth Report and Order in CG Docket No. 17-59, Fifth Report and Order in WC Docket No. 17-97, Order on Reconsideration in WC Docket No. 17-97, Order, Seventh Further Notice of Proposed Rulemaking in CG Docket 17-59, Fifth Further Notice of Proposed Rulemaking in WC Docket No. 17-97, 37 FCC Rcd 6865, 6892, para. 59 (2022) (Gateway Provider Order and Further Notice); Sixth Caller ID Authentication Order and Further Notice, 38 FCC Rcd at 2587, para. 27. Now, all providers with control over the network infrastructure necessary to authenticate calls are required to implement STIR/SHAKEN for session internet protocol (SIP) calls unless subject to an exemption or extension. See 47 CFR § 64.6304(a)(1)(iii), (b). With these developments in mind, we seek comment on how well STIR/SHAKEN effectuates the authentication of caller ID information today. Are there ways STIR/SHAKEN could be more effective at authenticating caller ID information? Do any specific factors limit STIR/SHAKEN’s efficacy, and what solutions might resolve these issues? Have there been other developments, such as industry changes or evolution in technologies, that affect the efficacy of STIR/SHAKEN, and how should any such developments be factored into our assessment? Do any commenters believe the Commission should revise STIR/SHAKEN or replace it with a different framework? We also seek comment on the efficacy of STIR/SHAKEN under any alternative standard proposed by commenters. III. PROCEDURAL MATTERS Comment Filing Procedures. Pursuant to sections 1.415 and 1.419 of the Commission’s rules, 47 CFR §§ 1.415, 1.419, interested parties may file comments and reply comments on or before the dates indicated on the first page of this document. Comments may be filed using the Commission’s Electronic Comment Filing System (ECFS). · Electronic Filers: Comments may be filed electronically using the Internet by accessing the ECFS: https://www.fcc.gov/ecfs. · Paper Filers: Parties who choose to file by paper must file an original and one copy of each filing. o Filings can be sent by hand or messenger delivery, by commercial courier, or by the U.S. Postal Service. All filings must be addressed to the Secretary, Federal Communications Commission. o Hand-delivered or messenger-delivered paper filings for the Commission’s Secretary are accepted between 8:00 a.m. and 4:00 p.m. by the FCC’s mailing contractor at 9050 Junction Drive, Annapolis Junction, MD 20701. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes and boxes must be disposed of before entering the building. o Commercial courier deliveries (any deliveries not by the U.S. Postal Service) must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701. o Filings sent by U.S. Postal Service First-Class Mail, Priority Mail, and Priority Mail Express must be sent to 45 L Street NE, Washington, DC 20554. · People with Disabilities: To request materials in accessible formats for people with disabilities (braille, large print, electronic files, audio format), send an e-mail to fcc504@fcc.gov or call the Consumer & Governmental Affairs Bureau at 202-418-0530. Ex Parte Rules. This proceeding shall be treated as a “permit-but-disclose” proceeding in accordance with the Commission’s ex parte rules. 47 C.F.R. §§ 1.1200 et seq. Persons making ex parte presentations must file a copy of any written presentation or a memorandum summarizing any oral presentation within two business days after the presentation (unless a different deadline applicable to the Sunshine period applies). Persons making oral ex parte presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the ex parte presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter’s written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during ex parte meetings are deemed to be written ex parte presentations and must be filed consistent with rule 1.1206(b). In proceedings governed by rule 1.49(f) or for which the Commission has made available a method of electronic filing, written ex parte presentations and memoranda summarizing oral ex parte presentations, and all attachments thereto, must be filed through the electronic comment filing system available for that proceeding, and must be filed in their native format (e.g., .doc, .xml, .ppt, searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission’s ex parte rules. Contact Information. For further information, please contact Janice Gorin, Attorney Advisor, Competition Policy Division, Wireline Competition Bureau at (202) 418-0637 or by email at Janice.Gorin@fcc.gov. -FCC- 2