Owen DeLong via NANOG <nanog@nanog.org> wrote:
The double billing (had it been present at the time) would have prevented me from signing the LRSA for my IPv4 resources.
Owen, the root of your problem is that you signed an LRSA with ARIN, rather than keeping your legacy resources un-tainted by an ARIN contract that deliberately reduced your rights. When ARDC transferred 44.192/10 via ARIN, the recipient lost the legacy status of the address block. That was an ARIN requirement, which was OK with that particular recipient. However, ARIN is not your only option. It is possible to transfer legacy resources such as IPv4 address blocks from ARIN to RIPE, having them be recognized as legacy blocks under RIPE jurisdiction. You can do this without signing any long term contract with RIPE, if you like; or you can choose to become a long-term paying RIPE member, under their fee schedule. All you need is to have any Internet resources in Europe -- like a virtual machine in a data center there, or a DNS server. I'm sure of this because I have done it; see https://apps.db.ripe.net/db-web-ui/lookup?source=ripe&key=209.16.159.0%20-%20209.16.159.255&type=inetnum The short-term contract for the transfer honors and retains the legacy status of those resources: that you own them, not the ARIN fiction that an RIR now controls them and will steal them from you if you stop paying them annually. Randy Bush detailed a similar transfer process back in 2016: https://archive.psg.com/160524.ripe-transfer.pdf The process is more bureaucratic and cumbersome than you expect; Europeans named bureacracy in the 1800s, and RIPE has raised it to a painful art. But once it's done, you are out from under the ARIN anti-legacy mentality forever. John Gilmore PS: If you want RPKI, which I didn't, you can sign a RIPE long term contract, pay them annually, and (according to Randy) they will STILL honor your ownership of your resources, unlike ARIN.