<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Aleksi,<br>
<br>
a few comments inline:<br>
<br>
<div class="moz-cite-prefix">On 07/05/14 04:24, Aleksi Suhonen
wrote:<br>
</div>
<blockquote cite="mid:53699950.5060105@ssd.axu.tm" type="cite">Hi,
<br>
<br>
While we were formulating the proposal 2014-04, we came up with a
handful of other more radical alternatives too. We decided to
leave them out of the initial proposal text, because of their
controversial nature. We decided to instead present them to the
discussion on the mailing list, which I'm doing now:
<br>
<br>
OTHER RIRS
<br>
<br>
The current policy for final /8 IPv4 assignments requires that the
IPv6 address space is assigned by RIPE NCC. Assignments by other
RIRs aren't accepted. Proposal 2014-04 does not change this
oversight.
<br>
</blockquote>
and I agree that it should also be fixed. If you have IPv6 (no
matter from where and which color it has) then you should be allowed
to receive your /22.<br>
<blockquote cite="mid:53699950.5060105@ssd.axu.tm" type="cite">
<br>
I can see one snag, if IPv6 assignments from other RIRs were
accepted: multi-national corporations would hoard "an automatic
/22" from every RIR slightly more easily than the current policy
allows. In that case I would also add policy text that would make
sure that if the applicant already has a final /8 IPv4 assignment
from some other RIR, they can't get one from RIPE.
<br>
<br>
</blockquote>
that won't fly. other RIRs have different policies regarding their
last /8 (APNIC's is the only one similar to RIPE's AFAIK). Some RIRs
don't even have a /22 policy. <br>
And if someone needs IPv4 in the RIPE Region, getting the /22 should
not be limited to the last /8 policy from an other region. That
would be plain wrong.<br>
<blockquote cite="mid:53699950.5060105@ssd.axu.tm" type="cite">PROMOTE
IPv6 USAGE
<br>
<br>
Gert Doering wrote:
<br>
<blockquote type="cite">Historically it was put in there as an
encouragement for "last /8" LIRs
<br>
to "do something with IPv6"...
<br>
</blockquote>
<br>
The something that the current policy encourages LIRs to do with
IPv6:
<br>
<br>
* register a block and forget about it
<br>
<br>
To really promote IPv6 adoption, why not require final /8
applicants to demonstrate their IPv6 capability before being given
the IPv4 address block? The simplest way I came up with would be
to create a service mailbox under an IPv6 only sub-domain (e.g.
<a class="moz-txt-link-abbreviated" href="mailto:hostmaster@v6only.ripe.net">hostmaster@v6only.ripe.net</a>) and require that the applicants
complete some steps of their process with this mailbox.
<br>
<br>
This would verify that the applicant has access to IPv6 capable:
<br>
* routing
<br>
* DNS resolvers
<br>
* authoritative DNS
<br>
* SMTP servers
<br>
<br>
... and is not afraid to use them!
<br>
<br>
Well, of course the applicant could be using someone else's mail
system to complete those steps. I'm not sure if that matters.
<br>
</blockquote>
if you really want to go on that path, you may want to say that the
LIRs which can receive their last /22 must have at least 4 IPv6
RIPEness stars. But I really think a lot of people will oppose to
such an idea.<br>
<br>
cheers,<br>
elvis<br>
<br>
<div class="moz-signature">-- <br>
<table border="0" cellpadding="0" cellspacing="0" width="400">
<tbody>
<tr>
<td valign="top" width="180"><a href="http://v4escrow.net"
target="_blank"><img
src="cid:part1.00000104.00070307@v4escrow.net"
style="margin:10px 40px 0px 0px" height="96"
width="178"></a></td>
<td valign="top" width="200">
<h1 style="font-family: Arial, Helvetica, sans-serif;
font-size: 14px; color: rgb(51, 51, 51); margin: 0px 0px
10px;color:#1a9bd7;font-size:14px; ">Elvis Daniel Velea</h1>
<h2 style="font-family: Arial, Helvetica, sans-serif;
font-size: 14px; color: rgb(51, 51, 51); margin: 0px 0px
10px;color:#74757d;font-size:13px;font-weight:100; ">Chief
Business Analyst</h2>
<p style="font-family:Arial, Helvetica, sans-serif;
font-size:12px; line-height:20px; font-weight:regular;
color:#74757d; margin:5px 0px;"> <span
style="color:#000;">Email:</span> <a
href="mailto:elvis@v4escrow.net" style="color:#74757d;
text-decoration: none; ">elvis@V4Escrow.net</a><br>
<span style="color:#000;">US Phone:</span> +1 (702) 475 5914<br>
<span style="color:#000;">EU Phone:</span> +3 (161) 458 1914<br>
</p>
</td>
</tr>
<tr>
<td colspan="2">
<p style="font-family:Arial, Helvetica, sans-serif;
font-size:12px;
line-height:15px;color:#000;margin-top:15px;text-align:center;"
align="center">Recognised IPv4 Broker/Facilitator in:</p>
</td>
</tr>
<tr>
<td colspan="2"> <img
src="cid:part4.05000205.05050709@v4escrow.net"
usemap="#Map" style="margin-top:5px;" border="0"
height="28" width="376"> </td>
</tr>
<tr>
<td colspan="2" style="padding-left:5px;padding-right:15px;">
<p style="color:#bbb;font-family: Arial, Helvetica,
sans-serif;font-size:10px;margin-top:15px;text-align:center;">This
message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private
information. If you have received this email in error,
please notify the sender immediately and delete the
original.Any other use of this email is strictly
prohibited.</p>
</td>
</tr>
</tbody>
</table>
<map name="Map">
<area shape="rect" coords="1,2,65,28"
href="http://www.ripe.net/lir-services/resource-management/ipv4-transfers/brokers"
target="_blank">
<area shape="rect" coords="138,0,234,31"
href="http://www.apnic.net/services/become-a-member/manage-your-membership/transfer-resources/transfer-facilitators"
target="_blank">
<area shape="rect" coords="297,3,380,40"
href="https://www.arin.net/resources/transfer_listing/facilitator_list.html"
target="_blank">
</map>
</div>
</body>
</html>