<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.fiercevoip.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Acceptable Behavior</title>
 <link>http://www.fiercevoip.com/tags/acceptable-behavior</link>
 <description></description>
 <language>en</language>
<item>
 <title>VoIP and the FCC Comcast Ruling</title>
 <link>http://www.fiercevoip.com/story/voip-and-fcc-comcast-ruling/2008-08-03?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FV0</link>
 <description>&lt;p&gt;It&#039;s OK to give VoIP traffic priority over other Internet traffic, says the Federal Communications Commission (FCC). &amp;nbsp;But, how do you tell if it is VoIP traffic in the first place?&lt;/p&gt;
&lt;p&gt;CircleID parses through the FCC order issued to Comcast, abet with some brightly colored commentary. &amp;nbsp;FCC Chairman Kevin Martin says it would be OK for networks to prioritize VoIP traffic.&amp;nbsp; But the FCC&#039;s own press release says network applications should be treated equally, rather than &quot;discriminate&quot; among applications.&lt;/p&gt;
&lt;p&gt;A further mystery arises when it comes to figuring out what packets should get priority over others--assuming, of course, that you can do so. The FCC&#039;s press release quotes Professor David Reed of the Massachusetts Institute of Technology as saying that deep packet inspection (DPI) is not &quot;acceptable behavior.&quot; It does beg the question of what you need to do to figure out what&#039;s in a packet in the first place in order to give it priority.&lt;/p&gt;
&lt;p&gt;For more:&lt;br /&gt;- Read the CircleID piece parsing the &lt;a href=&quot;http://www.circleid.com/posts/88103_fcc_comcast_ruling_inconsistent_incoherent/&quot;&gt;FCC Comcast ruling&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Related articles:&lt;br /&gt;&lt;/strong&gt;Comcast, Vonage reach &lt;a href=&quot;http://www.fiercetelecom.com/story/comcast-vonage-reach-traffic-management-understanding/2008-07-09&quot;&gt;traffic management understanding&lt;/a&gt;&lt;br /&gt; FCC targets &lt;a href=&quot;http://www.fiercevoip.com/story/fcc-targets-transparency-for-network-management/2008-03-10&quot;&gt;transparency for network management&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.fiercevoip.com/story/voip-and-fcc-comcast-ruling/2008-08-03#comments</comments>
 <category domain="http://www.fiercevoip.com/tags/acceptable-behavior">Acceptable Behavior</category>
 <category domain="http://www.fiercevoip.com/tags/comcast">Comcast</category>
 <category domain="http://www.fiercevoip.com/tags/dpi">DPI</category>
 <category domain="http://www.fiercevoip.com/tags/fcc">FCC</category>
 <category domain="http://www.fiercevoip.com/tags/federal-communications-commission">Federal Communications Commission</category>
 <category domain="http://www.fiercevoip.com/tags/traffic-priority">Traffic Priority</category>
 <category domain="http://www.fiercevoip.com/tags/voip-regulation-0">VoIP Regulation;</category>
 <pubDate>Sun, 03 Aug 2008 17:38:01 -0400</pubDate>
 <dc:creator>Doug Mohney</dc:creator>
 <guid isPermaLink="false">2650 at http://www.fiercevoip.com</guid>
</item>
</channel>
</rss>
