<?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"
	>
<channel>
	<title>Comments on: Getting Closer To IPv6?</title>
	<atom:link href="http://phoneboy.com/2101/getting-closer-to-ipv6/feed" rel="self" type="application/rss+xml" />
	<link>http://phoneboy.com/2101/getting-closer-to-ipv6</link>
	<description>VoIP, Mobile Phones, Telecom, and Technology Made Simple</description>
	<pubDate>Thu, 04 Dec 2008 04:56:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: My Ip Address</title>
		<link>http://phoneboy.com/2101/getting-closer-to-ipv6#comment-25715</link>
		<dc:creator>My Ip Address</dc:creator>
		<pubDate>Tue, 19 Feb 2008 09:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/2101/getting-closer-to-ipv6#comment-25715</guid>
		<description>In the IPv4 world, RIPv2 [RFC2453], the integrated IS-IS [RFC1195], and OSPFv2 [RFC2328] are commonly deployed unicast routing protocols in networks of small to middle scale such as enterprise environments, while BGP-4 [RFC4271] is the common routing protocol deployed among large organizations such as Internet Service Providers (ISPs). 
In general, since the routing concept is identical between IPv4 and IPv6, these routing protocols have been naturally extended to support IPv6. Even though the packet formats may have changed, the principles remain largely the same.
But there are IPv6 specific issues. In particular, most IPv6 routing protocols rely heavily on link-local addresses since communication using these addresses is stable in terms of routing, thanks to their limited scope. 
On the other hand, the ambiguity of link-local addresses requires special care in implementing these protocols. It is therefore important to understand the details of the protocols and how they should be implemented even for those who are familiar with IPv4 routing protocols.</description>
		<content:encoded><![CDATA[<p>In the IPv4 world, RIPv2 [RFC2453], the integrated IS-IS [RFC1195], and OSPFv2 [RFC2328] are commonly deployed unicast routing protocols in networks of small to middle scale such as enterprise environments, while BGP-4 [RFC4271] is the common routing protocol deployed among large organizations such as Internet Service Providers (ISPs).<br />
In general, since the routing concept is identical between IPv4 and IPv6, these routing protocols have been naturally extended to support IPv6. Even though the packet formats may have changed, the principles remain largely the same.<br />
But there are IPv6 specific issues. In particular, most IPv6 routing protocols rely heavily on link-local addresses since communication using these addresses is stable in terms of routing, thanks to their limited scope.<br />
On the other hand, the ambiguity of link-local addresses requires special care in implementing these protocols. It is therefore important to understand the details of the protocols and how they should be implemented even for those who are familiar with IPv4 routing protocols.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PhoneBoy</title>
		<link>http://phoneboy.com/2101/getting-closer-to-ipv6#comment-25668</link>
		<dc:creator>PhoneBoy</dc:creator>
		<pubDate>Mon, 11 Feb 2008 04:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/2101/getting-closer-to-ipv6#comment-25668</guid>
		<description>@derek of course it doesn't preclude it, but it makes it a little bit easier to jump on the bandwagon now. :)</description>
		<content:encoded><![CDATA[<p>@derek of course it doesn&#8217;t preclude it, but it makes it a little bit easier to jump on the bandwagon now. <img src='http://phoneboy.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Morr</title>
		<link>http://phoneboy.com/2101/getting-closer-to-ipv6#comment-25667</link>
		<dc:creator>Derek Morr</dc:creator>
		<pubDate>Mon, 11 Feb 2008 01:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/2101/getting-closer-to-ipv6#comment-25667</guid>
		<description>Yes, having IPv6 in the DNS root is a very important step forward for IPv6 deployment. I just wanted to point out that it doesn't preclude organizations from deploying IPv6 themselves, and running IPv6 on their own authoritative name servers.</description>
		<content:encoded><![CDATA[<p>Yes, having IPv6 in the DNS root is a very important step forward for IPv6 deployment. I just wanted to point out that it doesn&#8217;t preclude organizations from deploying IPv6 themselves, and running IPv6 on their own authoritative name servers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PhoneBoy</title>
		<link>http://phoneboy.com/2101/getting-closer-to-ipv6#comment-25664</link>
		<dc:creator>PhoneBoy</dc:creator>
		<pubDate>Sun, 10 Feb 2008 23:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/2101/getting-closer-to-ipv6#comment-25664</guid>
		<description>@derek wouldn't deployment of a major Internet service like DNS indicate progress on IPv6 adoption?</description>
		<content:encoded><![CDATA[<p>@derek wouldn&#8217;t deployment of a major Internet service like DNS indicate progress on IPv6 adoption?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Morr</title>
		<link>http://phoneboy.com/2101/getting-closer-to-ipv6#comment-25662</link>
		<dc:creator>Derek Morr</dc:creator>
		<pubDate>Sun, 10 Feb 2008 17:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/2101/getting-closer-to-ipv6#comment-25662</guid>
		<description>There are far, far more than 11 DNS root servers. There are closer to 130. ICANN has a nice write up it - http://blog.icann.org/?p=235

I agree that having IPv6 in the DNS root is very important. However, organizations have been deploying IPv6 for years before this announcement.</description>
		<content:encoded><![CDATA[<p>There are far, far more than 11 DNS root servers. There are closer to 130. ICANN has a nice write up it - <a href="http://blog.icann.org/?p=235" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/blog.icann.org');">http://blog.icann.org/?p=235</a></p>
<p>I agree that having IPv6 in the DNS root is very important. However, organizations have been deploying IPv6 for years before this announcement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PhoneBoy</title>
		<link>http://phoneboy.com/2101/getting-closer-to-ipv6#comment-25651</link>
		<dc:creator>PhoneBoy</dc:creator>
		<pubDate>Fri, 08 Feb 2008 19:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/2101/getting-closer-to-ipv6#comment-25651</guid>
		<description>@spg NAT makes stuff worse, but then again, protocol designers are stupid for not taking the reality of NAT into account. 

Then again, with IPSec as part of the standard, "filtering" content might be a lot harder.</description>
		<content:encoded><![CDATA[<p>@spg NAT makes stuff worse, but then again, protocol designers are stupid for not taking the reality of NAT into account. </p>
<p>Then again, with IPSec as part of the standard, &#8220;filtering&#8221; content might be a lot harder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spg</title>
		<link>http://phoneboy.com/2101/getting-closer-to-ipv6#comment-25648</link>
		<dc:creator>spg</dc:creator>
		<pubDate>Fri, 08 Feb 2008 18:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.phoneboy.com/2101/getting-closer-to-ipv6#comment-25648</guid>
		<description>IPv6 will eliminate a lot of headaches with protocols like SIP getting around NAT firewalls, etc. but lets hope that as the ISPs, cell carriers(who will likely be one of the  main pipes into the net in 10 years) and the backbone operators do not put no obstacles in place as they upgrade. without net neutrality IPv6 could actually be more of a problem and a help in that the backbone operators and ISP will be able to identify far more about what is connected to you IP connection and throttle as they see fit.</description>
		<content:encoded><![CDATA[<p>IPv6 will eliminate a lot of headaches with protocols like SIP getting around NAT firewalls, etc. but lets hope that as the ISPs, cell carriers(who will likely be one of the  main pipes into the net in 10 years) and the backbone operators do not put no obstacles in place as they upgrade. without net neutrality IPv6 could actually be more of a problem and a help in that the backbone operators and ISP will be able to identify far more about what is connected to you IP connection and throttle as they see fit.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
