<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: DPI can be misused – so can a hammer</title>
	<atom:link href="http://dpi.priv.gc.ca/index.php/essays/dpi-can-be-misused-%e2%80%93-so-can-a-hammer/feed/" rel="self" type="application/rss+xml" />
	<link>http://dpi.priv.gc.ca/index.php/essays/dpi-can-be-misused-%e2%80%93-so-can-a-hammer/</link>
	<description>Essays on Deep Packet Inspection</description>
	<lastBuildDate>Tue, 29 Jun 2010 17:04:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Lewis</title>
		<link>http://dpi.priv.gc.ca/index.php/essays/dpi-can-be-misused-%e2%80%93-so-can-a-hammer/comment-page-1/#comment-143</link>
		<dc:creator>Chris Lewis</dc:creator>
		<pubDate>Fri, 09 Apr 2010 02:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://dpi.priv.gc.ca/?p=258#comment-143</guid>
		<description>The reality is that it&#039;s almost exactly the reverse.   Most of the egregious problems we see, DNS redirections, advertising substitution, penalizing certain sites et. al. isn&#039;t done with DPI, it&#039;s done with other far simpler techniques.   Such as QOS, priority management, local DNS substitution and IP and port redirection/blackholing.  Most of which are simple and relatively inexpensive to implement even in very large networks.  DPI requires considerable investment, and the volumes involved are huge. For the most part, the primary incentive for doing it is for automated detection, analysis and blocking malicious packets that either endanger the ISP&#039;s network, or their users, or both.

As I said, these (QOS, DPI, port redirection, DNS redirection) are all just tools.  As a society, we need to decide what these tools should be allowed to do/not do, _not_ which tools are used.</description>
		<content:encoded><![CDATA[<p>The reality is that it&#8217;s almost exactly the reverse.   Most of the egregious problems we see, DNS redirections, advertising substitution, penalizing certain sites et. al. isn&#8217;t done with DPI, it&#8217;s done with other far simpler techniques.   Such as QOS, priority management, local DNS substitution and IP and port redirection/blackholing.  Most of which are simple and relatively inexpensive to implement even in very large networks.  DPI requires considerable investment, and the volumes involved are huge. For the most part, the primary incentive for doing it is for automated detection, analysis and blocking malicious packets that either endanger the ISP&#8217;s network, or their users, or both.</p>
<p>As I said, these (QOS, DPI, port redirection, DNS redirection) are all just tools.  As a society, we need to decide what these tools should be allowed to do/not do, _not_ which tools are used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M B A</title>
		<link>http://dpi.priv.gc.ca/index.php/essays/dpi-can-be-misused-%e2%80%93-so-can-a-hammer/comment-page-1/#comment-113</link>
		<dc:creator>M B A</dc:creator>
		<pubDate>Fri, 07 Aug 2009 06:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://dpi.priv.gc.ca/?p=258#comment-113</guid>
		<description>I certainly agree with you but dealing with thee threats is also possible without DPI. 
and right now the ISPs are not really using this tehcnology for that exactly. instead they`re perverting it and using it to hinder their user&#039;s (other ISP&#039;s users fot that matter ) internet experience. choosing in the user&#039;s place what he can use or can&#039;t use with his purchased bandwidth.  and no body is stopping them.
As somebody said is post canada allowed to open everyone&#039;s mail and check it to see if it&#039;s dangerous or important enough to deliver it?
the answer is obviously no.

It is true most certainly that P2P traffic  can certainly be cumbersom (Bittorrent for instance fills up conection queues very quickly-- depending)  but there are other methods  to do so. QOS and Priority Queus are one of these (personallyI use that to balance the traffic in my network). should I need an SSH connection I can without halting any P2P traffic  as I gave SSh high priority and if I don;t ... well P2P traffic can flow as quick as it can.  and everybody is happy.
Which is not the case with ISPs. Actualy only one taht is afecting others using his position as leader in that market. If some ISP decided to put that for his client I don;t see why other ISP`s client should suffer from that.</description>
		<content:encoded><![CDATA[<p>I certainly agree with you but dealing with thee threats is also possible without DPI.<br />
and right now the ISPs are not really using this tehcnology for that exactly. instead they`re perverting it and using it to hinder their user&#8217;s (other ISP&#8217;s users fot that matter ) internet experience. choosing in the user&#8217;s place what he can use or can&#8217;t use with his purchased bandwidth.  and no body is stopping them.<br />
As somebody said is post canada allowed to open everyone&#8217;s mail and check it to see if it&#8217;s dangerous or important enough to deliver it?<br />
the answer is obviously no.</p>
<p>It is true most certainly that P2P traffic  can certainly be cumbersom (Bittorrent for instance fills up conection queues very quickly&#8211; depending)  but there are other methods  to do so. QOS and Priority Queus are one of these (personallyI use that to balance the traffic in my network). should I need an SSH connection I can without halting any P2P traffic  as I gave SSh high priority and if I don;t &#8230; well P2P traffic can flow as quick as it can.  and everybody is happy.<br />
Which is not the case with ISPs. Actualy only one taht is afecting others using his position as leader in that market. If some ISP decided to put that for his client I don;t see why other ISP`s client should suffer from that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
