<html><body bgcolor="#FFFFFF"><div>My understanding is that returning unused IPv4 would make us win weeks not years so may be too much efforts for little gain?<br><br>Toute connaissance est une réponse à une question</div><div><br>On 26/10/2008, at 7:57, "Chris Grundemann" <<a href="mailto:cgrundemann@gmail.com">cgrundemann@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>As one more possible avenue for ISOC to pursue; there was a recent suggestion on the ARIN PPML by Tom Vest that we look into the idea of a tax credit to organizations which return space to their RIR (<a href="http://lists.arin.net/pipermail/arin-ppml/2008-October/012386.html"><a href="http://lists.arin.net/pipermail/arin-ppml/2008-October/012386.html">http://lists.arin.net/pipermail/arin-ppml/2008-October/012386.html</a></a>). I think that at least in the US, it has a potential to help and I wonder what others thoughts are?<br>
~Chris<br><br><div class="gmail_quote">On Sat, Oct 25, 2008 at 2:35 PM, Sivasubramanian Muthusamy <span dir="ltr"><<a href="mailto:isolatedn@gmail.com"><a href="mailto:isolatedn@gmail.com">isolatedn@gmail.com</a></a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Sat, Oct 25, 2008 at 4:06 PM, Franck Martin <<a href="mailto:franck@sopac.org"><a href="mailto:franck@sopac.org">franck@sopac.org</a></a>> wrote:<br>
<br>
> What would you and others suggest ISOC should do to save the titanic?<br>
<br>
</div>Hello Frank Martin, John Schnizlein,<br>
<br>
1. Focus on promoting migration to IPV6 rather than worry to much<br>
about the IPV4 Legacy? The more ICANN and the RIRs fret over the hard,<br>
unpleasant decisions that need to be taken on IPV4, greater would be<br>
the time taken to transition to IPV6. Some breathing space is indeed<br>
required, but the extent of importance given to managing IPV4<br>
resources appear to be in the order of extending the life span of the<br>
IPV4 Legacy. What ISOC could do is to encourage hard, tough decisions<br>
and make it swift. The address spaces were allocated almost for free,<br>
at a throwaway price, and now they are dear. Any thing scarce brings<br>
in a lot of value. The businesses are bound to resist the idea of<br>
letting them all go exactly at this opportunistic moment. So, remind<br>
everyone that these are relatively 'free" assets and make all the<br>
tough decisions that are necessary on the issues of recalling unused<br>
addresses or on allowing/ disallowing transfers. ( At the same time,<br>
some consideration needs to given to the inexplicable aspects in<br>
business - these "assets" might have been acquired at a negligible<br>
cost, but around these allocations businesses are bound to have<br>
invested a considerably, so the "accumulated" cost of these assets<br>
would in reality be a lot more than initially paid for. If ICANN as<br>
many cents as collected on allocation, it might square up ICANN's<br>
books, but might not be the same case with businesses. )<br>
<br>
2. Declare War. It requires war like measures to cause IPV6 adopted<br>
before it is too late.<br>
<div class="Ih2E3d"><br>
<br>
On Sun, Oct 26, 2008 at 1:27 AM, John Schnizlein <<a href="mailto:schnizlein@isoc.org"><a href="mailto:schnizlein@isoc.org">schnizlein@isoc.org</a></a>> wrote:<br>
<br>
> Yes, price speculation is possible in an unregulated market for IPv4 address<br>
> blocks. This speculation could, as your doubt suggests, increase volatility in such<br>
> a market.<br>
<br>
</div>Should we be complacent at this threat of speculative trade in the<br>
names and numbers space? Speculation has done enough harm to the<br>
World Economy, shouldn't the Internet be kept away from such trade<br>
practices ?<br>
<br>
Perhaps ICANN could make it mandatory that transfers are routed through RIRs.<br>
<font color="#888888"><br>
Sivasubramanian Muthusamy<br>
ISOC India Chennai.<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Chapter-delegates mailing list<br>
<a href="mailto:Chapter-delegates@elists.isoc.org"><a href="mailto:Chapter-delegates@elists.isoc.org">Chapter-delegates@elists.isoc.org</a></a><br>
<a href="http://elists.isoc.org/mailman/listinfo/chapter-delegates" target="_blank"><a href="http://elists.isoc.org/mailman/listinfo/chapter-delegates">http://elists.isoc.org/mailman/listinfo/chapter-delegates</a></a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Chris Grundemann<br><a href="http://www.chrisgrundemann.com"><a href="http://www.chrisgrundemann.com">www.chrisgrundemann.com</a></a><br><a href="http://www.linkedin.com/in/cgrundemann"><a href="http://www.linkedin.com/in/cgrundemann">www.linkedin.com/in/cgrundemann</a></a><br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Chapter-delegates mailing list</span><br><span><a href="mailto:Chapter-delegates@elists.isoc.org">Chapter-delegates@elists.isoc.org</a></span><br><span><a href="http://elists.isoc.org/mailman/listinfo/chapter-delegates">http://elists.isoc.org/mailman/listinfo/chapter-delegates</a></span><br></div></blockquote></body></html>