<?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: Recovering IPv4 Address Space</title>
	<atom:link href="http://blog.icann.org/2008/02/recovering-ipv4-address-space/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/</link>
	<description>Internet Corporation for Assigned Names and Numbers</description>
	<lastBuildDate>Mon, 23 Nov 2009 02:20:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Leo Vegoda</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11572</link>
		<dc:creator>Leo Vegoda</dc:creator>
		<pubDate>Fri, 15 Feb 2008 09:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11572</guid>
		<description>Larry,

The difficulty involved in reclaiming portions of a legacy /8 depend on how it has been used. In some cases it could be relatively easy to free up large, contiguous blocks and in other cases the space is highly fragmented.

The technical problems can doubtless be solved with time and money. I think the other issue is the incentive for the user of the address space to go through the renumbering process.

Three RIRs are discussing proposals to introduce mechanisms to allow the transfer of address blocks between their members. (A new proposal was introduced in ARIN). Perhaps those policies (if they are agreed) will provide that incentive?

Leo</description>
		<content:encoded><![CDATA[<p>Larry,</p>
<p>The difficulty involved in reclaiming portions of a legacy /8 depend on how it has been used. In some cases it could be relatively easy to free up large, contiguous blocks and in other cases the space is highly fragmented.</p>
<p>The technical problems can doubtless be solved with time and money. I think the other issue is the incentive for the user of the address space to go through the renumbering process.</p>
<p>Three RIRs are discussing proposals to introduce mechanisms to allow the transfer of address blocks between their members. (A new proposal was introduced in ARIN). Perhaps those policies (if they are agreed) will provide that incentive?</p>
<p>Leo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Seltzer</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11539</link>
		<dc:creator>Larry Seltzer</dc:creator>
		<pubDate>Thu, 14 Feb 2008 14:03:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11539</guid>
		<description>Leo,

I don&#039;t want to go too far with Jay Daley&#039;s argument (I think he&#039;s making more of an equity argument rather than saying that it would meaningfully extend the life of the IPv4 pool), but I have a question about those legacy assignments. 

You point out that many of these old /8 networks are at least partially assigned; assuming the allocations were organized enough for this, could the /8 be reclaimed and the assigned parts reassigned as /16s or something else lesser? How much work would that really be?</description>
		<content:encoded><![CDATA[<p>Leo,</p>
<p>I don&#8217;t want to go too far with Jay Daley&#8217;s argument (I think he&#8217;s making more of an equity argument rather than saying that it would meaningfully extend the life of the IPv4 pool), but I have a question about those legacy assignments. </p>
<p>You point out that many of these old /8 networks are at least partially assigned; assuming the allocations were organized enough for this, could the /8 be reclaimed and the assigned parts reassigned as /16s or something else lesser? How much work would that really be?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michele</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11404</link>
		<dc:creator>Michele</dc:creator>
		<pubDate>Tue, 12 Feb 2008 01:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11404</guid>
		<description>Leo
We&#039;ve been trying to encourage companies both big and small to IPv6 enable content websites here in Ireland. So far we&#039;ve had a reasonable level of interest and one commercial site has made the move:
http://blog.blacknight.com/blacknight_and_page7_media_lau.html

Regards

Michele</description>
		<content:encoded><![CDATA[<p>Leo<br />
We&#8217;ve been trying to encourage companies both big and small to IPv6 enable content websites here in Ireland. So far we&#8217;ve had a reasonable level of interest and one commercial site has made the move:<br />
<a href="http://blog.blacknight.com/blacknight_and_page7_media_lau.html" rel="nofollow">http://blog.blacknight.com/blacknight_and_page7_media_lau.html</a></p>
<p>Regards</p>
<p>Michele</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leo Vegoda</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11344</link>
		<dc:creator>Leo Vegoda</dc:creator>
		<pubDate>Mon, 11 Feb 2008 11:35:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11344</guid>
		<description>Jay, which space are you referring to when you say &quot;reclaiming this space might only buy a year or two at the most&quot;? The space I wrote about in this blog post probably extends the life of the IANA free pool by no more than three months. The other legacy /8 assignments are all at least partially used.

The RIRs were allocated 13 /8s last year. That means that even if the demand for space does not increase, buying one year would involve recovering almost one third of the legacy assigned space from networks that are actively using it. 

You seem to be proposing that legacy assignments should be reclaimed even though they are in use. Is that right?</description>
		<content:encoded><![CDATA[<p>Jay, which space are you referring to when you say &#8220;reclaiming this space might only buy a year or two at the most&#8221;? The space I wrote about in this blog post probably extends the life of the IANA free pool by no more than three months. The other legacy /8 assignments are all at least partially used.</p>
<p>The RIRs were allocated 13 /8s last year. That means that even if the demand for space does not increase, buying one year would involve recovering almost one third of the legacy assigned space from networks that are actively using it. </p>
<p>You seem to be proposing that legacy assignments should be reclaimed even though they are in use. Is that right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Daley</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11321</link>
		<dc:creator>Jay Daley</dc:creator>
		<pubDate>Mon, 11 Feb 2008 04:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11321</guid>
		<description>You do not seem to be acknowledging the important political dimension to this.  There is a strong perception in parts of the developing world that the /8 allocations to US corporations are inherently unfair.  Particularly as it is clear that only small parts of this address space are publicly routed.

So whilst reclaiming this space might only buy a year or two at the most, it would go a long way towards showing that management of address space by IANA and the RIRs is equitable and inclusive and there is no need for alternate arrangements.

BTW one or two years could actually make a huge difference in the ability of companies to plan the capital expenditure.</description>
		<content:encoded><![CDATA[<p>You do not seem to be acknowledging the important political dimension to this.  There is a strong perception in parts of the developing world that the /8 allocations to US corporations are inherently unfair.  Particularly as it is clear that only small parts of this address space are publicly routed.</p>
<p>So whilst reclaiming this space might only buy a year or two at the most, it would go a long way towards showing that management of address space by IANA and the RIRs is equitable and inclusive and there is no need for alternate arrangements.</p>
<p>BTW one or two years could actually make a huge difference in the ability of companies to plan the capital expenditure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leo Vegoda</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11251</link>
		<dc:creator>Leo Vegoda</dc:creator>
		<pubDate>Sat, 09 Feb 2008 19:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11251</guid>
		<description>I&#039;m not sure what you mean. IPv4 has just 4 billion addresses, not 30 billion. This isn&#039;t enough to address the Internet if everyone in the world has access.

IPv6 has far more addresses (about 340 trillion trillion trillion) but it is not backwards compatible with IPv4 and so the transition requires using both IPv4 and IPv6 at the same time. Unfortunately, that is expensive and does not generate any additional income for ISPs and other network operators. And so take-up has been so slow.

When the IANA and RIR IPv4 free pools are empty, ISPs and other network operators will probably find it very expensive to obtain additional IPv4 space and IPv6 will become more attractive. But deploying IPv6 means making changes to a lot of systems. As an example of the sorts of changes that need to happen, when Randy Bush added IPv6 to his network he found that he had &lt;a href=&quot;http://rip.psg.com/~randy/ipv6-westin.html&quot; rel=&quot;nofollow&quot;&gt;problems with DNSBLs not supporting IPv6 addresses&lt;/a&gt;. There were problems with other software, too.

There&#039;s a lot of work still to be done.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure what you mean. IPv4 has just 4 billion addresses, not 30 billion. This isn&#8217;t enough to address the Internet if everyone in the world has access.</p>
<p>IPv6 has far more addresses (about 340 trillion trillion trillion) but it is not backwards compatible with IPv4 and so the transition requires using both IPv4 and IPv6 at the same time. Unfortunately, that is expensive and does not generate any additional income for ISPs and other network operators. And so take-up has been so slow.</p>
<p>When the IANA and RIR IPv4 free pools are empty, ISPs and other network operators will probably find it very expensive to obtain additional IPv4 space and IPv6 will become more attractive. But deploying IPv6 means making changes to a lot of systems. As an example of the sorts of changes that need to happen, when Randy Bush added IPv6 to his network he found that he had <a href="http://rip.psg.com/~randy/ipv6-westin.html" rel="nofollow">problems with DNSBLs not supporting IPv6 addresses</a>. There were problems with other software, too.</p>
<p>There&#8217;s a lot of work still to be done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: network admin</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11212</link>
		<dc:creator>network admin</dc:creator>
		<pubDate>Fri, 08 Feb 2008 20:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11212</guid>
		<description>one thing i need to have clarified for myself. why is it so difficult to implement proper subnetowrking to save the ip addresses and have lots of ip addresses left when you can have over 30 billion ip addresses possible.... it is baffling me as to why there is this much stress over something that is very simple to fix...</description>
		<content:encoded><![CDATA[<p>one thing i need to have clarified for myself. why is it so difficult to implement proper subnetowrking to save the ip addresses and have lots of ip addresses left when you can have over 30 billion ip addresses possible&#8230;. it is baffling me as to why there is this much stress over something that is very simple to fix&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 贵州酒店</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11177</link>
		<dc:creator>贵州酒店</dc:creator>
		<pubDate>Fri, 08 Feb 2008 06:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11177</guid>
		<description>I are looking forword the IPv6 to be deployed</description>
		<content:encoded><![CDATA[<p>I are looking forword the IPv6 to be deployed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leo Vegoda</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11138</link>
		<dc:creator>Leo Vegoda</dc:creator>
		<pubDate>Thu, 07 Feb 2008 11:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11138</guid>
		<description>We have noticed that some networks use address space that has not been allocated. This is unfortunate as all the unicast IPv4 address space will be allocated, eventually. Using space that is properly allocated elsewhere is likely to cause problems and increase support costs. To some extent this is already the case.

ICANN staff has developed a way of measuring some (but not all) use of unallocated IPv4 address space. As &lt;a href=&quot;http://blog.icann.org/?p=240&quot; rel=&quot;nofollow&quot;&gt;John wrote&lt;/a&gt; a few weeks ago, we can measure the queries received at l.root-servers.net. We have used this to begin &lt;a href=&quot;http://www.esnog.net/gore1-files/ESNOG1-IANA-IDN-Update-draft-4.pdf&quot; rel=&quot;nofollow&quot;&gt;begin measuring the problem&lt;/a&gt;.

We are continuing to work on this topic and I hope we can write a blog article with some details fairly soon.</description>
		<content:encoded><![CDATA[<p>We have noticed that some networks use address space that has not been allocated. This is unfortunate as all the unicast IPv4 address space will be allocated, eventually. Using space that is properly allocated elsewhere is likely to cause problems and increase support costs. To some extent this is already the case.</p>
<p>ICANN staff has developed a way of measuring some (but not all) use of unallocated IPv4 address space. As <a href="http://blog.icann.org/?p=240" rel="nofollow">John wrote</a> a few weeks ago, we can measure the queries received at l.root-servers.net. We have used this to begin <a href="http://www.esnog.net/gore1-files/ESNOG1-IANA-IDN-Update-draft-4.pdf" rel="nofollow">begin measuring the problem</a>.</p>
<p>We are continuing to work on this topic and I hope we can write a blog article with some details fairly soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.icann.org/2008/02/recovering-ipv4-address-space/comment-page-1/#comment-11113</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 06 Feb 2008 20:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=271#comment-11113</guid>
		<description>I guess the Fastweb users in southern Milano (Italy) will begin to have problems, as soon as the 14.0.0.0/8 net will be sued to assign new addresses... (as Fastweb is used to use &quot;reserved&quot; address pools for its users, as the whole network is behind a NAT)</description>
		<content:encoded><![CDATA[<p>I guess the Fastweb users in southern Milano (Italy) will begin to have problems, as soon as the 14.0.0.0/8 net will be sued to assign new addresses&#8230; (as Fastweb is used to use &#8220;reserved&#8221; address pools for its users, as the whole network is behind a NAT)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
