<?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.tvtechnology.com/feeds/tag/common-alerting-protocol" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Common-alerting-protocol ]]></title>
                <link>https://www.tvtechnology.com/tag/common-alerting-protocol</link>
        <description><![CDATA[ All the latest common-alerting-protocol content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Tue, 05 Nov 2019 18:28:21 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ FCC Reveals 60-Day Grace Period for IPAWS Update ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/fcc-reveals-60-day-grace-period-for-ipaws-update</link>
                                                                            <description>
                            <![CDATA[ The quick turnaround for a recent update had many EAS participants worried. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">aTSDLMzUzvppcGm8oFgA5W</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/wbK7xwCRgzaTMbBxqGL9kR-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 05 Nov 2019 18:28:21 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Regulatory &amp; Legal]]></category>
                                                                                                                    <dc:creator><![CDATA[ Michael Balderston ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/wbK7xwCRgzaTMbBxqGL9kR-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/wbK7xwCRgzaTMbBxqGL9kR-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON—</strong>EAS participants who are not able to update to the <a href="https://www.tvtechnology.com/news/updated-ipaws-certificate-released-for-dasdec-onenet">IPAWS certificate</a> that was released on Oct. 28 by the applied deadline of Nov. 8 will not turn into the proverbial pumpkin when the clock strikes midnight, according to a Public Notice from the FCC.</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="wbK7xwCRgzaTMbBxqGL9kR" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/wbK7xwCRgzaTMbBxqGL9kR.jpg" mos="https://cdn.mos.cms.futurecdn.net/wbK7xwCRgzaTMbBxqGL9kR.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p>In the notice from the Public Safety and Homeland Security Bureau of the FCC, it was revealed that there are specific guidelines regarding equipment readiness that will allow EAS participants to continue to operate without the impacted, required equipment for a period of 60 days after the Nov. 8 deadline.</p><p>The issue of this public notice came after FEMA and some EAS participants expressed concern over the time frame from when the update was made available and the deadline that was set, saying that it was not sufficient time. As a result, the FCC issued the public notice to inform EAS participants about Section 11.35(b) of the commission’s rules, which allow for operations to continue “without the defective equipment pending its repair or replacement for 60 days without further FCC authority.”</p><p>As a result, EAS participants unable to make the IPAWS update prior to Nov. 8 will have until Jan. 7, 2020, to do so. In the event that they are not able to meet that deadline, an informal request for additional time must be submitted to the FCC and explain what steps have been taken, the alternative procedures being used while equipment has been defective and when the defective equipment will be repaired or replaced.</p><p>The update, and the subsequent operation without proper equipment in the situation of an extension, only applies to Common Alerting Protocol-formatted alerts distributed by IPAWS; EAS participants must still monitor, receive and process legacy EAS alerts formatted in the EAS protocol.</p><p>More information can be found in the FCC’s official <a href="https://docs.fcc.gov/public/attachments/DA-19-1144A1.pdf">Public Notice</a>.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ FCC Working Group Report ‘Re-imagines’ Emergency Alerting ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/fcc-working-group-report-re-imagines-emergency-alerting</link>
                                                                            <description>
                            <![CDATA[ Among other things, the report examines the potential of Next Gen TV and the efforts of PBS ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">dAyejuRNj61WK65V3EW3ir</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 20 Jul 2018 21:12:51 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Mergers &amp; Acquisitions]]></category>
                                                    <category><![CDATA[Business]]></category>
                                                                                                                    <dc:creator><![CDATA[ Phil Kurz ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/sNtEgpne6F9EezmB5uHeVM.png ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON</strong> — A <a href="https://www.fcc.gov/files/csric6wg29junereportcomppdf">new report</a> from a working group of the FCC’s Communications Security, Reliability and Interoperability Council (CSRIC) lays out a new vision for alerting the public in times of emergency and explores how the new ATSC 3.0 television standard can play a major role.</p><p>“The ATSC 3.0 (AKA Next Gen TV) standard holds the potential to not only vastly improve the broadcast television viewing experience and expand programming opportunities, but also enhance emergency communications capabilities and create new operational capabilities for broadcast stations,” it says.</p><p>The report, “Comprehensive Re-imagining of Emergency Alerting,” identifies three ways the Next Gen TV standard supports distribution of emergency information, including EAS support, advanced emergency services, such as Advanced Emergency Alerting (AEA), and CAP (Common Alerting Protocol) relay via 3.0’s native IP transport capability.</p><p><a href="https://www.tvtechnology.com/news/public-tv-raises-concern-over-possible-wea-enhancement"><strong><em>[Read: Public TV Raises Concern Over Possible WEA Enhancement]</em></strong></a></p><p>The standard’s support for advanced emergency information services offers “a powerful tool” to target any type of emergency information beyond typical emergency alerts to TV viewers. “This is an informational service capable of conveying a broad range of urgent information bulletins and updates to targeted audiences,” the report says.</p><p>When it comes to Advanced Emergency Alerting, 3.0 offers broadcasters a way to reach fixed, mobile and portable consumer devices with audience-targeted messages, alerts flexible enough for nearly any form of emergency information, location-targeted alerts, support for multimedia content such as graphics, photos, maps and video, alert updates, multilingual messaging and a wake-up signal to awaken receivers in standby or sleep mode, it says.</p><p>The report notes that 3.0 deployment is voluntary and that the working group expects EAS “to continue to provide its essential functions for national and local public alert and warning.” It envisions 3.0-based alerting as “a value-added function from television broadcasters.”</p><p>Among the other topics covered in the document is the role PBS and local public television stations play in helping to protect communities by datacasting to deliver information to individuals and first responders.</p><p>The report lays out the main features of PBS-WARN, which takes advantage of the nationwide public TV interconnection system to provide for a nationwide emergency alerting network that serves as a redundant backup path for the Wireless Emergency Alerts (WEA) C interface, which is technologically diverse from the Commercial Mobile Service Provider’s primary WEA gateway.</p><p>The document describes various instances of public broadcasters partnering with first responders in different locales to enable responders to send information and video via datacasts in emergency situations. Instances noted in the report include OEAS Public Alertnet with ties to all eight Ohio public TV licenses and their 12 stations, as well as other examples in Alabama, Maine, Minnesota, Nevada and Texas.</p><p>The working group’s report notes public TV stations choosing to deploy Next Gen TV will be able to provide even more robust emergency alert and communications service to first responders and the public. For example, 3.0 will allow them to operate more efficiently in terms of TV bandwidth usage, which could allow additional Common Alert Protocol feeds of national, regional and statewide data pertaining to alerts.</p><p>“Because PBS has already implemented an intersection of traditional broadcast and cellular technologies through the nationwide PBS-WARN system, we believe that public media has shown itself [to] be an ideal vehicle for projects which explore alerting and the intersection of the next generations of traditional broadcast (ATSC 3.0) and Cellular Mobile Service (5G),” says the report.</p><p>America’s Public Television Stations (APTS) issued a statement July 19 lauding the report. “The extraordinary technological achievement of ATSC 3 will enhance public safety communications and interoperability capabilities for law enforcement. Public television is already experimenting with the new services this broadcast standard makes possible,” says Patrick Butler, APTS president and CEO.</p><p>The report is available on the FCC <a href="https://www.fcc.gov/files/csric6wg29junereportcomppdf">website</a>.</p><p><a href="https://www.b2bmediaportal.com/nbmedia/subscribe.aspx"><em><strong>[Want more information like this? Subscribe to our newsletter and get it delivered right to your inbox.]</strong></em></a></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Monroe Issues New EAS Credentials File for OneNet and DASDEC Devices ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/equipment/monroe-issues-new-eas-credentials-file-for-onenet-and-dasdec-devices</link>
                                                                            <description>
                            <![CDATA[ Users must download and install file before June 24 for uninterrupted operation ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">ia4PTN3cFzk5gN9TdvLrV4</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/DL5RJjjgDUnjavZcPesfn3-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Mon, 11 Jun 2018 20:29:46 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Business]]></category>
                                                                                                                    <dc:creator><![CDATA[ Claudia Kienzle ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/aww8skeHUBpDVHq2LAGCeB.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/DL5RJjjgDUnjavZcPesfn3-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/DL5RJjjgDUnjavZcPesfn3-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>LYNDONVILLE, N.Y.</strong> — As providers of Emergency Alert System/Common Alerting Protocol equipment, Monroe Electronics — and its Digital Alert Systems subsidiary — are advising users of their OneNet and DASDEC EAS/CAP systems to download the <a href="https://www.digitalalertsystems.com/resources_fsb.html" data-original-url="http://www.digitalalertsystems.com/resources_fsb.html">latest Integrated Public Alert and Warning System Certificate Authority (CA) credentials file</a>.</p><p>Users must install these new digital CA credentials, recently issued by The Federal Emergency Management Agency — the administrator of IPAWS — in order to replace the previously issued version, which is set to expire on June 24.</p><p>Maintaining the most recent CA credentials is essential to ensuring that OneNet and DASDEC EAS/CAP encoders and decoders continue to operate properly. These devices use these digital certificates to validate the authenticity of IPAWS sourced Common Alerting Protocol alerts.</p><p>IPAWS users who fail to update their equipment before June 24 could see the error message: “Event Log: Digital Signature VERIFICATION ERROR : Signer UNTRUSTED! Check for correct CAP decoder CA file.;”</p><p>This is because FEMA uses digital CA certificates to create a “chain of trust between Emergency Alert System devices and the IPAWS servers.” According to FEMA IPAWS is an internet-based system that enables federal, state, and local authorities to issue critical public alerts and warnings. It’s accessed through software that meets IPAWS system requirements.</p><p>“We have been advised there will be several certificate and policy changes through the end of 2018 that will necessitate some certificate updates during this period,” said Ed Czarnecki, senior director of strategy and government affairs for Monroe Electronics and Digital Alert Systems.</p><p>Czarnecki added, “We’re constantly evaluating and updating our systems to stay in step with IPAWS, and since assisting customers is our top priority, we are actively working on new methods of managing government certificates with an improved path forward.”</p><p>All OneNet and DASDEC customers using the IPAWS system must have the latest digital certificates in place to assure the validity of the communications chain of trust, which prevents a “man in the middle” attack by only processing the messages that are authenticated through the IPAWS system.</p><p><a href="https://www.b2bmediaportal.com/nbmedia/subscribe.aspx"><em><strong>[Want more information like this? Subscribe to our newsletter and get it delivered right to your inbox.]</strong></em></a></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>