[arin-ppml] Revisit RPKI TAL Relying Party Agreement?

Richard J. Letts rjletts at uw.edu
Fri Feb 3 14:46:42 EST 2017

From: ARIN-PPML [mailto:arin-ppml-bounces at arin.net] On Behalf Of William Herrin
> Sent: Friday, February 3, 2017 9:29 AM
> Exactly. You refuse to provide new services related to legacy resource
> holdings, including RPKI. While not unreasonable in the context of ARIN
> operations, this is harmful to the RPKI efforts. This is something no
> organization prioritizing RPKI would do. Since offering new services like RPKI
> to legacy registrants* appears inimical to ARIN's core mission I respectfully
> question whether ARIN can be a satisfactory steward for RPKI.

RIPE's Policy is:
The resource certificate is linked to RIPE NCC registration. This is because only for as long as you are a RIPE NCC member and *have a contractual relationship with the RIPE NCC* can it be authoritatively stated who the holder of a certain Internet number resource is. 

 [Emphasis mine]

It doesn't seem to that different from what I understand ARIN's policy is.

More information about the ARIN-PPML mailing list