<?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: Is IPv6 inevitable?</title>
	<atom:link href="http://blog.thedruid.co.uk/2005/11/11/is-ipv6-inevitable/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thedruid.co.uk/2005/11/11/is-ipv6-inevitable/</link>
	<description>The world as I see it. Links to the best on the web. Free software. Linux. Atticware. And more.</description>
	<lastBuildDate>Sat, 28 Jan 2012 00:36:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: akaDruid</title>
		<link>http://blog.thedruid.co.uk/2005/11/11/is-ipv6-inevitable/comment-page-1/#comment-68</link>
		<dc:creator>akaDruid</dc:creator>
		<pubDate>Fri, 11 Nov 2005 14:47:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thedruid.co.uk/2005/11/11/is-ipv6-inevitable/#comment-68</guid>
		<description>Thanks for your comment.  I don&#039;t have a Linksys WRT54G (or Earthlink) so I can&#039;t evaluate this firmware, but it&#039;s nice to know that at least one ISP is seriously working towards IPv6.</description>
		<content:encoded><![CDATA[Mozilla Firefox 1.0.7   Windows 2000<p>
Thanks for your comment.  I don&#8217;t have a Linksys WRT54G (or Earthlink) so I can&#8217;t evaluate this firmware, but it&#8217;s nice to know that at least one ISP is seriously working towards IPv6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://blog.thedruid.co.uk/2005/11/11/is-ipv6-inevitable/comment-page-1/#comment-67</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Fri, 11 Nov 2005 14:37:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thedruid.co.uk/2005/11/11/is-ipv6-inevitable/#comment-67</guid>
		<description>Here&#039;s a firmware mod that actually does something witih IPv6.  Users get a /64 routed to their home in a manner similar to how DHCP allocates and routes a single /32 now.  Hosts in the home acquire one of these /64 addresses via stateless autoconfiguration.

Very slowly, we see users finding ways to use IPv6, and in this case, obsoleting NAT.  Many of tus believe NAT is keeping food off the table, as it represents a tax on application developers and service providers alike, many of whom are simply not willing to pay.  

Skeptics point to a lack of IPv6-aware (whatever that means) as a reason IPv6 is wedged.  This is nonsense:  we have an app that will leverage IPv6:  VoIP.  Talk to the larger VoIP service providers and you&#039;ll learn that because of the problems NAT causes with bearing UDP based voice, these providers find it *easier* to handle all the voice media for all calls rather than let the voice media go p2p, as SIP cleanly allows once the call setup signalling is complete.  That&#039;s a real shame, because it doesn&#039;t have to be this way.  So SIP-based voice  is your killer IPv6 app.

Disclaimer:  I work at EathLink, but the firmware below is free, and we&#039;ll show you how to configure your network so you can reproduce what we did.  The work is not a solution to all our problems, but it helps keep the conversation going.

http://www.research.earthlink.net/ipv6/</description>
		<content:encoded><![CDATA[Mozilla Firefox 1.0.6   Linux<p>
Here&#8217;s a firmware mod that actually does something witih IPv6.  Users get a /64 routed to their home in a manner similar to how DHCP allocates and routes a single /32 now.  Hosts in the home acquire one of these /64 addresses via stateless autoconfiguration.</p>
<p>Very slowly, we see users finding ways to use IPv6, and in this case, obsoleting NAT.  Many of tus believe NAT is keeping food off the table, as it represents a tax on application developers and service providers alike, many of whom are simply not willing to pay.  </p>
<p>Skeptics point to a lack of IPv6-aware (whatever that means) as a reason IPv6 is wedged.  This is nonsense:  we have an app that will leverage IPv6:  VoIP.  Talk to the larger VoIP service providers and you&#8217;ll learn that because of the problems NAT causes with bearing UDP based voice, these providers find it *easier* to handle all the voice media for all calls rather than let the voice media go p2p, as SIP cleanly allows once the call setup signalling is complete.  That&#8217;s a real shame, because it doesn&#8217;t have to be this way.  So SIP-based voice  is your killer IPv6 app.</p>
<p>Disclaimer:  I work at EathLink, but the firmware below is free, and we&#8217;ll show you how to configure your network so you can reproduce what we did.  The work is not a solution to all our problems, but it helps keep the conversation going.</p>
<p><a href="http://www.research.earthlink.net/ipv6/" rel="nofollow">http://www.research.earthlink.net/ipv6/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

