<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>
<blockquote type="cite">
<div>On Feb 21, 2024, at 1:56 AM, Owen DeLong <owen@delong.com> wrote:</div>
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>
<blockquote type="cite">
<div>On Feb 20, 2024, at 16:55, John Curran <jcurran@arin.net> wrote:</div>
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div><br>
</div>
<div>Alas, the challenge is that there are legacy resource holders who have made a conscious decision </div>
<div>over the years that they are better off not entering into a registration services agreement with ARIN – </div>
<div>the same agreement that every other resource holder has & with the same terms and conditions – </div>
<div>and thus they decline to receive the full set of services as every other registry customer. While it is</div>
<div>possible that the benefits of RPKI will impact their consideration of the matter, it’s not at all assured.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
In its current state, RPKI is at best a cryptographically signed hint at how to best spoof an advertisement.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>That is case only for those who do not perform RPKI ROV – as it is those who fail to perform ROV (or rely</div>
<div>on others that fail to perform ROV) that run the risk of routing impact by such spoofing… i.e., a self-inflicted</div>
<div>injury to some extent. </div>
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div><br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>As for the reason why, we’ve heard it asserted by some legacy resource holders that they hold </div>
<div>unspecified and/or unproven rights to their number resource entries in the ARIN registry, and </div>
<div>furthermore that entry into an ARIN registration services agreement would impact those rights. </div>
<div>While ARIN has changed the registration agreement several times to reduce the probability of </div>
<div>any conflict, it is a realistic concern given the otherwise indeterminate nature of the assertions. </div>
</div>
</div>
</blockquote>
<div><br>
</div>
In my case, I entered into the ARIN Legacy RSA based on a set of conditions that were not expected to change. The</div>
<div>ARIN board chose to change those conditions over my objections, but would not give me the option of retaining my</div>
<div>resources and going back to an uncontracted state. Fortunately, I found a loophole by transferring my resources to</div>
<div>the RIPE NCC as uncontracted legacy resources, so my only relationship with ARIN regards my IPv6 /48.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
That is not a “loophole” but rather a feature of the confederated nature of Internet numbers registry system – </div>
<div>each RIR community, through its own governance mechanisms, determines its own policies and services. </div>
<div>
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div><br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>ARIN was formed to take on full responsibility for the Internet number registry that was previously </div>
<div>administered under USG direction, and to provide a clear voice to this community on how these </div>
<div>number resources are managed. We have provided this community with the ability to elect its own </div>
<div>governing body for ARIN (the ARIN Board of Trustees) and that body has consistently held for over </div>
<div>25 years that that ARIN should provide legacy holders with the same basic registry services that they </div>
<div>were receiving at ARIN’s formation without cost or contract. However, we have also heard consistent </div>
<div>community demand for equitable treatment of _all_ ARIN customers in terms of agreements and fees; </div>
<div>this should not be surprising given that the ARIN registry exists in service to the entire community. </div>
</div>
</div>
</blockquote>
<div><br>
</div>
No, you have provided the membership, not the community, with the ability to elect the BOT and the AC.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
Note that when ARIN was first formed even that ability for the community to elect a Board wasn’t present – </div>
<div>we had to define the membership and provide it with the right to elect the Board and the AC. Over time </div>
<div>we have continued to vest more authority in the ARIN membership, and this has included the member right </div>
<div>to remove trustees, to be consulted on governance bylaw changes, etc. </div>
<div><br>
</div>
<div>We have even gone as far as to place control over changes to the registration service agreement itself with </div>
<div>the members (as the latest RSA provides that ARIN may only modify its terms for a compelling need to due </div>
<div>to a discrete, identifiable change in relevant statute or caselaw, or upon recommendation of the Board with </div>
<div>a ratification by ARIN member vote.) </div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>Please note that the membership consists solely of those who have both opted in to some form of RSA and expressed a desire to participate in ARIN governance.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
To be clear, the membership now consists of all organizations receiving ARIN services for their Internet </div>
<div>number resources under contract (this includes IPv4, IPv6, and ASN holders), as these are all Service </div>
<div>Members. Those that wish to participate in ARIN governance may opt to become ARIN General Members </div>
<div>(by agreeing to vote in elections, be published in the membership directory, contacted with governance </div>
<div>information, etc. )</div>
<div><br>
</div>
<div>The goal is a stable self-governing organization that allows those in the community that wish to participate</div>
<div>in governance to have a voice in the way that number resources are managed in the registry, and those </div>
<div>simply want to receive registry services to do so without the overhead of governance involvement. One</div>
<div>doesn’t have to participate in ARIN governance, but you are still governed by the whatever those that do </div>
<div>participate end up deciding. </div>
<div>
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div><br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>Further, the holding of the BoT that ARIN should provide those services to legacy holders without contract or cost is widely understood to be a promise ARIN made to the resource holding community at or near the time that it was awarded with that responsibility.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
ARIN has continued provide such service to date, as it has been viewed as appropriate course by the </div>
<div>member-elected Board of Trustees. Ultimately, however, ARIN is a membership organization, and it will </div>
<div>take whatever course of action is set by the ARIN membership who choose to participate in its governance. </div>
<div>
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div><br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div><font color="#00afcd"><span style="caret-color: rgb(0, 175, 205);">...</span></font></div>
<div>
<blockquote type="cite">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div>However, if they want to receive all of services that have been funded by the ARIN members – such as </div>
<div>authenticated IRR and RPKI – then they have to agree to the same registry terms as everyone else. </div>
<div>Doing so is quite simple, but does require being comfortable with being treated the same as every other </div>
<div>ARIN member – a problematic requirement for some given that they hold inherently inequitable beliefs</div>
<div>regarding their number resources in the ARIN registry. </div>
</div>
</div>
</blockquote>
<div><br>
</div>
IMHO, this is a derogatory and unfair characterization of the legacy holders who have, for various reasons, chosen not to adopt the ARIN RSA.</div>
</div>
</div>
</blockquote>
<br>
</div>
<div>Apologies, it was not my goal to cast aspersions on those who have chosen not to enter into a registration </div>
<div>services agreement, but rather to simply convey (in a clear and accurate manner) the inherent conflict between</div>
<div>their expectations and ARIN’s goals of a member-governed organization that provides equitable treatment of</div>
<div>all members. </div>
<div><br>
</div>
<div>I note that this thread, while perhaps informative on several related topics, has wandered a bit astray from the </div>
<div>original question of the community consultation – i.e., the proposal that we change the ARIN Online interface </div>
<div>for the Hosted RPKI service to provide additional information on current routing state to the user (as further </div>
<div>described here – <a href="https://www.arin.net/participate/community/acsp/consultations/2024/2024-1/">https://www.arin.net/participate/community/acsp/consultations/2024/2024-1/</a>) </div>
<div><br>
</div>
<div>To the extent that there is further feedback or suggestions regarding this proposed service change, please </div>
<div>provide it here on the list as soon as possible (as this consultation will close in just over one week’s time.) </div>
<div><br>
</div>
<div>Thanks! </div>
<div>/John</div>
<div><br>
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
</body>
</html>