<div dir="ltr">Hello, <br><br>I agree with David. After further thought, I believe the registration of PA Assignments that are used by entities other than the holding LIR should remain *mandatory*. For reasons of transparency and well, to know who is using the IP space. <br><br>But I still believe there would be benefit in changing the registration policy of LIR infrastructure Assignments to *optional*. Why? Primarily to: <br>a. Reduce data duplication. The LIR’s tech and admin contact info is already contained in the parent PA Allocation (and also in several other LIR objects). <br>b. Support data accuracy. Anecdotal but from my experience of managing multiple LIRs of different sizes and their address space over the years, I know that simply having less objects to maintain in the RIPE database makes it easier, and more likely, for the LIR admin to keep their data up-to-date. <br><br>Interesting stats (thanks Ed!): <br>- Total IPv4 PA Allocations in the database today = 60,587 <br>- Allocations without any Assignment = 18,157 (30% of total) <br>- 14,744 of those 18,157 childless Allocations have a covering route object <br>Under current policy, the LIRs should register 14,744 - 29,488 additional Assignment inetnums in the RIPE database. What value would that bring? <br><br>I also like Gert’s suggestion to better educate LIRs about what the community expects of them – incl. database registration – in a BCP document. Both efforts can help improve data management in the RIPE Database going forward. <br><br>Regards, <br>James <br><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 7, 2022 at 8:03 PM David Farmer via address-policy-wg <<a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 4, 2022 at 2:44 AM Angela Dall'Ara <<a href="mailto:adallara@ripe.net" target="_blank">adallara@ripe.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<br>
<p class="MsoNormal"><span>Dear colleagues,</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>A new RIPE Policy Proposal, 2022-02,
"Remove
mandatory IPv4 PA assignment registration in the RIPE Database"
</span></p>
<p class="MsoNormal"><span>is now available for discussion.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>This goal of this proposal is to
change the
registration of IPv4 assignments from mandatory to optional.</span></p></div></blockquote><div><br></div><div>The registration of IPv4 PA assignments should not be completely optional. Using the word "optional" implies to me that the decision to register an assignment or not is completely at the discretion of the LIR, and I don't believe that is appropriate. LIRs should have an obligation to register PA assignments if the registration is requested by the customer who receives the assignment and/or if the assignment will be visible outside the LIR's network, such as in the global route table. However, registration of assignments not requested by the customer or that are not visible outside the LIR's network should be at the LIR's discretion.</div><div><br></div><div>Thanks</div></div><div><br></div>-- <br><div dir="ltr">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div></div>
-- <br>
<br>
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://lists.ripe.net/mailman/listinfo/address-policy-wg" rel="noreferrer" target="_blank">https://lists.ripe.net/mailman/listinfo/address-policy-wg</a><br>
</blockquote></div>