<?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: IPv6 in 2009?  Are you kidding me?</title>
	<atom:link href="http://www.barkingseal.com/2009/01/ipv6-in-2009-are-you-kidding-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.barkingseal.com/2009/01/ipv6-in-2009-are-you-kidding-me/</link>
	<description>Applied Trust off-leash: IT infrastructure, security, and performance</description>
	<lastBuildDate>Thu, 29 Jul 2010 20:30:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: joe klein</title>
		<link>http://www.barkingseal.com/2009/01/ipv6-in-2009-are-you-kidding-me/comment-page-1/#comment-40</link>
		<dc:creator>joe klein</dc:creator>
		<pubDate>Mon, 23 Mar 2009 02:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.barkingseal.com/?p=463#comment-40</guid>
		<description>Actually, Trent is correct. You guys are in deinal. If your organizations has any current operating system in your environment then you have a very good chance IPv6 is already in your environment. This is based on hundreds of security assessment over the last year. 

Now you have one of two choices: The first is to leave this potential security vulnerabilty open, not including IPv6 in your risk model and mitigating IPv6 on your infrastructure. There for, you now in violation with your compliance. Opps. 

The second is you begin to mitigate the security exposure, by beginning the process of implementing IPv6.</description>
		<content:encoded><![CDATA[<p>Actually, Trent is correct. You guys are in deinal. If your organizations has any current operating system in your environment then you have a very good chance IPv6 is already in your environment. This is based on hundreds of security assessment over the last year. </p>
<p>Now you have one of two choices: The first is to leave this potential security vulnerabilty open, not including IPv6 in your risk model and mitigating IPv6 on your infrastructure. There for, you now in violation with your compliance. Opps. </p>
<p>The second is you begin to mitigate the security exposure, by beginning the process of implementing IPv6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blaine Berger</title>
		<link>http://www.barkingseal.com/2009/01/ipv6-in-2009-are-you-kidding-me/comment-page-1/#comment-35</link>
		<dc:creator>Blaine Berger</dc:creator>
		<pubDate>Mon, 05 Jan 2009 08:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.barkingseal.com/?p=463#comment-35</guid>
		<description>Trent - I laughed when I read this because IPV6 has enough IP addresses to give one to every living thing and every grain of sand. And certainly a costly network equipment upgrade spiral. -- Blaine</description>
		<content:encoded><![CDATA[<p>Trent &#8211; I laughed when I read this because IPV6 has enough IP addresses to give one to every living thing and every grain of sand. And certainly a costly network equipment upgrade spiral. &#8212; Blaine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dual Stack</title>
		<link>http://www.barkingseal.com/2009/01/ipv6-in-2009-are-you-kidding-me/comment-page-1/#comment-31</link>
		<dc:creator>Dual Stack</dc:creator>
		<pubDate>Sun, 04 Jan 2009 13:28:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.barkingseal.com/?p=463#comment-31</guid>
		<description>Before you &quot;jump ship and move to IPv6&quot; is a wrong architecture. The network will be dual stack for may decades. There will be IPv4 and IPv6 connectivity for servers and node during IPv6 transition. Any current application must support dual stack transition for seamless transition to the IPv6.</description>
		<content:encoded><![CDATA[<p>Before you &#8220;jump ship and move to IPv6&#8243; is a wrong architecture. The network will be dual stack for may decades. There will be IPv4 and IPv6 connectivity for servers and node during IPv6 transition. Any current application must support dual stack transition for seamless transition to the IPv6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: UC IPv6</title>
		<link>http://www.barkingseal.com/2009/01/ipv6-in-2009-are-you-kidding-me/comment-page-1/#comment-30</link>
		<dc:creator>UC IPv6</dc:creator>
		<pubDate>Sat, 03 Jan 2009 23:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.barkingseal.com/?p=463#comment-30</guid>
		<description>There will be more IPv6 lab testing for many applications including unified communcation world wide.</description>
		<content:encoded><![CDATA[<p>There will be more IPv6 lab testing for many applications including unified communcation world wide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars auridson</title>
		<link>http://www.barkingseal.com/2009/01/ipv6-in-2009-are-you-kidding-me/comment-page-1/#comment-29</link>
		<dc:creator>Lars auridson</dc:creator>
		<pubDate>Sat, 03 Jan 2009 21:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.barkingseal.com/?p=463#comment-29</guid>
		<description>Yes, you re right. You are just clueless and crazy :-)</description>
		<content:encoded><![CDATA[<p>Yes, you re right. You are just clueless and crazy <img src='http://www.barkingseal.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
