<div><br></div>Who are the shepherds and should I expect to hear from them with plenty of time available prior to the next AC meeting to make potential initial adjustments? <div><br></div><div>Best, </div><div><br></div><div>
Martin</div><div><br></div><div><span></span><br><br>On Monday, February 17, 2014, Scott Leibrand <<a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>Marc,</div><div><br></div><div>Good input, thanks. Can you expand a bit on which aspects of the LRSA some of your clients find burdensome, and which aspects of RIPE 605 they find preferable? As we (and particularly the AC shepherds) work with the proposal originator on getting a clear problem statement and then figuring out which parts of prop-203 are in scope for the PDP (and which parts should be submitted through the ACSP), it would be good to have your perspective on what aspects of the RIPE policy would be most helpful for making sure that transfers from non-RSA address holders get properly recorded. <br>
<br>Thanks,<br><div>Scott</div></div><div><br>On Feb 17, 2014, at 11:53 AM, "Lindsey, Marc" <<a href="javascript:_e(%7B%7D,'cvml','mlindsey@lb3law.com');" target="_blank">mlindsey@lb3law.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div>
<div>
<p class="MsoNormal">I advise several large legacy block holders. Some of them signed the LRSA, but many have not. For them, the burdens imposed by the LRSA outweigh the benefits. Some on the PPML have suggested that off-contract legacy holders don’t sign
up with ARIN because they want to be free-riders. But the fees (and the avoidance of the fees) are not a factor in their LRSA decision.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Based on my experience working with legacy block holders, I believe adopting a policy substantially similar to RIPE 605 (ARIN prop 203) would go a long way in harmonizing the interests of the ARIN community with the community of legacy
holders that do not have formal relationships with ARIN. <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">ARIN’s absolute control over additional allocations of “free” IPv4 numbers in its region has served as the primary policy enforcement mechanism. This carrot really only works on recipients that need more IPv4 numbers, and then only as
long as ARIN has free numbers to give out. It doesn’t directly influence the behavior of many legacy block holders when they convey their spare numbers. Legacy holders are a major source of future IPv4 number distributions, and their relevance to the broader
ARIN community will become more prominent as ARIN’s IPv4 free pool reaches depletion.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">In the secondary market context, ARIN now relies on its ability to withhold registry database updates as the primary means to extend enforcement of its current policies into private transactions between parties conveying beneficial use
of IPv4 numbers. This, however, is a weak enforcement tool. Two parties can convey beneficial use of IPv4 numbers in lawful commercial transactions without updating ARIN’s registry database. But IPv4 number conveyances not recorded in the registry system
produces very undesirable results – the “reality” in the registry database will not reflect operational reality, as David Conrad and others have pointed out in several posts.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Buyers and sellers would prefer to document their conveyances in a reliable and accurate public registry, but not if the contingencies and conditions materially and adversely affect their commercial arrangement. RIPE 605/ ARIN prop 203
recognizes this reality. With a little tweaking, adopting it would go a long way in minimizing the disincentives now facing legacy holders (and entities that want to acquire their numbers) when contemplating whether updating the registry database is worth
the risk of subjecting their transactions to ARIN’s approval process. <u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style>Marc Lindsey</span></b><span style><br>
Levine, Blaszak, Block & Boothby, LLP<br>
2001 L Street, NW Suite 900<br>
Washington, DC 20036<br>
<i>Office:</i> (202) 857-2564<br>
<i>Mobile:</i> (202) 491-3230<br>
<i>Email:</i> </span><span style="color:#1f497d"><a href="javascript:_e(%7B%7D,'cvml','mlindsey@lb3law.com');" target="_blank"><span style="color:#0563c1">mlindsey@lb3law.com</span></a><br>
</span><span style>Website: </span><span style="color:#1f497d"><a href="http://www.lb3law.com" target="_blank"><span style="color:#0563c1">www.lb3law.com</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="javascript:_e(%7B%7D,'cvml','ARIN-PPML@arin.net');" target="_blank">ARIN-PPML@arin.net</a>).</span><br>
<span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>Please contact <a href="javascript:_e(%7B%7D,'cvml','info@arin.net');" target="_blank">info@arin.net</a> if you experience any issues.</span></div>
</blockquote></div></blockquote></div>