<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Domain name big bang solving lack of addresses?</title>
	<link>http://blogs.educationau.edu.au/jleeson/2008/06/30/domain-name-big-bang-solving-lack-of-addresses/</link>
	<description>a blog by Jerry Leeson</description>
	<pubDate>Wed, 07 Jan 2009 17:52:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Claude Gelinas</title>
		<link>http://blogs.educationau.edu.au/jleeson/2008/06/30/domain-name-big-bang-solving-lack-of-addresses/#comment-70983</link>
		<pubDate>Mon, 30 Jun 2008 13:58:41 +0000</pubDate>
		<guid>http://blogs.educationau.edu.au/jleeson/2008/06/30/domain-name-big-bang-solving-lack-of-addresses/#comment-70983</guid>
					<description>Thanks for this explanation ; )

My main concern with IPv6 has to do with privacy. With IPv4, most of the internal networks aren't visible outside the firewall but with IPv6, every single device is more likely to have its own address which could end up being directly visible from the internet.

Although device-specific firewalling might emerge, I feel IPv6 could make it more difficult to maintain true privacy. IPv4, with its inevitable internal addressing, seems more effective at preserving privacy "by default".</description>
		<content:encoded><![CDATA[<p>Thanks for this explanation ; )</p>
<p>My main concern with IPv6 has to do with privacy. With IPv4, most of the internal networks aren&#8217;t visible outside the firewall but with IPv6, every single device is more likely to have its own address which could end up being directly visible from the internet.</p>
<p>Although device-specific firewalling might emerge, I feel IPv6 could make it more difficult to maintain true privacy. IPv4, with its inevitable internal addressing, seems more effective at preserving privacy &#8220;by default&#8221;.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
