<?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: &#8216;DPI is necessary&#8217; &#8211; Sandvine</title>
	<atom:link href="http://www.p2pnet.net/story/21162/feed" rel="self" type="application/rss+xml" />
	<link>http://www.p2pnet.net/story/21162</link>
	<description>p2pnet.net - reader powered</description>
	<lastBuildDate>Wed, 01 Feb 2012 15:11:09 -0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Christopher Parsons</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973653</link>
		<dc:creator>Christopher Parsons</dc:creator>
		<pubDate>Fri, 08 May 2009 23:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973653</guid>
		<description>It seems to me that it would be valuable to look at different DPI appliances to hone arguments for and against the technology more broadly - the appliances are *not* all made the same. Some of iPoque&#039;s devices, for example, are capable of the forensic analysis that has been alluded to in this post, some are not (DPX Network Probes are better able at forensics, PRX devices not so much). Also, when we&#039;re talking about DPI it is critically important to distinguish between: (a) devices&#039; theoretical capabilities; (b) how ISPs have actually deployed them. Further, DPI vendors themselves often produce whitepapers that demonstrate that they are engaging with privacy, copyright, and other issues of the day. I&#039;ve fairly recently looked at a few of iPoque&#039;s whitepapers (just happens to be where I am on &#039;things to read&#039; research list) and analyzed and critiqued them at the following: 

http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-copyright/
http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-encryption/
http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-bandwidth-management/

Looking CRTC submissions, it isn&#039;t immediately apparent to me that ISPs have particularly detailed consumer logs. ISPs have a tendency to aggregate data sets, with most individuated alerts about network uses coming up when something &#039;weird&#039; appears (e.g. when a computer attached the network is infested with hostile code and starts spamming the network, that activity is seen and the computer removed from the network until the issue is cleared up). Don&#039;t get me wrong - if we read whitepapers from actual DPI vendors we can see that there is the potential to do really unpleasant things, including *very* detailed user tracking. The concern is that, once these devices are in place, third-parties will be able to exert influence and have ISPs actually begin tracking users in a very granular fashion. This is an entirely justified and legitimate worry, but isn&#039;t one that necessarily follows from inserting any old DPI appliance in a network - certain vendors&#039; products can do this easily, others cannot.

