[187537] in North American Network Operators' Group
Re: Change re ARIN RPKI Relying Party TAL access
daemon@ATHENA.MIT.EDU (John Curran)
Sat Feb 6 04:15:44 2016
X-Original-To: nanog@nanog.org
From: John Curran <jcurran@arin.net>
To: Job Snijders <job@instituut.net>
Date: Fri, 5 Feb 2016 18:27:57 +0000
In-Reply-To: <20160205164432.GI1192@57.rev.meerval.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Feb 5, 2016, at 8:44 AM, Job Snijders <job@instituut.net> wrote:
>=20
> Dear John,
>=20
> On Thu, Feb 04, 2016 at 08:15:29PM +0000, John Curran wrote:
>> One of the concerns raised at a previous NANOG was with respect to the
>> need for an RPKI relying parties to explicitly accept ARIN's relying
>> party agreement (RPA) - note that this has now been changed (per the
>> attached announcement)
>>=20
>> Wile the RPA terms remain the same, it is no longer necessary to
>> click-accept and provide an email in order to access ARIN's trust
>> anchor locator (TAL).
>=20
> Can you explain in layman terms what the legal consequences of this
> change are?
Job -=20
=20
As I noted, the Relying Party Agreement terms and conditions remain
the same - we have simply eliminated the requirement for explicit=20
agreement to it thru entry of your email and click-to-accept. We do=20
not expect there is any legal consequences for relying parties as result=
=20
of this change [1], only a question of convenience of access to the TAL
as sought by the community.
Thanks!
/John
John Curran
President and CEO
ARIN
[1] The world of assenting to agreement terms is an interesting legal
topic, and others may argue that changing from click-to-accept to=20
binding by usage is material; such is the nature of legal matters.
