<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML - vooraf opgemaakt Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTML-voorafopgemaaktChar
{mso-style-name:"HTML - vooraf opgemaakt Char";
mso-style-priority:99;
mso-style-link:"HTML - vooraf opgemaakt";
font-family:"Consolas",serif;
color:black;}
span.E-mailStijl19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Riccardo, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>></span> with all respect I don't see a "remarkable success" in current last /8 policy.<span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The fact that you don’t see it, doesn’t make it less true. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>RIPE IPv4 is out … the reservation of space for IXP’s and other uses ( like future new entrance ) doesn’t change that. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This is not something we have to explain .. this is not something that we will change. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The /22 IPv4 is not for new entrance to assign to customers.. it is to enable them to communicate via a CGNAT from a v6 world to a v4 world. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>If you don’t use the obtained v4 space for the intended use, it will never be enough and you will always feel incorrectly treated … <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This policy proposal (with all respect to you and Radu and good intentions) needs to stop as it gives people hope on something that isn’t there ... <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Erik Bais <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=NL style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'>Van:</span></b><span lang=NL style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext'> address-policy-wg [mailto:address-policy-wg-bounces@ripe.net] <b>Namens </b>Riccardo Gori<br><b>Verzonden:</b> vrijdag 15 april 2016 7:49<br><b>Aan:</b> address-policy-wg@ripe.net; remco.vanmook@gmail.com<br><b>Onderwerp:</b> Re: [address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Good Morning Remco, Good Morning List,<br><br>with all respect I don't see a "remarkable success" in current last /8 policy.<br>We are dealing with the same amount of space as September 2012 that in the meanwhile has been abused in several ways and there are really no incentives to IPv6 adoption.<br><br>There was only one requirement to obtain one IPv4 /22: request and obtain at least from /32 IPv6 to a maximum of /29 IPv6.<br>Am I wrong or this requirement has been removed?!?! Please explain that to a new entrant...<br>What does it mean? "we are running out. here your crumbs, sorry we have no solution" ?!?<br><br>If for you last /8 policy is a success to me IPv6 incentives policies looks absent. We completly failed from this point of view.<br>If you look at this where IPv4 exhaustion took place IPv6 is strongly gowing: <a href="https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption&tab=per-country-ipv6-adoption">https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption&tab=per-country-ipv6-adoption</a><br><br>I think this policy is not for faster exhaustion but for "farier exhaustion" and is offering a path to go over IPv4 while still needing it to grow.<br><br>kind regards<br>Riccardo<o:p></o:p></p><div><p class=MsoNormal>Il 15/04/2016 00:50, remco van mook ha scritto:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Dear colleagues, <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I'd like to reiterate my objection to this proposal. Anyone who thinks another block of 1,000 addresses is going to help them float their business is in my opinion delusional (because the next step would be an extra 2,000, then 4,000, ..). The problem is not that you're getting a /22 - the problem is that we're out of space, never to come back. I also object to the notion that new entrants who joined the game recently have any more entitlement than new entrants 2 years from now. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The final /8 policy in the RIPE region has been, in my opinion, a remarkable success because there's actually still space left to haggle about. What does need fixing is the fact that there are a few obvious loopholes that are now being used to contravene the intention of the policy, and are being used as a rationale for this proposal. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kind regards,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Remco<o:p></o:p></p></div><div><p class=MsoNormal>(no hats)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu, Apr 14, 2016 at 2:43 PM Marco Schmidt <<a href="mailto:mschmidt@ripe.net">mschmidt@ripe.net</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal style='margin-bottom:12.0pt'>Dear colleagues,<br><br>The Discussion Period for the policy proposal 2015-05, "Last /8<br>Allocation Criteria Revision" has been extended until 13 May 2016.<br><br>The goal of this proposal is to allow LIRs to request an additional /22<br>IPv4 allocation from the RIPE NCC every 18 months.<br><br>The text of the proposal has been revised based on mailing list feedback<br>and we have published a new version (2.0) today. As a result, a new<br>Discussion Phase has started for the proposal.<br><br>Some of the differences from version 1.0 include:<br>- Additional /22 IPv4 allocations can be only provided from address<br>space outside 185/8<br>- Only LIRs with less than a /20 in total are eligible to receive<br>additional allocations<br>- LIRs must document their IPv6 deployment as part of the request<br><br>You can find the full proposal at:<br><br><a href="https://www.ripe.net/participate/policies/proposals/2015-05" target="_blank">https://www.ripe.net/participate/policies/proposals/2015-05</a><br><br>We encourage you to review this policy proposal and send your comments<br>to <<a href="mailto:address-policy-wg@ripe.net" target="_blank">address-policy-wg@ripe.net</a>>.<br><br>Regards,<br><br>Marco Schmidt<br>Policy Development Officer<br>RIPE NCC<o:p></o:p></p></blockquote></div></div></div></blockquote><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>-- <o:p></o:p></p><pre>Ing. Riccardo Gori<o:p></o:p></pre><pre>e-mail: <a href="mailto:rgori@wirem.net">rgori@wirem.net</a><o:p></o:p></pre><pre>Mobile: +39 339 8925947<o:p></o:p></pre><pre>Mobile: +34 602 009 437<o:p></o:p></pre><pre>Profile: <a href="https://it.linkedin.com/in/riccardo-gori-74201943">https://it.linkedin.com/in/riccardo-gori-74201943</a><o:p></o:p></pre><p class=MsoNormal><img border=0 width=200 height=80 id="_x0000_i1025" src="cid:image002.jpg@01D196F8.CD456CF0"><o:p></o:p></p><pre>WIREM Fiber Revolution<o:p></o:p></pre><pre>Net-IT s.r.l.<o:p></o:p></pre><pre>Via Cesare Montanari, 2<o:p></o:p></pre><pre>47521 Cesena (FC)<o:p></o:p></pre><pre>Tel +39 0547 1955485<o:p></o:p></pre><pre>Fax +39 0547 1950285<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>--------------------------------------------------------------------<o:p></o:p></pre><pre> CONFIDENTIALITY NOTICE<o:p></o:p></pre><pre>This message and its attachments are addressed solely to the persons <o:p></o:p></pre><pre>above and may contain confidential information. If you have received <o:p></o:p></pre><pre>the message in error, be informed that any use of the content hereof <o:p></o:p></pre><pre>is prohibited. Please return it immediately to the sender and delete <o:p></o:p></pre><pre>the message. Should you have any questions, please contact us by re-<o:p></o:p></pre><pre>plying to <a href="mailto:info@wirem.net">info@wirem.net</a><o:p></o:p></pre><pre> Thank you<o:p></o:p></pre><pre>WIREM - Net-IT s.r.l.Via Cesare Montanari, 2 - 47521 Cesena (FC)<o:p></o:p></pre><pre>--------------------------------------------------------------------<o:p></o:p></pre></div></div></body></html>