<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 4, 2017, at 08:49 , Arnaud AMELINA <<a href="mailto:amelnaud@gmail.com" class="">amelnaud@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="auto" class=""><div class="">Hi Owen, Hi Community , see in lines<br class=""></div><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">Le 31 juil. 2017 17:54, "Owen DeLong" <<a href="mailto:owen@delong.com" target="_blank" class="">owen@delong.com</a>> a écrit :<br type="attribution" class=""><blockquote class="gmail-m_7661495750926472626quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-m_7661495750926472626quoted-text">>>>> combined with the failure to implement IPv6<br class="">
>>>> at a similar level because it has the same kind of cost-shifting effect.<br class="">
>>>><br class="">
>>>>> But using your analogy, please help me understand how the two liken,<br class="">
>>>>> who is dumping what on who, and which side is facing any costs as a<br class="">
>>>>> result.<br class="">
>>>><br class="">...<br class="">
>><br class="">
>><br class="">
><br class="">
> As an example: There is a residential ISP in South Africa who has over 500 IPv4 prefixes. How many IPv6 prefixes do they announce? None. ZERO. You are saying that this operator should be allowed as much more IPv4 space as they can get, until it runs out, and tough luck to the new IPv6 operator down the line who needs IPv4 to connect to the legacy Internet. I'm sorry, I can not, and won't support the continued distribution of IPv4 resources to existing operators to maintain the IPv4 status quo.<br class="">
<br class="">
</div>Not at all… If you want to write a policy that resolves this issue without the other baggage and problems present in this policy, I would support a clean policy designed to address that issue and make space available to ANYONE specifically for IPv6 to IPv4 connectivity/transition. In fact, I wrote such a policy in the ARIN region years ago and it is now NRPM section 4.10 in the ARIN region.<br class="">><br class="">><br class=""><br class=""><div dir="auto" class="">I don't really know how things work in ARIN region, but
the proposal which led to section 4.10 of ARIN NRPM was authored by
Alain Durand.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><a href="https://www.arin.net/policy/proposals/2008_5.html" target="_blank" class="">https://www.arin.net/policy/<wbr class="">proposals/2008_5.html</a></div><div dir="auto" class=""><a href="http://lists.arin.net/pipermail/arin-ppml/2008-June/011277.html" target="_blank" class="">http://lists.arin.net/<wbr class="">pipermail/arin-ppml/2008-June/<wbr class="">011277.html</a></div></blockquote></div></div></div></div></div></div></blockquote><div><br class=""></div></div>Indeed, 4.10 is actually the result of a merger of multiple proposals, one of which was written by Alain and one of which I authored. I apologize for my misstatement as compared to the record.<div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""></div></body></html>