<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;"><br><div><br><blockquote type="cite"><div>On Oct 31, 2022, at 20:13, David Farmer <farmer@umn.edu> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 31, 2022 at 9:47 PM Owen DeLong <<a href="mailto:owen@delong.com">owen@delong.com</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><div><div><br></div>While it’s true that ARIN does not make the authenticated IRR or RPKI available to legacy holders without a contract, those that care</div><div>to publish the information are free to do any of the following:</div><div><span style="white-space:pre-wrap"> </span>+<span style="white-space:pre-wrap"> </span>Transfer their legacy resources to RIPE and publish RPKI there</div><div><span style="white-space:pre-wrap"> </span>+<span style="white-space:pre-wrap"> </span>Use ALT-DB or another IRR to publish their RPSL statements</div></div></blockquote><div><br></div><div>Transferring your resources to RIPE will either require a contract with RIPE if you wish to become an LIR or a contract with a sponsoring LIR. So, you are probably not doing RPKI without some kind of contract. You may have some choices on who you contract with, but I see a contract in your future if you want to do RPKI.</div></div></div></div></blockquote><div><br></div>Guess again. For a legacy holder, you can transfer to RIPE as “legacy without contract” and retain your legacy status with no contract whatsoever.</div><div><br></div><div>I’ve done it. It got me out of the fee hikes and double-charging that were imposed as a result of the ARIN board’s fee-asco long ago.</div><div><br><blockquote type="cite"><div><div dir="ltr"><div class="gmail_quote"><div>As for ALT-DB that could be an option. However, if content providers start requiring authenticated IRR information, which is being at least talked about, then ALT-DB might only be a short-term option.</div></div></div></div></blockquote><div><br></div>I’m sure that if that becomes the case, someone will produce something like ALT-DB with authentication.</div><div> <br><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>I will admit that during the original debate, I opposed the creation of this field expecting that it would end up exactly where it is now. Of limited</div><div>use and even less accuracy.</div><div><br></div><div>IMHO, it’s well past time to recognize this as a failed experiment and clean up after it.</div></div></blockquote><div><br></div><div>The experiment was not a failure, but we have better options now, so I agree it's time for it to go.</div></div></div></blockquote><div><br></div>It certainly wasn’t anything I would call a success. It was never well populated, never terribly accurate, and never widely used.</div><div><br></div><div>Owen</div><div><br></div><br></body></html>