ARIN's RPKI Relying agreement

Thu Dec 4 18:47:48 UTC 2014

On 12/4/14, 1:13 PM, "John Curran" <jcurran at arin.net> wrote:

>>>I am happy to champion the change that you seek (i.e. will get it
>>>reviewed
>>> by legal and brought before the ARIN Board) but still need clarity on
>>>what
>>> change you wish to occur -
>>>
>>>    A) Implicit binding to the indemnification/warrant disclaimer
>>>clauses
>>>       (as done by the other RIRs)
>>>
>>>    B) Removal of the indemnification & warranty disclaimer clause
>>>
>>> I asked this directly during your NANOG presentation, but you did not
>>>respond
>>> either way.

WG] I deferred because I am not a lawyer and am not empowered to speak
anything more than my opinion on the matter. I believe that the more
useful response to your question came during the ARIN members' meeting
post-NANOG, where Rob Seastrom suggested at the mic that rather than a
bunch of engineers and policy wonks playing armchair lawyer and guessing
at what will make the actual lawyers happy, that we should organize a
separate meeting involving:
- the ARIN board
- ARIN legal counsel and other relevant ARIN staff
- legal representatives from as many of the operators and others
expressing concern over this as appropriate,
- along with a few of the technical folks to help deal with the
interaction between the technical and the legal

and use it to discuss the issues in order to come up with something
better.

>(One can easily argue that best practices require multiple connections
>or service providers, but that is the same with best practices for RPKI
>use requiring proper preferences to issues with certification data...)

WG]  So how would I as an ARIN member go about getting a redundant RPKI
provider? I'm uncomfortable being single-homed to ARIN since that seems
contrary to best practices.

Also: Most SPs provide an SLA to their customers that serves as a balance
to contractual liability weasel words.

Wes

Anything below this line has been added by my company’s mail server, I
have no control over it.
-----------

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.