<?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>Peer To Peer Architecture</title>
 <link>http://www.fiercevoip.com/tags/peer-peer-architecture</link>
 <description></description>
 <language>en</language>
<item>
 <title>BitTorrent battles accusations of VoIP, network clobbering</title>
 <link>http://www.fiercevoip.com/story/bittorrent-battles-accusations-voip-network-clobbering/2008-12-02?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FV0</link>
 <description>&lt;p&gt;A full-blown blog-o-war has started between &lt;em&gt;The Register&lt;/em&gt; and BitTorrent.&amp;nbsp; A Register columnist said BitTorrent&#039;s uTorrent client is going to bring the internet to a crawl because of its preference for using UDP.&lt;/p&gt;
&lt;p&gt;The use of UDP as UTorrent&#039;s default peer-to-peer protocol&amp;nbsp;allegedly could make the amount of ungovernable traffic go through the roof, clobbering bandwidth, slowing gamers and VoIP. ISPs could control traffic flow by slowing down UDP traffic, but such a move would &quot;utterly destroy VoIP,&quot; alleges The Register.&lt;/p&gt;
&lt;p&gt;Techno sites have taken the cannon fodder and fired it with differing results. Excess UDP traffic could slow last-mile connections, say some, rather than bringing the whole Internet to its knees.&lt;/p&gt;
&lt;p&gt;BitTorrent says &lt;em&gt;The Register&lt;/em&gt; piece is &quot;utter nonsense&quot; and a switch to a UDP-based implementation of its client was intended to reduce internet congestion, not kill the Internet proper.&lt;/p&gt;
&lt;p&gt;We suspect some of this brouhaha has to do with the fine British journalistic tradition (&lt;em&gt;The Register&lt;/em&gt; is published in the UK) of running wild headlines and wilder stories to generate controversy and more readership.&amp;nbsp;Gotta get those web hits up for the end of the year bonuses, wot?&lt;/p&gt;
&lt;p&gt;For more:&lt;br /&gt;- &lt;em&gt;The Industry Standard&lt;/em&gt; raps on UDP vs TCP. &lt;a href=&quot;http://www.thestandard.com/news/2008/12/01/bittorrent-register-report-protocol-change-utter-nonsense&quot;&gt;Article&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Related articles&lt;/strong&gt;&lt;br /&gt;&lt;a href=&quot;http://www.fiercetelecom.com/story/comcast-bittorrent-cooperate-on-p2p-fix/2008-03-27&quot;&gt;Comcast, BitTorrent cooperate on P2P fix - FierceTelecom&lt;/a&gt;&lt;br /&gt;&lt;a href=&quot;http://www.fiercetelecom.com/story/study-cox-among-bittorrent-traffic-throttlers/2008-05-19&quot;&gt;Study: Cox among BitTorrent traffic throttlers - FierceTelecom&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.fiercevoip.com/story/bittorrent-battles-accusations-voip-network-clobbering/2008-12-02#comments</comments>
 <category domain="http://www.fiercevoip.com/tags/bittorrent">Bittorrent</category>
 <category domain="http://www.fiercevoip.com/tags/internet-congestion">Internet Congestion</category>
 <category domain="http://www.fiercevoip.com/tags/p2p">P2P</category>
 <category domain="http://www.fiercevoip.com/tags/peer-peer-architecture">Peer To Peer Architecture</category>
 <category domain="http://www.fiercevoip.com/tags/traffic-flow">Traffic Flow</category>
 <category domain="http://www.fiercevoip.com/tags/udp">udp</category>
 <category domain="http://www.fiercevoip.com/tags/utorrent">Utorrent</category>
 <category domain="http://www.fiercevoip.com/tags/voip-0">VoIP</category>
 <category domain="http://www.fiercevoip.com/tags/voip-technology">VoIP Technology</category>
 <category domain="http://www.fiercevoip.com/tags/voip-technology-news">voip technology news</category>
 <pubDate>Tue, 02 Dec 2008 14:02:46 -0500</pubDate>
 <dc:creator>Doug Mohney</dc:creator>
 <guid isPermaLink="false">3011 at http://www.fiercevoip.com</guid>
</item>
<item>
 <title>Skype Wiretap Nuances </title>
 <link>http://www.fiercevoip.com/story/skype-wiretap-nuances/2008-06-10?utm_medium=rss&amp;utm_source=rss&amp;cmp-id=OTC-RSS-FV0</link>
 <description>&lt;p&gt;Skype says it is unable to comply with court-authorized
