It would be helpful if ROAs were allowed for legacy prefixes, without having to sign an RSA or other agreement w/ARIN. I have a /24 ("class C" from the 90's) that I route. I have hesitant to start pay for something I got for free. I think many organizations that were on the early Internet are also in a similar position.
We're in the same boat. We have two /24 (/23) that we advertise through our ISP(s) and we've been hesitant to sign an LSA/RSA because it seems to put us in a position where we may be held to standard and fees that we weren't previously held to.
If there was an easy and straightforward path to onboarding that would go a long way, but every time we look into it the process seems convoluted and unclear with too many options and potential foot guns.
Yep, I have also looked into it and agree it is confusing. I own this /24 as an individual and use it for hobbyist purposes, so try to keep expenses to a minimum. I got my ASN through a RIPE LIR, so it is separate from my ARIN legacy account. My understanding is I could transfer the /24 to RIPE but haven't looked into that much.
How hard/cumbersome is it for a individual/small group to implement RPKI for their ASN? I'm guessing it would involve some sort of collaboration with your LIR?
https://news.ycombinator.com/item?id=40487419