As a note: in terms of encrypted traffic it is possible for many DPI appliances to identify what program is attempting to establish a connection based on the initial exchange of packets between programs. This is one of the key ways that Skype is identified, as well as some P2P protocols. In these cases, there is a heuristic analysis of packet sizes and transmissions - if this analysis is performed and an appliance applies its rulesets without creating a consumer profile (X customer used Skype on days A,B,C,D,etc) has there been an infringement on the consumer&#039;s privacy? (This is an open question - I&#039;m not trying to be rhetorical, just trying to open up a bit what we mean by &#039;privacy&#039; in these discussions.)</description>
		<content:encoded><![CDATA[<p>It seems to me that it would be valuable to look at different DPI appliances to hone arguments for and against the technology more broadly &#8211; the appliances are *not* all made the same. Some of iPoque&#8217;s devices, for example, are capable of the forensic analysis that has been alluded to in this post, some are not (DPX Network Probes are better able at forensics, PRX devices not so much). Also, when we&#8217;re talking about DPI it is critically important to distinguish between: (a) devices&#8217; theoretical capabilities; (b) how ISPs have actually deployed them. Further, DPI vendors themselves often produce whitepapers that demonstrate that they are engaging with privacy, copyright, and other issues of the day. I&#8217;ve fairly recently looked at a few of iPoque&#8217;s whitepapers (just happens to be where I am on &#8216;things to read&#8217; research list) and analyzed and critiqued them at the following: </p>
<p><a href="http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-copyright/" rel="nofollow">http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-copyright/</a><br />
<a href="http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-encryption/" rel="nofollow">http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-encryption/</a><br />
<a href="http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-bandwidth-management/" rel="nofollow">http://www.christopher-parsons.com/blog/technology/analysis-ipoque-dpi-and-bandwidth-management/</a></p>
<p>Looking CRTC submissions, it isn&#8217;t immediately apparent to me that ISPs have particularly detailed consumer logs. ISPs have a tendency to aggregate data sets, with most individuated alerts about network uses coming up when something &#8216;weird&#8217; appears (e.g. when a computer attached the network is infested with hostile code and starts spamming the network, that activity is seen and the computer removed from the network until the issue is cleared up). Don&#8217;t get me wrong &#8211; if we read whitepapers from actual DPI vendors we can see that there is the potential to do really unpleasant things, including *very* detailed user tracking. The concern is that, once these devices are in place, third-parties will be able to exert influence and have ISPs actually begin tracking users in a very granular fashion. This is an entirely justified and legitimate worry, but isn&#8217;t one that necessarily follows from inserting any old DPI appliance in a network &#8211; certain vendors&#8217; products can do this easily, others cannot.</p>
<p>As a note: in terms of encrypted traffic it is possible for many DPI appliances to identify what program is attempting to establish a connection based on the initial exchange of packets between programs. This is one of the key ways that Skype is identified, as well as some P2P protocols. In these cases, there is a heuristic analysis of packet sizes and transmissions &#8211; if this analysis is performed and an appliance applies its rulesets without creating a consumer profile (X customer used Skype on days A,B,C,D,etc) has there been an infringement on the consumer&#8217;s privacy? (This is an open question &#8211; I&#8217;m not trying to be rhetorical, just trying to open up a bit what we mean by &#8216;privacy&#8217; in these discussions.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973649</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Fri, 08 May 2009 20:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973649</guid>
		<description>I am sorry but being a pro p2p downloader against DPI is like a transport carrier being opposed to d.o.t. weight limits on roads. Unless you work for an ISP and understand the growth problems and how the IP protocol works, you really can&#039;t claim to know what you are talking about. 

Please take a CISCO CCNA course before saying things like &quot;WTF??? How the hell can inspecting a packet help you take an IPv4 address and put it on an IPv6 network without modifying the contents of the packet? And I thought you just said in point 6 you donât inspect the content? How do you even know itâs an IPv4 packet then?&quot; 
The 4 bits of an IP packet (in the header, not the DATA portion of the packet)  tells you what version of IP protocol is being used. If you say that reading thoes 4 bits is a privacy violation you might be more concerned to know every router will read further into the packet to decide where to forward that packet... if you take the header of an IPV4 packet, and rip it off, and exchange it with a header with &#039;similar&#039; information, but using 128bit addresses and changing the first 4 bits to 0110... you performed some level of packet inspection and created a IPV4-IPV6 router. I am sorry you feel the internet is a giant privacy concern to you and that your pornz have been slowed. Also sending a packet with the reset bit set in the header is only impersonating the ISP&#039;s own IP address (which they would also own the product) to the other ISP.  

Instead of being confused and wrong, please get some real world education. We have a great university in Waterloo, you probably already know that because you also got drunk at a Sandvine recruiting event where you heard about that &quot;database product&quot; and came to your own drunken suspicions.

Sadly shepd you are embarrasing my hometown as well. Using shortforms as STFU, WTF etc. just take away any credibility you build.
 
The internet was never designed to be last mile to last mile. It was designed to connect in a &quot;mesh&quot;. Instead of mopeing about DPI you should be more concerned about the monopolies owning the last mile of network. Call group telecoms old number... press 1 for sales and get rogers... 2 for support and get Bell. Rogers owns GT. Charter communications filed for chapter 11. Bell has filed a tarrif for &quot;Usage based billing&quot; in which they will be billing wholesale DSL ISPs for Data usage on the last mile. ISPs still pay for the data usage to their transit providers. Congestion during peak hours means an internet provider may not be able to provide resonable VOIP experience unless other non real-time protocols are managed.

If your post office was overloaded but could prioritize bills and cheques over junk mail, would you not want that so the bills and cheques arrived on time... also keeping in mind the junk mail keeps the post office from losing billions of dollars a year.</description>
		<content:encoded><![CDATA[<p>I am sorry but being a pro p2p downloader against DPI is like a transport carrier being opposed to d.o.t. weight limits on roads. Unless you work for an ISP and understand the growth problems and how the IP protocol works, you really can&#8217;t claim to know what you are talking about. </p>
<p>Please take a CISCO CCNA course before saying things like &#8220;WTF??? How the hell can inspecting a packet help you take an IPv4 address and put it on an IPv6 network without modifying the contents of the packet? And I thought you just said in point 6 you donât inspect the content? How do you even know itâs an IPv4 packet then?&#8221;<br />
The 4 bits of an IP packet (in the header, not the DATA portion of the packet)  tells you what version of IP protocol is being used. If you say that reading thoes 4 bits is a privacy violation you might be more concerned to know every router will read further into the packet to decide where to forward that packet&#8230; if you take the header of an IPV4 packet, and rip it off, and exchange it with a header with &#8217;similar&#8217; information, but using 128bit addresses and changing the first 4 bits to 0110&#8230; you performed some level of packet inspection and created a IPV4-IPV6 router. I am sorry you feel the internet is a giant privacy concern to you and that your pornz have been slowed. Also sending a packet with the reset bit set in the header is only impersonating the ISP&#8217;s own IP address (which they would also own the product) to the other ISP.  </p>
<p>Instead of being confused and wrong, please get some real world education. We have a great university in Waterloo, you probably already know that because you also got drunk at a Sandvine recruiting event where you heard about that &#8220;database product&#8221; and came to your own drunken suspicions.</p>
<p>Sadly shepd you are embarrasing my hometown as well. Using shortforms as STFU, WTF etc. just take away any credibility you build.</p>
<p>The internet was never designed to be last mile to last mile. It was designed to connect in a &#8220;mesh&#8221;. Instead of mopeing about DPI you should be more concerned about the monopolies owning the last mile of network. Call group telecoms old number&#8230; press 1 for sales and get rogers&#8230; 2 for support and get Bell. Rogers owns GT. Charter communications filed for chapter 11. Bell has filed a tarrif for &#8220;Usage based billing&#8221; in which they will be billing wholesale DSL ISPs for Data usage on the last mile. ISPs still pay for the data usage to their transit providers. Congestion during peak hours means an internet provider may not be able to provide resonable VOIP experience unless other non real-time protocols are managed.</p>
<p>If your post office was overloaded but could prioritize bills and cheques over junk mail, would you not want that so the bills and cheques arrived on time&#8230; also keeping in mind the junk mail keeps the post office from losing billions of dollars a year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973318</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Mon, 04 May 2009 12:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973318</guid>
		<description>This discussion, and a new topic of interest in based on this topic, is continued over here:

http://www.p2pnet.net/story/21212</description>
		<content:encoded><![CDATA[<p>This discussion, and a new topic of interest in based on this topic, is continued over here:</p>
<p><a href="http://www.p2pnet.net/story/21212" rel="nofollow">http://www.p2pnet.net/story/21212</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devil's Advocate</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973190</link>
		<dc:creator>Devil's Advocate</dc:creator>
		<pubDate>Sat, 02 May 2009 18:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973190</guid>
		<description>&quot;Itâs retained for a certain amount of time, in case the same person (or someone else) requests it soon afterward&quot;

The &quot;content caching&quot; you&#039;re talking about doesn&#039;t capture user data, it only caches the static elements of a popular site&#039;s webpage, and that kind of stuff, and retaining it on geographically dispersed servers, with the intention of speeding up all the instances of that page being called.  It&#039;s got nothing to do with the users that access them.  (Other names for this are &quot;content delivery&quot; and &quot;content distribution service&quot;.)

&quot;Every ISP in the world has the capability in their network to single out a user and monitor their traffic&quot;

The &quot;capability&quot; to do this comes from procedures they need to perform, and not from any mechanism that is in place and waiting to be used on &quot;everybody&quot; on the fly.  Monitoring is done, by law and court order only, when cause has been presented (complaints, police investigation, etc.).  Anything else would currently not be legal in Canada (not sure about the US now, where the Patriot Act seems to have perverted everything).

The provider needs to actually intercept data packets from and to the user in question (using the right packet headers), and copy and forward those packets to a computer, which would assemble and &quot;recreate&quot; what the user would be getting from them.  They need to know who they&#039;re looking for first, and sort his activities to find and reconstruct what they&#039;re looking for.  That&#039;s how they trace child porn traffic for the RCMP.

&quot;...what is the specific privacy loss?&quot;

DPI equipment inspects each packet, logs content types and all packet headers, and keeps a record of individual user activity summaries.  These summaries make it much easier to retrieve those packets that are still in cache, and it has been discussed that the packet caching (which I erroneously thought you were talking about before) be done for longer periods of time, thereby raising the question that our personal activities and privacy would no longer be considered as important as things like delivering countless &quot;targetted&quot; ads, or suing copyright infringers, while using the spin &quot;finding child predators&quot; as an incentive to overlook the all the other obvious implications.

DPI takes away the &quot;dumb pipe&quot; quality of a provider, as it saves individually-targetted and specific information on not only a network&#039;s paying customers, but on those whose traffic needs to peer with that network.  DPI takes away the &quot;anonymity&quot; of the current packet transfer protocol by IDENTIFYING EACH USER it collects logs on, and by INTERCEPTING TRAFFIC to do so.

The privacy issues are endless.
And, by the very definition of what DPI does, it should be considered a violation of current privacy law.</description>
		<content:encoded><![CDATA[<p>&#8220;Itâs retained for a certain amount of time, in case the same person (or someone else) requests it soon afterward&#8221;</p>
<p>The &#8220;content caching&#8221; you&#8217;re talking about doesn&#8217;t capture user data, it only caches the static elements of a popular site&#8217;s webpage, and that kind of stuff, and retaining it on geographically dispersed servers, with the intention of speeding up all the instances of that page being called.  It&#8217;s got nothing to do with the users that access them.  (Other names for this are &#8220;content delivery&#8221; and &#8220;content distribution service&#8221;.)</p>
<p>&#8220;Every ISP in the world has the capability in their network to single out a user and monitor their traffic&#8221;</p>
<p>The &#8220;capability&#8221; to do this comes from procedures they need to perform, and not from any mechanism that is in place and waiting to be used on &#8220;everybody&#8221; on the fly.  Monitoring is done, by law and court order only, when cause has been presented (complaints, police investigation, etc.).  Anything else would currently not be legal in Canada (not sure about the US now, where the Patriot Act seems to have perverted everything).</p>
<p>The provider needs to actually intercept data packets from and to the user in question (using the right packet headers), and copy and forward those packets to a computer, which would assemble and &#8220;recreate&#8221; what the user would be getting from them.  They need to know who they&#8217;re looking for first, and sort his activities to find and reconstruct what they&#8217;re looking for.  That&#8217;s how they trace child porn traffic for the RCMP.</p>
<p>&#8220;&#8230;what is the specific privacy loss?&#8221;</p>
<p>DPI equipment inspects each packet, logs content types and all packet headers, and keeps a record of individual user activity summaries.  These summaries make it much easier to retrieve those packets that are still in cache, and it has been discussed that the packet caching (which I erroneously thought you were talking about before) be done for longer periods of time, thereby raising the question that our personal activities and privacy would no longer be considered as important as things like delivering countless &#8220;targetted&#8221; ads, or suing copyright infringers, while using the spin &#8220;finding child predators&#8221; as an incentive to overlook the all the other obvious implications.</p>
<p>DPI takes away the &#8220;dumb pipe&#8221; quality of a provider, as it saves individually-targetted and specific information on not only a network&#8217;s paying customers, but on those whose traffic needs to peer with that network.  DPI takes away the &#8220;anonymity&#8221; of the current packet transfer protocol by IDENTIFYING EACH USER it collects logs on, and by INTERCEPTING TRAFFIC to do so.</p>
<p>The privacy issues are endless.<br />
And, by the very definition of what DPI does, it should be considered a violation of current privacy law.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NO1UNO</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973179</link>
		<dc:creator>NO1UNO</dc:creator>
		<pubDate>Sat, 02 May 2009 15:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973179</guid>
		<description>@ Tom, well said......and although this will show everyone my tech level on networking
what the heck do you mean by PVCs??? Is it like running a VM or what??</description>
		<content:encoded><![CDATA[<p>@ Tom, well said&#8230;&#8230;and although this will show everyone my tech level on networking<br />
what the heck do you mean by PVCs??? Is it like running a VM or what??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Koltai</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973171</link>
		<dc:creator>Tom Koltai</dc:creator>
		<pubDate>Sat, 02 May 2009 11:33:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973171</guid>
		<description>I&#039;m flabergasted.

Sandvine seem to be saying that obfusaction prevents traffic management.
Um - crap.
Traffic management is required for QOS and QOS only.
If some of the traffic wants to masquerade as different port utilisation then iut will either miss out on obtaining better QOS or be included in QOS by accident.

And actually - he is quite incorrect about being able to obtain the result by dpi.
128 bit encryption with fake headers bouncing of a remote proxy through a pvc is impossible to read - and I dont care what your patent claims mr sandvine group. It just cant be done.

But I tell you what - you write a paper that tells the truth - i.e: American protectionist FUD distribiution has forced the global internet community to experiment with new methods enabling discrete private data streams to make sure that when the commercially filetered internet does arrive in 2012, those individuals that havbe mastered the ART of CDMA type TCP-IP layer overlay with disparate ad-hoc on demand chaos based random routing - will still be able to cruise the net quite comfortably without being traced.

And Sandvine - if you dont join the team - you become part of the problem. And if you&#039;re part of the problem, well then no-one is actually going to give you the solution. So I guess, the academics have been right all alone - surprise surprise surprise (gomer pyle accent). We do have a need for Internet 2.
Damn - I really did think that government would come to its senses.

Everyone - load PVC&#039;s - take aim at neutral virtual proxy and fire.

Sesame Street today was brought to you by the letter i as in invisible, the R as in you&#039;re wRong and letter S as in &quot;duck Sucker&quot; (any &quot;A fist full of Dynamite&quot; fans out there ?</description>
		<content:encoded><![CDATA[<p>I&#8217;m flabergasted.</p>
<p>Sandvine seem to be saying that obfusaction prevents traffic management.<br />
Um &#8211; crap.<br />
Traffic management is required for QOS and QOS only.<br />
If some of the traffic wants to masquerade as different port utilisation then iut will either miss out on obtaining better QOS or be included in QOS by accident.</p>
<p>And actually &#8211; he is quite incorrect about being able to obtain the result by dpi.<br />
128 bit encryption with fake headers bouncing of a remote proxy through a pvc is impossible to read &#8211; and I dont care what your patent claims mr sandvine group. It just cant be done.</p>
<p>But I tell you what &#8211; you write a paper that tells the truth &#8211; i.e: American protectionist FUD distribiution has forced the global internet community to experiment with new methods enabling discrete private data streams to make sure that when the commercially filetered internet does arrive in 2012, those individuals that havbe mastered the ART of CDMA type TCP-IP layer overlay with disparate ad-hoc on demand chaos based random routing &#8211; will still be able to cruise the net quite comfortably without being traced.</p>
<p>And Sandvine &#8211; if you dont join the team &#8211; you become part of the problem. And if you&#8217;re part of the problem, well then no-one is actually going to give you the solution. So I guess, the academics have been right all alone &#8211; surprise surprise surprise (gomer pyle accent). We do have a need for Internet 2.<br />
Damn &#8211; I really did think that government would come to its senses.</p>
<p>Everyone &#8211; load PVC&#8217;s &#8211; take aim at neutral virtual proxy and fire.</p>
<p>Sesame Street today was brought to you by the letter i as in invisible, the R as in you&#8217;re wRong and letter S as in &#8220;duck Sucker&#8221; (any &#8220;A fist full of Dynamite&#8221; fans out there ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BennyBeans</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973157</link>
		<dc:creator>BennyBeans</dc:creator>
		<pubDate>Sat, 02 May 2009 03:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973157</guid>
		<description>&quot;What difference should it make if the network itself is private?!&quot;

Ask shepd, who seems to think public vs private is a big deal.

&quot;Content caching is done on the fly, doesnât interfere with the service (actually improves it), doesnât examine the data packets (just caches them), and the content is dumped as soon as itâs no longer required by the USER (no retention when done).&quot;

It&#039;s not dumped when the user&#039;s done with it. That&#039;s the whole point of caching. It&#039;s retained for a certain amount of time, in case the same person (or someone else) requests it soon afterward.

&quot;If they could âseeâ anything, groups like the RIAA would be totally badgering the providers for a âfront row seatâ, to see and record all the copyright infringements âas they go byâ.&quot;

This is nonsense. Every ISP in the world has the capability in their network to single out a user and monitor their traffic. They have to, it&#039;s the law. With a court order, the police can require an ISP to monitor any given user&#039;s Internet traffic, and get all of it. So if the idea is that DPI is giving privacy-impairing capabilities to ISPs that they don&#039;t already have, then it&#039;s wrong. And the RIAA doesn&#039;t need this capability to figure out who is copying files (they just get on the P2P network).

So again, what is the specific privacy loss?</description>
		<content:encoded><![CDATA[<p>&#8220;What difference should it make if the network itself is private?!&#8221;</p>
<p>Ask shepd, who seems to think public vs private is a big deal.</p>
<p>&#8220;Content caching is done on the fly, doesnât interfere with the service (actually improves it), doesnât examine the data packets (just caches them), and the content is dumped as soon as itâs no longer required by the USER (no retention when done).&#8221;</p>
<p>It&#8217;s not dumped when the user&#8217;s done with it. That&#8217;s the whole point of caching. It&#8217;s retained for a certain amount of time, in case the same person (or someone else) requests it soon afterward.</p>
<p>&#8220;If they could âseeâ anything, groups like the RIAA would be totally badgering the providers for a âfront row seatâ, to see and record all the copyright infringements âas they go byâ.&#8221;</p>
<p>This is nonsense. Every ISP in the world has the capability in their network to single out a user and monitor their traffic. They have to, it&#8217;s the law. With a court order, the police can require an ISP to monitor any given user&#8217;s Internet traffic, and get all of it. So if the idea is that DPI is giving privacy-impairing capabilities to ISPs that they don&#8217;t already have, then it&#8217;s wrong. And the RIAA doesn&#8217;t need this capability to figure out who is copying files (they just get on the P2P network).</p>
<p>So again, what is the specific privacy loss?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devil's Advocate</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973144</link>
		<dc:creator>Devil's Advocate</dc:creator>
		<pubDate>Fri, 01 May 2009 22:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973144</guid>
		<description>&quot;None of this changes the fact that the network is privately owned.&quot;

What difference should it make if the network itself is private?!
(Not that most actually aren&#039;t anyway, or wouldn&#039;t exist without public money, but...)
The USER DATA isn&#039;t owned by the provider, who&#039;s getting paid to transfer it.
___________________________________

&quot;The privacy implications seem very stretched to me, though. Isnât content caching a far more invasive feature of ISPs?&quot;

No, it&#039;s not.
Content caching is done on the fly, doesn&#039;t interfere with the service (actually improves it), doesn&#039;t examine the data packets (just caches them), and the content is dumped as soon as it&#039;s no longer required by the USER (no retention when done).  Compare content caching to the RAM chips in your computer.  

DPI digs into the packets, interferes with the flow, and records information on them.
This information is retained for set periods of time, or &quot;permanently&quot; in some cases.
Why do you think there&#039;s so much discussion from police forces and other interests about legalizing DPI??
Some are completely drooling over the amount of information they would have access to that wouldn&#039;t have normally been kept by the providers.

&quot;Of course they see the content.&quot;

No, they don&#039;t.
The content you transfer is dismantled at the transmission user&#039;s end into smaller data packets, and reassembled at the receiving user&#039;s end.

Normal equipment doesn&#039;t exactly &quot;see&quot; anything, nor does it assemble the packets it caches into a &quot;viewable&quot; form at the provider end.  Nor does the provider know what packets belong to a specific transfer or user.  Providers would need to pick out a specific user, sort only those packets into their respective transfer clusters, and reassemble it the way a computer reassembles it at the user end, in order to &quot;see&quot; anything.  Providers wouldn&#039;t have the time, desire, or incentive to rig that kind of thing up.  That&#039;s essentially what makes a provider a &quot;dumb pipe&quot;.  DPI would change that significantly.

If they could &quot;see&quot; anything, groups like the RIAA would be totally badgering the providers for a &quot;front row seat&quot;, to see and record all the copyright infringements &quot;as they go by&quot;.

Providers are supposed to be &quot;dumb pipes&quot;.
They&#039;re not going to be allowed to open data packets to determine their contents, if we, collectively, can help it at all!
Content control by the ISPs, as well as loss of user privacy, would be two of the many negative results if we don&#039;t.</description>
		<content:encoded><![CDATA[<p>&#8220;None of this changes the fact that the network is privately owned.&#8221;</p>
<p>What difference should it make if the network itself is private?!<br />
(Not that most actually aren&#8217;t anyway, or wouldn&#8217;t exist without public money, but&#8230;)<br />
The USER DATA isn&#8217;t owned by the provider, who&#8217;s getting paid to transfer it.<br />
___________________________________</p>
<p>&#8220;The privacy implications seem very stretched to me, though. Isnât content caching a far more invasive feature of ISPs?&#8221;</p>
<p>No, it&#8217;s not.<br />
Content caching is done on the fly, doesn&#8217;t interfere with the service (actually improves it), doesn&#8217;t examine the data packets (just caches them), and the content is dumped as soon as it&#8217;s no longer required by the USER (no retention when done).  Compare content caching to the RAM chips in your computer.  </p>
<p>DPI digs into the packets, interferes with the flow, and records information on them.<br />
This information is retained for set periods of time, or &#8220;permanently&#8221; in some cases.<br />
Why do you think there&#8217;s so much discussion from police forces and other interests about legalizing DPI??<br />
Some are completely drooling over the amount of information they would have access to that wouldn&#8217;t have normally been kept by the providers.</p>
<p>&#8220;Of course they see the content.&#8221;</p>
<p>No, they don&#8217;t.<br />
The content you transfer is dismantled at the transmission user&#8217;s end into smaller data packets, and reassembled at the receiving user&#8217;s end.</p>
<p>Normal equipment doesn&#8217;t exactly &#8220;see&#8221; anything, nor does it assemble the packets it caches into a &#8220;viewable&#8221; form at the provider end.  Nor does the provider know what packets belong to a specific transfer or user.  Providers would need to pick out a specific user, sort only those packets into their respective transfer clusters, and reassemble it the way a computer reassembles it at the user end, in order to &#8220;see&#8221; anything.  Providers wouldn&#8217;t have the time, desire, or incentive to rig that kind of thing up.  That&#8217;s essentially what makes a provider a &#8220;dumb pipe&#8221;.  DPI would change that significantly.</p>
<p>If they could &#8220;see&#8221; anything, groups like the RIAA would be totally badgering the providers for a &#8220;front row seat&#8221;, to see and record all the copyright infringements &#8220;as they go by&#8221;.</p>
<p>Providers are supposed to be &#8220;dumb pipes&#8221;.<br />
They&#8217;re not going to be allowed to open data packets to determine their contents, if we, collectively, can help it at all!<br />
Content control by the ISPs, as well as loss of user privacy, would be two of the many negative results if we don&#8217;t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BennyBeans</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973138</link>
		<dc:creator>BennyBeans</dc:creator>
		<pubDate>Fri, 01 May 2009 21:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973138</guid>
		<description>None of this changes the fact that the network is privately owned. People connect into the privately owned network so they can send requests and get responses from servers somewhere.

The privacy implications seem very stretched to me, though. Isn&#039;t content caching a far more invasive feature of ISPs? Why does nobody care about caching? Is it simply because people don&#039;t like DPI (it makes BitTorrent slow) and do like content caching (it makes the web much faster)?

We&#039;re complaining about programs &#039;seeing&#039; our content. Of course they see the content. Routers have to copy those bits all over the place to get them to the destination; they can&#039;t copy it without &#039;seeing&#039; it. Caching is far worse because it leaves the bits in one place where they can be inspected after the fact. DPI is just a bunch of heuristics that makes decisions based on certain properties of the data. What are the specific privacy concerns there?</description>
		<content:encoded><![CDATA[<p>None of this changes the fact that the network is privately owned. People connect into the privately owned network so they can send requests and get responses from servers somewhere.</p>
<p>The privacy implications seem very stretched to me, though. Isn&#8217;t content caching a far more invasive feature of ISPs? Why does nobody care about caching? Is it simply because people don&#8217;t like DPI (it makes BitTorrent slow) and do like content caching (it makes the web much faster)?</p>
<p>We&#8217;re complaining about programs &#8217;seeing&#8217; our content. Of course they see the content. Routers have to copy those bits all over the place to get them to the destination; they can&#8217;t copy it without &#8217;seeing&#8217; it. Caching is far worse because it leaves the bits in one place where they can be inspected after the fact. DPI is just a bunch of heuristics that makes decisions based on certain properties of the data. What are the specific privacy concerns there?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Devil's Advocate</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973137</link>
		<dc:creator>Devil's Advocate</dc:creator>
		<pubDate>Fri, 01 May 2009 20:14:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973137</guid>
		<description>I don&#039;t think it&#039;s possible to set up DPI at the front of a backbone network in such a way it could be considered &quot;private&quot;.

The trouble with DPI is, it sees EVERYTHING going IN and coming OUT of that provider&#039;s network.
Even networks that wouldn&#039;t be using DPI would still have to peer with those that would be.

Even &quot;opting out&quot;, if such an option was offered by networks that use it, would need to be done with EVERY DPI-USING PROVIDER ON THE PLANET, in order to effectively opt out of the practice.  Even if that choice was honoured by each provider, your traffic would still have to line up with everyone else&#039;s and pass through these DPI units.  (Your service would still be degraded, by default, by a factor times the number of DPI units it needs to pass through.)

This essentially makes DPI totally &quot;public&quot;, and should be absolutely illegal.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it&#8217;s possible to set up DPI at the front of a backbone network in such a way it could be considered &#8220;private&#8221;.</p>
<p>The trouble with DPI is, it sees EVERYTHING going IN and coming OUT of that provider&#8217;s network.<br />
Even networks that wouldn&#8217;t be using DPI would still have to peer with those that would be.</p>
<p>Even &#8220;opting out&#8221;, if such an option was offered by networks that use it, would need to be done with EVERY DPI-USING PROVIDER ON THE PLANET, in order to effectively opt out of the practice.  Even if that choice was honoured by each provider, your traffic would still have to line up with everyone else&#8217;s and pass through these DPI units.  (Your service would still be degraded, by default, by a factor times the number of DPI units it needs to pass through.)</p>
<p>This essentially makes DPI totally &#8220;public&#8221;, and should be absolutely illegal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BennyBeans</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973121</link>
		<dc:creator>BennyBeans</dc:creator>
		<pubDate>Fri, 01 May 2009 17:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973121</guid>
		<description>&quot;If he does not, its use is public use (= without knowing customer, his opinion, and using it thus on all the traffic).&quot;

This is a very strange definition of public. Usually the distinction has to do with ownership. If I allow someone use of my property by contract, and I don&#039;t abide by the terms of the contract, then this is a tortious conduct. I haven&#039;t read that closely any ISP customer agreements, but if ISP&#039;s behaviour contradicts what&#039;s in the agreement then I&#039;m sure it wouldn&#039;t be hard to get a lawyer to take on the class action suit.

&quot;If I funnel my BitTorrent traffic through VPN, or my sole net usage is transferring data loads over VPN, guess what kind of traffic the DPI would mark on an egress port of my router?&quot;

I would call it VPN traffic, no matter what you are doing. DPI is impossible on tunneled IPSec traffic, unless your DPI engine knows something the information security profession doesn&#039;t.

BitTorrent over VPN would be crap, though.

&quot;No, shepd is right here. Why? Becouse you simply canât generalize âIPv4â² is not a data content.&quot;

I&#039;m not sure why the definition matters. The point is that networks cannot support IPv6 tunneling without &#039;inspecting&#039; what comes after IPv4 headers. If you insist on creating a bright-line network rule of &quot;don&#039;t read what comes after a packet&#039;s layer 3 header&quot;, then the ISATAP RFC becomes illegal to implement.</description>
		<content:encoded><![CDATA[<p>&#8220;If he does not, its use is public use (= without knowing customer, his opinion, and using it thus on all the traffic).&#8221;</p>
<p>This is a very strange definition of public. Usually the distinction has to do with ownership. If I allow someone use of my property by contract, and I don&#8217;t abide by the terms of the contract, then this is a tortious conduct. I haven&#8217;t read that closely any ISP customer agreements, but if ISP&#8217;s behaviour contradicts what&#8217;s in the agreement then I&#8217;m sure it wouldn&#8217;t be hard to get a lawyer to take on the class action suit.</p>
<p>&#8220;If I funnel my BitTorrent traffic through VPN, or my sole net usage is transferring data loads over VPN, guess what kind of traffic the DPI would mark on an egress port of my router?&#8221;</p>
<p>I would call it VPN traffic, no matter what you are doing. DPI is impossible on tunneled IPSec traffic, unless your DPI engine knows something the information security profession doesn&#8217;t.</p>
<p>BitTorrent over VPN would be crap, though.</p>
<p>&#8220;No, shepd is right here. Why? Becouse you simply canât generalize âIPv4â² is not a data content.&#8221;</p>
<p>I&#8217;m not sure why the definition matters. The point is that networks cannot support IPv6 tunneling without &#8216;inspecting&#8217; what comes after IPv4 headers. If you insist on creating a bright-line network rule of &#8220;don&#8217;t read what comes after a packet&#8217;s layer 3 header&#8221;, then the ISATAP RFC becomes illegal to implement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973118</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Fri, 01 May 2009 16:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973118</guid>
		<description>@BennyBeans

&gt; Bell and Rogers using DPI is private usage. It happens on their own privately-owned networks, which customers have paid
&gt; for the right to put their traffic on.

1. Customer is the one who designates the use of type, content, priority and timing of his communication over the internet. Noone has the right to stomp upon his right of free decision. So NO, DPI usage is not matter of ISP deciding whether to use it or not. Customer must give him right to do so first. If he does not, its use is public use (= without knowing customer, his opinion, and using it thus on all the traffic).

2. Show me, where customer gives its ISP the right to manipulate his/her own originated/destined traffic, in the agreement between customer and ISP.

3. Customer is the one who comes to ISP with demand. Network wouldnt be there without people interrested to use it; they drive it. Without customer demand, the ISP can pack up and go away, it is useless, at least as a business. So: Customer is the one who primarily decides, NOT ISP.

&gt;&gt; âIn my opinion, nothing is a bigger hog than work VPNs.â
&gt;
&gt; Thatâs a pretty ill-informed opinion. If Iâm active on BitTorrent, Iâm using about 10-20 times the bandwidth as when Iâm
&gt; active on my work VPN connection.

VPNs *may* be fair much more hogs; it depends on technology usage. If I funnel my BitTorrent traffic through VPN, or my sole net usage is transferring data loads over VPN, guess what kind of traffic the DPI would mark on an egress port of my router?

So, neither you nor shepd are right on this point. However, if customer decides to prioritize certain traffic, ISP has no right to thwart such his decision by giving it. ISP must stay network usage-agnostic (a.k.a. &quot;best effort&quot; model), at least in their own network, unless they both have agreed upon something else. See point 1 in my reply above.

&gt;&gt; âAnd I thought you just said in point 6 you donât inspect the content? How do you even know itâs an IPv4 packet then?â
&gt;
&gt; This is just being obtuse. The IP header isnât the content. If you disallow inspection of IP headers, then the Internet might 
&gt; not work so well. Iâm not sure if you really donât know how ISATAP works or if youâre just pretending for the sake of being 
&gt; argumentative.

No, shepd is right here. Why? Becouse you simply can&#039;t generalize &#039;IPv4&#039; is not a data content. It again may be, depending on use. Guess what will happen if I&#039;ll create an IPSec connection in tunneling mode? The original IPv4 header is part of data payload. What will happen if my application packs an IPv4 header as a means of app-driven routing information? Again, this is content. So: anything *data* is content, part of it is just being marked &#039;header&#039; for purpose of specific program handling (routing decision, manipulation/marking, logging, etc.). In this sense, it is no different than anything that follows header.
And no, do not object this is just wording. This is definition. If you have more exact one, go ahead and beat it.</description>
		<content:encoded><![CDATA[<p>@BennyBeans</p>
<p>&gt; Bell and Rogers using DPI is private usage. It happens on their own privately-owned networks, which customers have paid<br />
&gt; for the right to put their traffic on.</p>
<p>1. Customer is the one who designates the use of type, content, priority and timing of his communication over the internet. Noone has the right to stomp upon his right of free decision. So NO, DPI usage is not matter of ISP deciding whether to use it or not. Customer must give him right to do so first. If he does not, its use is public use (= without knowing customer, his opinion, and using it thus on all the traffic).</p>
<p>2. Show me, where customer gives its ISP the right to manipulate his/her own originated/destined traffic, in the agreement between customer and ISP.</p>
<p>3. Customer is the one who comes to ISP with demand. Network wouldnt be there without people interrested to use it; they drive it. Without customer demand, the ISP can pack up and go away, it is useless, at least as a business. So: Customer is the one who primarily decides, NOT ISP.</p>
<p>&gt;&gt; âIn my opinion, nothing is a bigger hog than work VPNs.â<br />
&gt;<br />
&gt; Thatâs a pretty ill-informed opinion. If Iâm active on BitTorrent, Iâm using about 10-20 times the bandwidth as when Iâm<br />
&gt; active on my work VPN connection.</p>
<p>VPNs *may* be fair much more hogs; it depends on technology usage. If I funnel my BitTorrent traffic through VPN, or my sole net usage is transferring data loads over VPN, guess what kind of traffic the DPI would mark on an egress port of my router?</p>
<p>So, neither you nor shepd are right on this point. However, if customer decides to prioritize certain traffic, ISP has no right to thwart such his decision by giving it. ISP must stay network usage-agnostic (a.k.a. &#8220;best effort&#8221; model), at least in their own network, unless they both have agreed upon something else. See point 1 in my reply above.</p>
<p>&gt;&gt; âAnd I thought you just said in point 6 you donât inspect the content? How do you even know itâs an IPv4 packet then?â<br />
&gt;<br />
&gt; This is just being obtuse. The IP header isnât the content. If you disallow inspection of IP headers, then the Internet might<br />
&gt; not work so well. Iâm not sure if you really donât know how ISATAP works or if youâre just pretending for the sake of being<br />
&gt; argumentative.</p>
<p>No, shepd is right here. Why? Becouse you simply can&#8217;t generalize &#8216;IPv4&#8242; is not a data content. It again may be, depending on use. Guess what will happen if I&#8217;ll create an IPSec connection in tunneling mode? The original IPv4 header is part of data payload. What will happen if my application packs an IPv4 header as a means of app-driven routing information? Again, this is content. So: anything *data* is content, part of it is just being marked &#8216;header&#8217; for purpose of specific program handling (routing decision, manipulation/marking, logging, etc.). In this sense, it is no different than anything that follows header.<br />
And no, do not object this is just wording. This is definition. If you have more exact one, go ahead and beat it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BennyBeans</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973113</link>
		<dc:creator>BennyBeans</dc:creator>
		<pubDate>Fri, 01 May 2009 15:02:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973113</guid>
		<description>&quot;Yes, thatâs why we want DPI banned for PUBLIC usage, not PRIVATE. Duh.&quot;

Bell and Rogers using DPI is private usage. It happens on their own privately-owned networks, which customers have paid for the right to put their traffic on.

&quot;In my opinion, nothing is a bigger hog than work VPNs.&quot;

That&#039;s a pretty ill-informed opinion. If I&#039;m active on BitTorrent, I&#039;m using about 10-20 times the bandwidth as when I&#039;m active on my work VPN connection.

&quot;And I thought you just said in point 6 you donât inspect the content? How do you even know itâs an IPv4 packet then?&quot;

This is just being obtuse. The IP header isn&#039;t the content. If you disallow inspection of IP headers, then the Internet might not work so well. I&#039;m not sure if you really don&#039;t know how ISATAP works or if you&#039;re just pretending for the sake of being argumentative.</description>
		<content:encoded><![CDATA[<p>&#8220;Yes, thatâs why we want DPI banned for PUBLIC usage, not PRIVATE. Duh.&#8221;</p>
<p>Bell and Rogers using DPI is private usage. It happens on their own privately-owned networks, which customers have paid for the right to put their traffic on.</p>
<p>&#8220;In my opinion, nothing is a bigger hog than work VPNs.&#8221;</p>
<p>That&#8217;s a pretty ill-informed opinion. If I&#8217;m active on BitTorrent, I&#8217;m using about 10-20 times the bandwidth as when I&#8217;m active on my work VPN connection.</p>
<p>&#8220;And I thought you just said in point 6 you donât inspect the content? How do you even know itâs an IPv4 packet then?&#8221;</p>
<p>This is just being obtuse. The IP header isn&#8217;t the content. If you disallow inspection of IP headers, then the Internet might not work so well. I&#8217;m not sure if you really don&#8217;t know how ISATAP works or if you&#8217;re just pretending for the sake of being argumentative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/21162/comment-page-1#comment-973110</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Fri, 01 May 2009 14:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/?p=21162#comment-973110</guid>
		<description>The CRTC should toss that out.

All Sandvine submitted was a commercial. 

An attempt to get attention using the tax payers regulatory website to submit a commercial that lacks in substance.

Maybe P2Pnet.net should use the CRTC as a commercial avenue as well. After all P2PNet is Canadian also.</description>
		<content:encoded><![CDATA[<p>The CRTC should toss that out.</p>
<p>All Sandvine submitted was a commercial. </p>
<p>An attempt to get attention using the tax payers regulatory website to submit a commercial that lacks in substance.</p>
<p>Maybe P2Pnet.net should use the CRTC as a commercial avenue as well. After all P2PNet is Canadian also.</p>
]]></content:encoded>
	</item>
</channel>
</rss>