wiretap requests, says News.com. A closer examination of the question and
Skype&#039;s reply bears examination and thought.&lt;/p&gt;
&lt;p&gt;News.com conducted a survey asking a number of big name vendors about
the privacy of instant messaging and other services they offer. One of the questions was: &quot;Have you ever
received a subpoena, court order or other law enforcement request asking you to
perform a live interception or wiretap, meaning the contents of your users&#039;
communications would be instantly forwarded to law enforcement?&quot;&lt;/p&gt;
&lt;p&gt;Skype&#039;s reply with underline emphasis provided by this reporter: &lt;em&gt;&quot;We have not received any subpoenas or
court orders asking us to perform a live interception or wiretap of &lt;u&gt;Skype-to-Skype
communications&lt;/u&gt;. In any event, because of Skype&#039;s peer-to-peer architecture
and encryption techniques, Skype would not be able to comply with such a
request.&quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Skype doesn&#039;t say it hasn&#039;t received any requests to perform live interception
of phone calls, just that nobody&#039;s asked them for Skype-to-Skype communication.
This would imply that SkypeIn and SkypeOut, the services that touch the PSTN,
might be fair game. The company has said
in the past that it cooperates with all lawful requests from &quot;relevant
authorities,&quot; so a reasonable person might assume that if you&#039;re making
calls through Skype that touch the PSTN, those calls could be subject to lawful
intercept.&lt;/p&gt;
&lt;p&gt;However, there&#039;s a rolling assumption that peer-to-peer calls that stick to
Skype&#039;s peer-to-peer network and are encrypted with 256-bit AES are potentially
untouchable, while centralized voice/VoIP services operated by Yahoo, AOL,
Microsoft and others could be readily tapped.&lt;/p&gt;
&lt;p&gt;Fanning the flames of speculation is Skype&#039;s closed software architecture
and a large body of work by independent researchers that have going through
detail reverse engineering of the program and how it works. Since Skype is a
&quot;black box,&quot; there is no way to know if there&#039;s a backdoor of sorts
to tap into a client and copy the voice stream to somewhere else or any way to
know if such a process was occurring.&lt;/p&gt;
&lt;p&gt;For more:&lt;br /&gt;- News.com&#039;s speculation that &lt;a href=&quot;http://news.cnet.com/8301-13578_3-9963028-38.html?tag=ndfd.fblgs&quot;&gt;Skype
is secure&lt;/a&gt;&lt;br /&gt;- For security geeks, a very cool compilation of &lt;a href=&quot;http://www1.cs.columbia.edu/%7Esalman/skype/&quot;&gt;Skype independent security analysis&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Related articles:&lt;/strong&gt;&lt;br /&gt; &lt;a href=&quot;http://www.fiercevoip.com/story/skype-resists-inter-operability/2008-01-17&quot;&gt;Skype
resists inter-operability&lt;/a&gt;&lt;br /&gt; Skype: &lt;a href=&quot;http://www.fiercevoip.com/story/skype-stand-by-for-violence/2008-02-19&quot;&gt;Stand-by
for violence&lt;/a&gt; with open telephony.&lt;br /&gt; Do as we say, not as we do; Skype wants &lt;a href=&quot;http://www.fiercevoip.com/story/fcc-chairman-says-no-to-skype-forced-open-access/2008-04-03&quot;&gt;open
access to wireless devices&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.fiercevoip.com/story/skype-wiretap-nuances/2008-06-10#comments</comments>
 <category domain="http://www.fiercevoip.com/tags/lawful-intercept">Lawful Intercept</category>
 <category domain="http://www.fiercevoip.com/tags/peer-peer-architecture">Peer To Peer Architecture</category>
 <category domain="http://www.fiercevoip.com/tags/reverse-engineering">Reverse Engineering</category>
 <category domain="http://www.fiercevoip.com/tags/skype">Skype</category>
 <category domain="http://www.fiercevoip.com/tags/voip-security">VoIP Security</category>
 <category domain="http://www.fiercevoip.com/tags/wiretap">Wiretap</category>
 <pubDate>Tue, 10 Jun 2008 20:49:24 -0400</pubDate>
 <dc:creator>Doug Mohney</dc:creator>
 <guid isPermaLink="false">2523 at http://www.fiercevoip.com</guid>
</item>
</channel>
</rss>
