Early Signs Are Stir/Shaken Is an Effective Tool Against Illegal Robocalls: FCC
Stir/Shaken is just getting started, but early signs are it’s helping curb illegal robocalls, the FCC said in a Friday report to Congress required by the Traced Act. “STIR/SHAKEN implementation is in its early stages,” the report said: “Voice service…
Sign up for a free preview to unlock the rest of this article
Timely, relevant coverage of court proceedings and agency rulings involving tariffs, classification, valuation, origin and antidumping and countervailing duties. Each day, Trade Law Daily subscribers receive a daily headline email, in-depth PDF edition and access to all relevant documents via our trade law source document library and website.
providers were just required to implement and begin using STIR/SHAKEN 18 months ago, with the exceptions of non-facilities based voice service providers, which were not required to implement STIR/SHAKEN until six months ago, and facilities-based small voice service providers, which will not be required to implement STIR/SHAKEN for another six months.” The data on its efficacy is “currently limited, but will increase as voice service providers’ experience with the technology and the providers using it expands.” The FCC noted it sought comment as it prepared its first triennial assessment on use of Stir/Shaken. “No commenter submitted substantive comments suggesting that the technology is itself deficient for that purpose, but some express concern that providers may be applying its technical requirements inconsistently,” the agency said. “There is general agreement in the record, however, that when applied as designed, the technology used in the STIR/SHAKEN framework effectively allows providers to identify calls with illegally spoofed caller ID information.” The technology relies on technical standards and protocols developed by ATIS, the report said: “Those commenters that express concern about the STIR/SHAKEN reaching its full potential as a tool to combat illegal spoofing generally do so on the basis that providers may be applying the standards inconsistently or incorrectly.” Comments were filed at the FCC in October (see 2210240062).