Max Emig via address-policy-wg wrote on 30/10/2025 15:17:
a large Tier 1 carrier in the ARIN region did not update the ARIN Whois
in 20 years and did not offer RPKI ROA until very recently over legal
concerns and maintained their own whois along with the non-authoritative
RADB.
Max,
ARIN declined to provide services to legacy holders unless they signed
the LRSA, which many organisations objected to. The RIPE NCC is not in
the same situation.
I would like to avoid any situations where organisations would have to
choose between RIPE DB accuracy and routing security using RPKI ROA and
legal-risks regarding out-of-region use among other concerns.
In relation to RPKI, it is not possible to legally attest to the
registration of a number resource unless the number resource holder has
formally identified themselves to the RIPE NCC, i.e. unless there's a
legal agreement in place. In other words, if the Legacy holder doesn't
have a contractual relationship with the RIPE NCC, then they don't have
RPKI.
Can you explain why this would impact transfers? I don't follow your
argument.
Nick
-----
To unsubscribe from this mailing list or change your subscription options,
please visit:
https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
