<div dir="ltr">I would go s far as to direct ARIN staff to provide provisional approval. <div>The process would look like this:<div><br></div><div>Customer: ARIN, I have a /16. I am currently using 200 IPs as documented below. </div><div>I would be willing to sell my /16 and replace it with a /24 if I can be assured that I </div><div>will be approved to get a /24.</div><div><br></div><div>ARIN: based on your current utilization you are pre-approved to transfer a /24 </div><div>on the condition that no longer hold the /16 and your utilization as reported </div><div>remains unchanged. </div><div><br></div><div><br></div><div>The customer could then go off and sell the /16 contingent on buying a /24 </div><div>and transferring it. Buy the /24, renumber into the /24 and then submit matching </div><div>transfer requests requesting the transfer of the /16 to the recipient which should </div><div>be held up until the transfer of a /24 from the source is also approved. </div><div><br></div><div>(I think of this like the complicated kidney donation surgeries) </div><div><br></div><div>I don't think we need policy for this, just the AC to advice ARIN on </div><div>the fact that this behavior is not prohibited under policy, and is what</div><div>the community desires ARIN to do in this situation.</div><div><br></div><div>I do not think ARIN should maintain a pool for this.</div><div><br></div><div>I would support ARIN holding a transfer in escrow, but I think it is unlikely </div><div>that a party is willing to number out of their space, be down, and then get </div><div>new space and be back up, so I don't see this being useful.</div><div><br></div><div>___Jason</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 19, 2016 at 9:18 PM, Gary Buhrmaster <span dir="ltr"><<a href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Apr 11, 2016 at 5:43 PM, Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</a>> wrote:<br>
....<br>
<span class="">> I’d be OK with this, but given that there is remaining free pool for these resources, I’m not sure that it isn’t better to have a clear policy that when the resources in these categories are no longer needed, voluntary return to ARIN is expected.<br>
<br>
</span>On Monday, there was discussion (during policy experience report)<br>
about ARIN not being able to provide "theoretical" pre-qualifications<br>
in the case where (in the example) you transfer a /16 to someone,<br>
and would want to get a /24 from somewhere else. And while most<br>
steeped in the ARIN process understand that qualifying is an almost<br>
certainty, that does not take it to the level some seem to need to feel<br>
entirely comfortable.<br>
<br>
As far as this proposal, I can imagine there to be cases were a transfer<br>
may only make sense if the receiving org can be assured that they will<br>
be able to get the IP numbers from a reserved pool which ARIN cannot<br>
make assurance on in advance. And while (as before) everyone may be<br>
(almost) 100% sure that the recipient will qualify, that does not always<br>
make everyone sufficiently comfortable.<br>
<br>
It would seem to be nice for a 8.3 transfer which happens to include<br>
reserved pool space not turn into another policy experience report<br>
bullet for not being able to successfully transfer (worst case?) "CI"<br>
space if indeed the recipient would otherwise qualify (and potentially<br>
force a renumber of such resources for no particular policy reason).<br>
<br>
I do agree with Owen that these cases are unlikely. And regardless<br>
of whether the (what I think is) better language as proposed by Scott<br>
is included, I would support the policy moving forward to address<br>
the problem statement.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</div>