T-Mobile, Cox See 2018-2019 Shaken/Stir Implementation, CenturyLink Cites 2019 'Impacts'
T-Mobile and Cox Communications cited 2018-2019 timelines for implementing Shaken/Stir call authentication standards targeting spoofed robocalling, and CenturyLink expects visible "impacts" beginning in 2019. T-Mobile plans "to commercially launch our STIR/SHAKEN network solution prior to the end of 2018," said…
Sign up for a free preview to unlock the rest of this article
Communications Daily is required reading for senior executives at top telecom corporations, law firms, lobbying organizations, associations and government agencies (including the FCC). Join them today!
a filing posted Friday in docket 17-59 on a discussion with FCC Chief Technology Officer Eric Burger and other staffers. "[W]e expect that by the end of 2019, all handset specifications will include the requirements necessary to support display of the STIR/SHAKEN verification result." It also noted its "Scam ID and Scam Block solutions" deployed in March 2017: "We believe these solutions are the best in the business, and our customers love them." Cox's "target date to begin to test SHAKEN/STIR for its residential customers is late 2018 to early 2019, with broader implementation" in 2019, said its filing on a discussion with agency staffers. CenturyLink cited the benefits of Shaken/Stir (Secure Handling of Asserted Information using toKENs/Secure Telephony Identity Revisited), its related efforts and "the company's and the industry's anticipated schedule for testing and deployment." CenturyLink believes "implementation and increasing deployment of these standards will benefit consumers, with impacts being visible beginning in 2019," said a filing on a discussion with agency staffers. Comcast (see 1805220014) and AT&T cited 2018-2019 implementation timelines, while Sprint cited hurdles (see 1805170018). FCC Chairman Ajit Pai accepted North American Numbering Council recommendations for creating a Shaken/Stir framework for VoIP service within a year and encouraging carrier implementation (see 1805140028).