<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi Hans, good morning list, I think there is no confusion. section 5.3 <a class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-649">https://www.ripe.net/publications/docs/ripe-649</a> [...] 5.3 Address Recycling Any address space that is returned to the RIPE NCC will be covered by the same rules as the address space intended in section 5.1. This section only applies to address space that is returned to the RIPE NCC and that will not be returned to the IANA but re-issued by the RIPE NCC itself. [...] What is you understanding of "not be returned to the IANA but re-issued by the RIPE NCC itself" ? In my understanding this does not talks about any space RECEIVED from IANA's Recovered IPv4 Pool Recovered space reiceved from IANA comes from a global policy ratified by RIRs in September 2012 Maybe Andrea Cima can clarify RIPE NCC understanding about this, Andrea could you please give us RIPE NCC understading? On the other hand it's easy to say that all the available pool can fall under the same policy in section 5.1. but it's clear that when last /8 was thought was to allow new entrants as well as existing LIRs develop IPv6 and keep fairness on the market. Sorry for repeating myself but please note that policy 2014-04 (<a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2014-04">https://www.ripe.net/participate/policies/proposals/2014-04</a>) removed IPv6 requirement to obtain last /22 IPv4 allocation. We have no IPv6 incentives but t-shirts! Gert, Sander (Chairs): may I ask you to give me/us your opinion about absence of IPv6 incetives in our policies don't you think we are missing something? regards Riccardo <div class="moz-cite-prefix">Il 20/04/2016 01:17, Hans Petter Holen ha scritto: </div> <blockquote cite="mid:5716BC84.2010406@oslo.net" type="cite"> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 16.04.2016 12.29, <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:remco.vanmook@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:remco.vanmook@gmail.com">remco.vanmook@gmail.com</a></a> wrote: </div> <blockquote cite="mid:57121420.6614c20a.ebfb5.4312@mx.google.com" type="cite">This confusion has been haunting the final /8 policy from day one - it was never about what to do with specifically 185/8, but what to do with all future allocations from the moment we needed to start allocating out of it. The policy text itself was never limited to a single /8, nor was that limitation any part of the discussion. </blockquote> I looked up the policy proposal at <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2010-02">https://www.ripe.net/participate/policies/proposals/2010-02</a> " <meta charset="utf-8"> <span style="color: rgb(51, 51, 51); font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 14.3px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 22.88px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: rgb(255, 255, 255);">This proposal describes how the RIPE NCC should distribute IPv4 address space from the final /8 address block it receives from the IANA." Reading the rest of the proposal I fully understand the confusion and find it hard to read your interpretation into the proposal. The updated policy after this proposal can be found in RIPE 509 <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-509#----use-of-last----for-pa-allocations">https://www.ripe.net/publications/docs/ripe-509#----use-of-last----for-pa-allocations</a> * <span style="color: rgb(51, 51, 51); font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 14.3px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 22.88px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none; background-color: rgb(255, 255, 255);">The following policies come into effect as soon as RIPE NCC is required to make allocations from the final /8 it receives from the IANA. It does not discuss the event where RIPE NCC gets more address space and could allocate from - which would strictly speaking not be allocation from the last /8 Tracing the policy text trough the versions - This text was first removed between * RIPE 599 published on 20 December 2013 <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-599#Use-last-for-PA-Allocations">https://www.ripe.net/publications/docs/ripe-599#Use-last-for-PA-Allocations</a>and * RIPE 604 - published on 4 Feb 2014: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-604">https://www.ripe.net/publications/docs/ripe-604</a> Where the text was changed to: <meta charset="utf-8"> <ol style="margin: 0px 0px 12px; padding: 0px 0px 0px 20px; box-sizing: border-box; list-style: decimal; color: rgb(51, 51, 51); font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 14.3px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 22.88px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"> <li style="margin: 0px; padding: 0px; box-sizing: border-box; display: list-item; max-width: 700px;">The size of the allocation made will be exactly one /22.</li> <li style="margin: 0px; padding: 0px; box-sizing: border-box; display: list-item; max-width: 700px;">The sum of all allocations made to a single LIR by the RIPE NCC after the 14th of September 2012 is limited to a maximum of 1024 IPv4 addresses (a single /22 or the equivalent thereof).</li> </ol> and no reference to the last /8. So I can easily understand the confusion. <pre class="moz-signature" cols="72">-- Hans Petter Holen Mobile +47 45 06 60 54 | <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:hph@oslo.net">hph@oslo.net</a> | <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://hph.oslo.net">http://hph.oslo.net</a> </pre> </blockquote> <div class="moz-signature">-- <pre>Ing. Riccardo Gori e-mail: <a class="moz-txt-link-abbreviated" href="mailto:rgori@wirem.net">rgori@wirem.net</a> Mobile: +39 339 8925947 Mobile: +34 602 009 437 Profile: <a class="moz-txt-link-freetext" href="https://it.linkedin.com/in/riccardo-gori-74201943">https://it.linkedin.com/in/riccardo-gori-74201943</a> </pre> <img src="cid:part8.05010508.08020400@wirem.net" width="200"> <pre>WIREM Fiber Revolution Net-IT s.r.l. Via Cesare Montanari, 2 47521 Cesena (FC) Tel +39 0547 1955485 Fax +39 0547 1950285 -------------------------------------------------------------------- CONFIDENTIALITY NOTICE This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by re- plying to <a class="moz-txt-link-abbreviated" href="mailto:info@wirem.net">info@wirem.net</a> Thank you WIREM - Net-IT s.r.l.Via Cesare Montanari, 2 - 47521 Cesena (FC) -------------------------------------------------------------------- </pre> </div> </body> </html>