<?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: SIP and Skype, P2P and Supernodes &#8211; what a melee</title>
	<atom:link href="http://blog.roychowdhury.org/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.roychowdhury.org/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/</link>
	<description></description>
	<lastBuildDate>Tue, 20 Dec 2011 10:18:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Arjun</title>
		<link>http://blog.roychowdhury.org/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/comment-page-1/#comment-52</link>
		<dc:creator>Arjun</dc:creator>
		<pubDate>Wed, 04 Oct 2006 17:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/#comment-52</guid>
		<description>thanks for the confirmation, Buda. The text does not really say that no node behind a NAT can be a supernode. It says no node which is unable to receive inbound connections (with NAT as one possible example) will not be an SN. This is what I thought - because being behind a NAT does not necessarily mean it cannot accept inbound connections - it depends on how the NAT device is configured, and its type.</description>
		<content:encoded><![CDATA[<p>thanks for the confirmation, Buda. The text does not really say that no node behind a NAT can be a supernode. It says no node which is unable to receive inbound connections (with NAT as one possible example) will not be an SN. This is what I thought &#8211; because being behind a NAT does not necessarily mean it cannot accept inbound connections &#8211; it depends on how the NAT device is configured, and its type.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buda</title>
		<link>http://blog.roychowdhury.org/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/comment-page-1/#comment-53</link>
		<dc:creator>Buda</dc:creator>
		<pubDate>Wed, 04 Oct 2006 15:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/#comment-53</guid>
		<description>You got that right, the keywords are &quot;unable to receive inbound network connection&quot;. SInce there are lots of NAT traveresal techniques and lots of NAT enabled network devices I think we can presume that NAT won&#039;t be a problem now or in the near future. Also I find the use of SuperNodes for VoIP a feasible idea, because of the constant growth of a CPU/Hardware power, while the VoIP requirements are already set and is not likely to grow much.</description>
		<content:encoded><![CDATA[<p>You got that right, the keywords are &#8220;unable to receive inbound network connection&#8221;. SInce there are lots of NAT traveresal techniques and lots of NAT enabled network devices I think we can presume that NAT won&#8217;t be a problem now or in the near future. Also I find the use of SuperNodes for VoIP a feasible idea, because of the constant growth of a CPU/Hardware power, while the VoIP requirements are already set and is not likely to grow much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Buda</title>
		<link>http://blog.roychowdhury.org/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/comment-page-1/#comment-51</link>
		<dc:creator>Buda</dc:creator>
		<pubDate>Wed, 04 Oct 2006 13:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/#comment-51</guid>
		<description>Quote from &quot;Skype Guide for Network Administrators - edition 1.0.1&quot;&lt;br/&gt;http://www.skype.com/security/guide-for-network-admins.pdf#search=%22supernode%20voip%22&lt;br/&gt;&quot;When a Skype client becomes a supernode, it accepts network connections from a&lt;br/&gt;small number of other Skype users for the purpose of maintaining the accuracy of&lt;br/&gt;the Global Index. Although the supernode activity is entirely transparent to the user,&lt;br/&gt;a Skype client that is unable to receive inbound network connections (such as a user&lt;br/&gt;behind a NAT or firewall) will never become eligible to become a supernode nor will it&lt;br/&gt;ever be asked to relay a third party’s traffic.&quot;</description>
		<content:encoded><![CDATA[<p>Quote from &#8220;Skype Guide for Network Administrators &#8211; edition 1.0.1&#8243;<br /><a href="http://www.skype.com/security/guide-for-network-admins.pdf#search=%22supernode%20voip%22" rel="nofollow">http://www.skype.com/security/guide-for-network-admins.pdf#search=%22supernode%20voip%22</a><br />&#8220;When a Skype client becomes a supernode, it accepts network connections from a<br />small number of other Skype users for the purpose of maintaining the accuracy of<br />the Global Index. Although the supernode activity is entirely transparent to the user,<br />a Skype client that is unable to receive inbound network connections (such as a user<br />behind a NAT or firewall) will never become eligible to become a supernode nor will it<br />ever be asked to relay a third party’s traffic.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjun</title>
		<link>http://blog.roychowdhury.org/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/comment-page-1/#comment-50</link>
		<dc:creator>Arjun</dc:creator>
		<pubDate>Tue, 03 Oct 2006 16:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/#comment-50</guid>
		<description>Julian, thanks for the commentary. I am guessing that your comment on a node behind a NAT never being a sn is specific to skype ? That is interesting. Could you confirm this ?&lt;br/&gt;&lt;br/&gt;Finally, unfortunately, the problem of voicemail may not be as simple as storing in locally. Consider the case where A calls B and B is offline. Now A goes for a vacation, and B comes online the next day. Then, in this case, B will have to wait for the voicemail till A gets back on.</description>
		<content:encoded><![CDATA[<p>Julian, thanks for the commentary. I am guessing that your comment on a node behind a NAT never being a sn is specific to skype ? That is interesting. Could you confirm this ?</p>
<p>Finally, unfortunately, the problem of voicemail may not be as simple as storing in locally. Consider the case where A calls B and B is offline. Now A goes for a vacation, and B comes online the next day. Then, in this case, B will have to wait for the voicemail till A gets back on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian</title>
		<link>http://blog.roychowdhury.org/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/comment-page-1/#comment-49</link>
		<dc:creator>Julian</dc:creator>
		<pubDate>Tue, 03 Oct 2006 07:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://iconverged.wordpress.com/2006/10/02/sip-and-skype-p2p-and-supernodes-what-a-melee/#comment-49</guid>
		<description>Great post. There&#039;s a surprising amount of FUD around Skype and Supernodes that needs dispelling. Not least is that a PC behind a firewall or NAT *WILL NEVER* be a supernode which gives the lie to &quot;Skype will use your bandwidth&quot;&lt;br/&gt;&lt;br/&gt;There&#039;s a bit more analysis to do here about approaches to NAT-firewall busting in P2P networks and VoIP. It&#039;s not clear to me that media needs to be relayed. Although an intermediary Supernode is required during connection setup between two devices behind NAT.&lt;br/&gt;&lt;br/&gt;There&#039;s a simple solution to voicemail and text&#039;s to nodes off line. That&#039;s to store it locally and deliver it when the other party comes on line. You don&#039;t need central storage, you just need delayed delivery.</description>
		<content:encoded><![CDATA[<p>Great post. There&#8217;s a surprising amount of FUD around Skype and Supernodes that needs dispelling. Not least is that a PC behind a firewall or NAT *WILL NEVER* be a supernode which gives the lie to &#8220;Skype will use your bandwidth&#8221;</p>
<p>There&#8217;s a bit more analysis to do here about approaches to NAT-firewall busting in P2P networks and VoIP. It&#8217;s not clear to me that media needs to be relayed. Although an intermediary Supernode is required during connection setup between two devices behind NAT.</p>
<p>There&#8217;s a simple solution to voicemail and text&#8217;s to nodes off line. That&#8217;s to store it locally and deliver it when the other party comes on line. You don&#8217;t need central storage, you just need delayed delivery.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

