<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="https://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
>
    <channel>
                    <atom:link href="https://www.nexttv.com/feeds/tag/stirshaken" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Next TV in Stirshaken ]]></title>
                <link>https://www.nexttv.com/tag/stirshaken</link>
        <description><![CDATA[ All the latest stirshaken content from the Next TV team ]]></description>
                                    <lastBuildDate>Thu, 20 May 2021 21:28:45 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ FCC Proposes Shorter STIR/SHAKEN Deadline for Some Providers ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/fcc-proposes-shorter-stirshaken-deadline-for-some-providers</link>
                                                                            <description>
                            <![CDATA[ Targets smaller operators with larger volume of illegal robocalls ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">VHyvAvfoJwAHwse6FYfaj6</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 20 May 2021 21:28:45 +0000</pubDate>                                                                                                                                <updated>Thu, 20 May 2021 22:16:26 +0000</updated>
                                                                                                                                            <category><![CDATA[Policy]]></category>
                                                                                                <author><![CDATA[ john.eggerton@futurenet.com (John Eggerton) ]]></author>                    <dc:creator><![CDATA[ John Eggerton ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/ETjt8sjZcQr97v7yakQ4hP.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg">
                                                            <media:credit><![CDATA[N/A]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[robocalls]]></media:description>                                                            <media:text><![CDATA[robocalls]]></media:text>
                                <media:title type="plain"><![CDATA[robocalls]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The <a href="https://www.nexttv.com/tag/fcc">FCC</a> has voted unanimously to shorten the deadline for some smaller voice providers to use the STIR/SHAKEN caller ID regime, meant to weed out unwanted robocalls, but smaller cable operator voice providers want to make sure the FCC isn&apos;t casting a too wide net.</p><p>The FCC said that some new evidence suggests that a "small subset" of smaller voice service providers were responsible for an "increasing quantity" of illegal robocalls.</p><p>The FCC set a June 30, 2021 deadline for most voice service providers, including larger cable operators, to implement STIR/SHAKEN, but <a href="https://www.nexttv.com/news/aca-connects-to-fcc-stir-shaken-extension-is-warranted">gave smaller providers—fewer than 100,000 subs—more time.</a></p><p><a href="https://www.nexttv.com/news/fcc-fleshes-out-shakenstir-mandate">Also Read: FCC Fleshes Out STIR/SHAKEN</a></p><p>But in a vote at its Thursday (May 20) public meeting, the commission said it would shorten that by a year (June 2022) for smaller providers "which originate an especially larger amount of traffic."</p><p>"We recently discovered that some smaller companies are pumping large volumes of traffic onto our networks and a lot of it looks suspiciously like robocalls," said <a href="https://www.nexttv.com/features/jessica-rosenworcel-takes-fcc-gavel">FCC acting chair Jessica Rosenworcel</a>. "It’s time to change course.  So here we propose to cut back on the extension for smaller providers that are sending these junk calls. Implementing STIR/SHAKEN—and doing it faster as we propose here—will help reduce robocalls over time."</p><p>The FCC sought comment on how to best define that subset that poses "a heightened risk of originating an especially large amount of illegal robocall traffic," as well as whether it should do more to improve oversight of the smaller providers it identifies as requiring the shortened deadline.</p><p>ACA Connects, which represents smaller providers, said it will keep an eye on the proceeding going forward to make sure the FCC is aiming at the right target.</p><p>“ACA Connects represents small voice providers that have an established presence in their communities and take their obligations seriously," said Brian Hurley, ACA Connects VP of regulatory affairs. "We intend to participate in this proceeding to ensure it remains squarely focused on the correct target – the &apos;subset&apos; of providers responsible for originating large volumes of illegal robocalls – and that it avoids sweeping in ACA Connects members and other legitimate providers that are not the source of this problem.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Comcast Rolls Out STIR/SHAKEN Robocall Protection to Xfinity Voice Landline Customers ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/comcast-rolls-out-stirshaken-robocall-protection-to-xfinity-voice-landline-customers</link>
                                                                            <description>
                            <![CDATA[ The cable operator’s 11 million residential and business voice customers will now see ‘V’ displayed on their caller ID, ensuring they’re not about to pick up a spam call ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">4qot7FVJgj6RmToqWnrt4Y</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/f7AUsaNs2XonTB6aeEyTkP-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 09 Mar 2021 20:01:41 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Technology]]></category>
                                                                                                <author><![CDATA[ daniel.frankel@futurenet.com (Daniel Frankel) ]]></author>                    <dc:creator><![CDATA[ Daniel Frankel ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/7wBJVmzcn7E9PQZWPFQsH7.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/f7AUsaNs2XonTB6aeEyTkP-1280-80.jpg">
                                                            <media:credit><![CDATA[Future]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[The average U.S. consumer receives 350 spam calls a year, YouMail says.]]></media:description>                                                            <media:text><![CDATA[The average U.S. consumer receives 350 spam calls a year, YouMail says.]]></media:text>
                                <media:title type="plain"><![CDATA[The average U.S. consumer receives 350 spam calls a year, YouMail says.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/f7AUsaNs2XonTB6aeEyTkP-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Comcast, too, has a message for the "vehicle owner." </p><p>Comcast has announced deployment of STIR/SHAKEN-based robocall protection to its 11 million residential and business landline voice customers. </p><p>When receiving calls, these customers will now be able to see a “V” in their caller ID, verifying that the call is actually coming from the displayed number and not some spammer who is spoofing the ID. </p><p>Comcast reported over 9.6 million Xfinity Voice residential customers at the end of 2020, down about 39,000 year over year, and nearly 1.4 million business voice subscribers, up about 16,000. </p><p>The cable company has been working on STIR/SHAKEN technology for several years and says the time is right to deploy it against the backdrop of an estimated 46 billion robocalls received nationwide just in 2020 alone. In fact, citing YouMail data, Comcast said the average U.S. consumer receives 350 spam calls a year. </p><p>“Comcast engineers helped pioneer STIR/SHAKEN and the company has been a leader in the industry-wide effort to combat fraudulent calls since day one,” said Kelly Barlow, senior VP of connectivity services for Comcast, in a statement. “We’ll continue to enable our customers with the tools to protect themselves and partner within the industry to help rid the nation’s consumers of these dangerous calls for good.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ FCC Fleshes Out SHAKEN/STIR Mandate ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/fcc-fleshes-out-shakenstir-mandate</link>
                                                                            <description>
                            <![CDATA[ FCC Fleshes out SHAKEN/STIR Mandate ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">GTCYDx95hab8koBDsxdtAk</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 29 Sep 2020 21:16:29 +0000</pubDate>                                                                                                                                <updated>Tue, 29 Sep 2020 22:18:08 +0000</updated>
                                                                                                                                            <category><![CDATA[Policy]]></category>
                                                                                                <author><![CDATA[ john.eggerton@futurenet.com (John Eggerton) ]]></author>                    <dc:creator><![CDATA[ John Eggerton ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/ETjt8sjZcQr97v7yakQ4hP.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg">
                                                            <media:credit><![CDATA[N/A]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The FCC has voted on new rules implementing the STIR/SHAKEN caller ID authentication regime meant to weed out unwanted robocalls. At the same time it dropped the item from its Sept. 30 public meeting agenda.</p><p>The new rules: "1) require voice service providers to either upgrade their non-IP networks to IP and implement STIR/SHAKEN, or work to develop a non-IP caller ID authentication solution"; 2) "require intermediate providers to implement STIR/SHAKEN so that IP calls retain caller ID authentication throughout the call path"; and 3) "prohibit carriers from adding a line item to the bills of consumers and small businesses for caller ID authentication technology."</p><p><a href="https://www.nexttv.com/news/fcc-adopts-mandatory-stir-shaken-regime">Related: FCC Adopts STIR/SHAKEN Regime</a></p><p>STIR/SHAKEN is the default protection against identity spoofing and malicious robocalls by verifying a caller ID before the call gets to the recipient. The regime applies to IP voice service.</p><p>The FCC initially voted to allow and encourage carriers to block unverified IDs by default using STIR/SHAKEN, but then mandated it. The service must be free. In addition, Congress voted in December 2019 to mandate the regime, giving carriers 18 months after passage to have it in place--a June 2021 deadline.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ ACA Connects to FCC: STIR/SHAKEN Extension is Warranted ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/aca-connects-to-fcc-stir-shaken-extension-is-warranted</link>
                                                                            <description>
                            <![CDATA[ ACA Connects to FCC: STIR/SHAKEN Extension is Warranted ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">hnpdrhHrDmStxqkC3LRD5K</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 02 Jun 2020 14:44:18 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Policy]]></category>
                                                                                                <author><![CDATA[ john.eggerton@futurenet.com (John Eggerton) ]]></author>                    <dc:creator><![CDATA[ John Eggerton ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/ETjt8sjZcQr97v7yakQ4hP.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/wxJPjEyzaESCobzA6QqwL4-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>ACA Connects said the FCC was definitely right in proposing a one-year extension to smaller operators of its deadline for adopting the STIR/SHAKEN call authentication regime. </p><p>STIR/SHAKEN is the illegal robocall-combating tool ISPs are required to adopt under the TRACED Act. </p><p><a href="https://www.nexttv.com/news/fcc-adopts-mandatory-stir-shaken-regime" data-original-url="https://www.multichannel.com/news/fcc-adopts-mandatory-stir-shaken-regime">Related: FCC Adopts Mandatory STIR/SHAKEN Regime </a></p><p>In reply comments filed at the FCC, ACA Connects, which represents those smaller operators, said that extending the June 30,2021 deadline until June 2022, as the FCC has proposed, makes sense because smaller operators are depending on third-party vendors for implementation "solutions" that are still being developed. </p><p>Responding to AT&T's opposition to the extension in its comments, ACA Connects pointed out that AT&T itself has conceded implementation can be tough, saying "these are not easy tasks to achieve." ACAC said that "no doubt this observation would apply with even greater force when it comes to small providers operating with limited resources or in-house technical expertise." </p><p>And while some have suggested the FCC could adopt a case-by-case review of extensions, rather than the blanket extension it has proposed, ACAC pushed back.  </p><p>"This approach would inundate the Commission with extension requests from a multitude of small providers, many of them presenting evidence of the same or similar implementation burdens," it said. "The costs of hiring outside lawyers and consultants to prepare and submit these requests would consume funds that would be better spent working towards implementation of STIR/SHAKEN." </p><p><a href="https://www.nexttv.com/news/house-approves-comprehensive-robocall-bill" data-original-url="https://www.multichannel.com/news/house-approves-comprehensive-robocall-bill">Related: House Approves Comprehensive Robocall Bill</a></p><p>ACAC said "small providers as a class face 'undue hardship' sufficient to justify an extension of at least one year." </p><p>The "at least" was a reference to some commenters seeking an even longer extension. ACAC said it was OK with that, too, though it said the FCC should provide plenty of notice if it planned to extend the extension. </p><p>Some commenters said that the exemption could allow smaller IP-based voice providers to continue to originate large volumes of illegal robocalls.  </p><p>ACAC countered that while it appreciates the concern, that is already taken care of by the TRACED Act's requirement that during any compliance delay, an operator must adopt a robocall mitigation program. It also urged the FCC to <a href="https://www.nexttv.com/news/fcc-to-robocallers-no-more-warnings" data-original-url="https://www.multichannel.com/news/fcc-to-robocallers-no-more-warnings">continue to pursue robocall scammers vigorously.</a> "[E]ven if most unlawful robocalls are originated by small providers, it does not follow that most small providers originate large volumes of unlawful robocalls," ACAC said.</p><p>ACAC got an assist from NCTA-The Internet & Television Association, which said it supports the extension because they face challenges that make it "difficult, if not impossible," to comply.</p><p>NCTA, whose members include all the largest providers, said those had an advantage smaller operators did not (and could be the 800 pound canaries in the mine shaft, as it were). "While the implementation of STIR/SHAKEN requires all voice providers to incur a variety of costs, most large providers already have commenced planning for the necessary investments and should be in a position to sign and receive calls by the deadline," it said. "Smaller providers, on the other hand, generally are not as far along in the planning process, and their decisions will be informed by the initial experience of larger providers." </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ FCC Releases Tentative Agenda for March Meeting ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/fcc-releases-tentative-agenda-for-march-meeting</link>
                                                                            <description>
                            <![CDATA[ FCC Releases Tentative Agenda for March Meeting ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">fwXkUQd8eiyB6UnCDT5QNc</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/aKj9FvHEqk8jasC25P6ezj-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 11 Mar 2020 02:58:49 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Policy]]></category>
                                                                                                <author><![CDATA[ john.eggerton@futurenet.com (John Eggerton) ]]></author>                    <dc:creator><![CDATA[ John Eggerton ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/ETjt8sjZcQr97v7yakQ4hP.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/aKj9FvHEqk8jasC25P6ezj-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/aKj9FvHEqk8jasC25P6ezj-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The FCC has released its tentative agenda for the March 31 public meeting and it includes proposals to 1) mandate the STIR/SHAKEN default robocall blocking technology, 2) adjust the methodology for significantly viewed station, 3) revising program carriage dispute resolution rules, 4) and adjust FCC rules to "facilitate next generation TV. </p><p>FCC chair Ajit Pai has circulated all those items for commissioner review before the meeting. </p><p><strong>1)</strong> The STIR/SHAKEN (formerly the more James Bondlike "SHAKEN/STIR") item is a report and order and further notice of proposed rulemaking (NPRM) that would "adopt rules requiring originating and terminating voice service providers to implement the STIR/SHAKEN caller ID authentication framework in the Internet Protocol portions of their networks; and (2) [in the FNPRM] propose additional measures to combat illegal spoofing, including measures to implement portions of the TRACED Act.</p><p>The item follows Congress' mandate in the TRACED Act that STIR/SHAKEN be made mandatory, and would set a June 30, 20201 deadline in alignment with the legislation. It would also extend STIR/SHAKEN to intermediate access providers. </p><p>The FCC has already voted unanimously to allow carriers to block robocalls by default via STIR/SHAKEN, but had made it voluntary.  </p><p><strong>2)</strong> The "Amending Distributed Transmission System Rules to Facilitate Next Generation TV" is an NPRM that seeks comment on whether to modify the Commission’s rules "governing the use of distributed transmission systems by broadcast television stations."  </p><p>The item would seek comment on amending the FCC's rules to allow DTS signals, which use multiple transmission sites in a market to boost a station's signal, to extend beyond a station's authorized service area by more than a de minimus amount. The National Association of Broadcasters and America's Public Television Stations petitioned the FCC for the change. </p><p>It would also seek input on the impact of the change on translator and LPTV stations. </p><p><strong>3)</strong> "Defining Significantly Viewed Local TV Stations" is an NPRM seeking comment on "whether to update the methodology for determining whether a television broadcast station is 'significantly viewed' in a community outside of its local market. </p><p>The syndicated and network programming on an out-of-market TV station imported into a local market must be deleted per syndicated and network exclusivity rules, unless the FCC determines that out-of-market stations also has significant viewership in that market. </p><p>The item seeks comment on, among other things, whether Nielsen or some other methodology should be used to determine "significantly viewed" status and whether terminology, like "independent station" or partial network station" should be updated given changes in the marketplace. </p><p><strong>4)</strong> "Revising Program Carriage Rules and Part 76 Review Procedures" is an FNPRM and NPRM – seeking comment on "whether to modify the Commission’s rules governing the resolution of program carriage disputes between video programming vendors and multichannel video programming distributors." </p><p>The item would seek comment on, again among several other things, whether to modify the time limit requirements for filing program carriage complaints to "clarify that it applies only in circumstances where there is not an existing program carriage contract or contract offer and a defendant MVPD has denied or failed to acknowledge either a request for program carriage or a request to negotiate for program carriage." </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Comcast and T-Mobile Announce STIR/SHAKEN Partnership to Combat Robocalling ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/comcast-and-t-mobile-join-forces-to-combat-robocalling</link>
                                                                            <description>
                            <![CDATA[ Comcast and T-Mobile Announce STIR/SHAKEN Partnership to Combat Robocalling ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">5LBsW1gAqASvgbMq4Nt3e4</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/f7AUsaNs2XonTB6aeEyTkP-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 17 Apr 2019 14:55:54 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Technology]]></category>
                                                                                                <author><![CDATA[ daniel.frankel@futurenet.com (Daniel Frankel) ]]></author>                    <dc:creator><![CDATA[ Daniel Frankel ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/7wBJVmzcn7E9PQZWPFQsH7.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/f7AUsaNs2XonTB6aeEyTkP-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/f7AUsaNs2XonTB6aeEyTkP-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>T-Mobile and Comcast have <a href="https://investor.t-mobile.com/news-and-events/t-mobile-us-press-releases/press-release-details/2019/T-Mobile-and-Comcast-FIRST-to-Give-Customers-New-Anti-Robocalling-Feature/default.aspx">announced</a> a partnership to combat robocalling by using the STIR/SHAKEN protocol to authenticate calls made between their respective networks.</p><p>“Robocalls and spam calls are an industry-wide problem, and we’ve got to join forces to keep consumers protected. Today, we’re the first to cross industry lines to do just that,” said T-Mobile CEO John Legere, in a statement.</p><p>Well, “first” is debatable. Comcast last month announced that it had jointly and successfully tested a collaborative STIR/SHAKEN effort with AT&T.</p><p><a href="https://www.nexttv.com/news/comcast-and-att-test-anti-robocalling-tech" data-original-url="https://www.multichannel.com/news/comcast-and-att-test-anti-robocalling-tech">Related: Comcast and AT&T Successfully Test Solution to Stop Robocalling</a></p><p>But there seems to be industry-wide consensus among telecom operators that robocalling is a problem for their customers, who last year suffered through 26 billion unwanted calls. In February, FCC Chairman Ajit Pai warned telecom companies that he would step in if they didn’t do something to combat the robocalling issue.</p><p>So what is STIR/SHAKEN?</p><p>STIR is short for Secure Telephony Identity Revisited. The SHAKEN acronym is a bit more of a reach—it stands for Secure Handling of Asserted (information using) Tokens. The “ken” in token comprises the last part of the acronym.</p><p>The protocol seeks to authenticate calls by using digital certificates that determine where the call actually originates from. If a caller is successfully authenticated, T-Mobile will display “Caller Verified” on the receiving user's smart phone. In its press release today, T-Mobile said it can now port this message into the caller ID displays of 10 smart phones, including the full line of Samsung Galaxy devices.</p><p>“Fraudulent robocalls hurt everyone, so we want to give consumers more power to protect themselves,” added Eric Schaefer, senior VP and GM of broadband and communications services at Comcast Cable. “Our engineers played a key role in developing this technology for the entire industry, and we are happy to work with T-Mobile to deliver another first in the fight against fraudulent robocalls. In the coming weeks, we’ll be exchanging authenticated calls with more providers across the industry as we come together to tackle this problem.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>