<div dir="ltr">Owen,<div><br></div><div>I like your suggestions, but offer a few friendly amendments.</div><div><br></div><div>I think the fee for source block pre-certification should be primarily based </div><div>on the cost to investigate providence of the number space. Use </div><div>that cost as the starting point, and possibly increase the price</div><div>if it is not sufficiently high to to discourage abuse of the process.</div><div><br></div><div>The research of providence should relate to the entire aggregate</div><div>even if only a small portion is considered for transfer. In other words,</div><div>it is a one time resource certification fee for the first transfer out of</div><div>the aggregate, and future transfers out of the same aggregate do</div><div>not carry an additional fee.</div><div><br></div><div><br></div><div>If there are multiple blocks sharing the same providence, </div><div>(e.g. company Xyz, Inc. was issues A.B.C.0/20 and D.E.F.0/16.</div><div>Company Xyz, Inc. was bought by company Lmno, LLC. and </div><div>merged into Newco Inc.) then the fee should cover all of those blocks.</div><div><br></div><div>WRT marking, I think it needs to equally apply to resources under RSA or</div><div>under pre-certification of providence. I am agnostic if it needs to be distinguishable</div><div>between RSA and non-RSA pre-certification, or not.</div><div><br></div><div>The listing of the providence either needs to be public, or the seller needs to be</div><div>able to get some sort of certified proof from ARIN of its status that can be used</div><div>anonymously by any potential purchaser to verify its authenticity. </div><div><br></div><div>I also agree with David, about needing some flexibility in redirecting payment of these fees.</div><div><br></div><div>__Jason</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 15, 2016 at 8:57 AM, Owen DeLong <span dir="ltr"><<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So I’ve been watching this and thinking about the situation. It occurs to me that perhaps we should consider the following:<br>
<br>
1. Open up a pre-approval process for resource suppliers similar to the current pre-approval process<br>
for requestors.<br>
<br>
2. Set a fee for pre-approval that would apply only to resources being pre-approved which are not already subject<br>
to an RSA. Ideally, this fee should be nominal, but large enough to discourage abuse of the process.<br>
<br>
3. Charge the same fee for any supplier of transferred resources not covered by RSA, whether at time of request<br>
or in a pre-approval process.<br>
<br>
4. Possibly provide some mechanism by which entities that wish to do so can have their pre-approved resources marked<br>
as such in whois and/or STLS.<br>
<br>
This fee would be separate from the fee collected for a transfer at the time of the transfer, though that fee could, potentially, be reduced accordingly to reflect the lower cost of transactions involving known resources. In this way, the seller would be responsible for paying the provenance costs and the buyer would be responsible for paying the administrative costs of processing the transfer.<br>
<br>
This seems like a good balance to me.<br>
<br>
Thoughts?<br>
<span class="HOEnZb"><font color="#888888"><br>
Owen<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<wbr>_________________<br>
ARIN-Consult<br>
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br>
List (<a href="mailto:ARIN-consult@arin.net">ARIN-consult@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-consult</a> Please contact the ARIN Member Services<br>
Help Desk at <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" data-smartmail="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>