<?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/harold-feld" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Next TV in Harold-feld ]]></title>
                <link>https://www.nexttv.com/tag/harold-feld</link>
        <description><![CDATA[ All the latest harold-feld content from the Next TV team ]]></description>
                                    <lastBuildDate>Tue, 25 Jul 2017 13:50:00 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ Verizon Calls Optimization Tests Reasonable Net Management ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/verizon-calls-optimization-tests-reasonable-net-management-414190</link>
                                                                            <description>
                            <![CDATA[ Verizon Calls Optimization Tests Reasonable Net Management ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">7VQVdLSxNoGv8vHjjn541m</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/WtvxG7CvZvpMnuYeysznec-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 25 Jul 2017 13:50:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Technology]]></category>
                                                    <category><![CDATA[Policy]]></category>
                                                                                                <author><![CDATA[ john.eggerton@futurenet.com (John Eggerton) ]]></author>                    <dc:creator><![CDATA[ John Eggerton ]]></dc:creator>                                                                <dc:description><![CDATA[ http://cdn.mos.cms.futurecdn.net/ETjt8sjZcQr97v7yakQ4hP.jpg ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/WtvxG7CvZvpMnuYeysznec-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/WtvxG7CvZvpMnuYeysznec-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <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="WtvxG7CvZvpMnuYeysznec" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/WtvxG7CvZvpMnuYeysznec.jpg" mos="https://cdn.mos.cms.futurecdn.net/WtvxG7CvZvpMnuYeysznec.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p>Verizon is dismissing a net-neutrality group's characterizations of what the telco said were common network management tests.<br/><br/>Public Knowledge had jumped on reports that the wireless ISP was "throttling" video streaming services as part of a video optimization test, and had done so without warning to customers.<br/><br/>"Current net-neutrality rules clearly state that providers may employ reasonable network management practices to ensure that their networks and services run efficiently and work well for their customers," a Verizon spokesman said. "Video optimization is a non-discriminatory network management practice designed to ensure a high quality customer experience for all customers accessing the shared resources of our wireless network."<br/><br/>He said the company has let customers know about its various network practices, which are common in the industry, adding, "It's not in our interest to do anything to jeopardize the products or services that our customers rely each and every day.<br/><br/>Public Knowledge pointed out that the FCC staff, in the waning days of former chair Tom Wheeler's tenure, had set out guidelines for reasonable network management, including evaluating video optimization, but that new FCC chair Ajit Pai had rescinded that report.<br/><br/>"ISPs need to know that tests to improve their system or develop new products won’t be mistaken for by their customers for bad behavior that undermines confidence in the network," Public Knowledge senior vice president Harold Feld said. “The guidelines distinguishing ‘throttling’ from ‘reasonable network management’ developed as part of the FCC’s investigation into T-Mobile’s Binge On service provided precisely this certainty.... Before, Verizon could simply point to the FCC guidelines to reassure their customers. Today, we must look to chairman Pai to tell us whether subscribers have anything more to rely on than Verizon’s promises."<br/><br/>Feld said that was one reason Pai should not try to roll back the Open Internet order or its Title II underpinning.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Title II's Full-‘Throttle’ History ]]></title>
                                                                                                                                                                                                <link>https://www.nexttv.com/news/title-iis-full-throttle-history-391470</link>
                                                                            <description>
                            <![CDATA[ Title II's Full-‘Throttle’ History ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">9FZ1M8RoMR22z3stHxE4JV</guid>
                                                                                                                            <pubDate>Wed, 17 Jun 2015 17:00:00 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Technology]]></category>
                                                    <category><![CDATA[Policy]]></category>
                                                    <category><![CDATA[Marketing]]></category>
                                                                                                <author><![CDATA[ john.eggerton@futurenet.com (John Eggerton) ]]></author>                    <dc:creator><![CDATA[ John Eggerton ]]></dc:creator>                                                                <dc:description><![CDATA[ http://cdn.mos.cms.futurecdn.net/ETjt8sjZcQr97v7yakQ4hP.jpg ]]></dc:description>
                                                                                                                                                                                                                                                                        <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>RELATED STORIES:</strong></p><p><a href="https://www.nexttv.com/news/twc-threatened-net-neutrality-complaint-391423" data-original-url="https://www.multichannel.com/news/twc-threatened-net-neutrality-complaint-391423">TWC Threatened With Net-Neutrality Complaint</a></p><p>Level 3: No Net-Neutrality Complaints — Yet</p><p>On June 12, the Federal Communications Commission was empowered to start enforcing its new Title II-based network-neutrality rules after a federal court denied a last-minute stay request.</p><p>That raised the question of how “throttling” became the term of art for what was referred to as “unreasonable discrimination” in the FCC’s 2010 order, and what’s been referred to generally as “degrading” — as in “no blocking or degrading or paid prioritization” — in network-neutrality debate parlance.</p><p>The migration from “unreasonable discrimination” made sense because the court frowned on the language, but “degrading” didn’t appear to have been undercut as a catch-all.</p><p>The term “throttling” has always been around, said Tim Karr, senior director of strategy at Washington, D.C.-based advocacy group Free Press and a veteran of the network-neutrality wars. “[W]e have used all of these terms throughout the history of this debate, using whichever is more appropriate in describing a particular circumstance,” Karr said.</p><p>But throttling’s stock has clearly risen since the first 2010 net-neutrality order.</p><p>No lesser a net-neutrality term-of-art aficionado than Public Knowledge’s Harold Feld — who, like Karr, has been a net-neutrality proponent for years — pronounced it a “good question.” That provided just the sort of positive reinforcement that has driven investigative journalists to pursue such semantic conundrums as why advertisers think they can hide their “sales” behind the pretentious cloak of “savings event.” But we digress.</p><p>Feld said he thinks it dates from the reaction to wireless carriers’ usage plans — wireless broadband is now regulated under the net-neutrality rules, so it would make sense for the catch-all phrase to have morphed as well.</p><p>“I think it came up when the wireless carriers started throttling unlimited plans when they went over some undefined ‘cap,’ ” Feld told <em>Multichannel News</em>. “The idea was that ‘throttling’ was different from degrading because [throttling] just reduced overall speed/capacity rather than actually disrupting the transmission, as Comcast did with BitTorrent.”</p><p>One cable veteran thought the transition point was when FCC chairman Tom Wheeler got so much pushback on the “commercial reasonableness” standard that the FCC “needed something else besides ‘no blocking.’ ”</p><p>Whatever you call it, cable operators wish the definition excluded Title II.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>