[arin-ppml] RPKI Relying Agreement

John Curran jcurran at arin.net
Thu Dec 4 13:53:41 EST 2014


On Dec 4, 2014, at 1:12 PM, William Herrin <bill at herrin.us<mailto:bill at herrin.us>> wrote:

On Thu, Dec 4, 2014 at 10:59 AM, John Curran <jcurran at arin.net<mailto:jcurran at arin.net>> wrote:
> Actually, the terms regarding indemnification and warrant disclaimer are nearly
> identical to that contained in the other RIR's RPKI agreements; are those also
> problematic, or is the difficultly that principally that ARIN agreeing to the
> terms explicit rather than implicit?

Hi John,

I've seen a lot of hand waving, but I still have no clue how the publication of RPKI data places ARIN at a different risk than publication of registration data via whois.

Bill -

  Parties are likely to use RPKI services such that (as someone put
  it recently) - "routing decisions are affected and breakage happens”

  While such impacts could happen with whois, parties would have to
  create the linkages themselves, whereas with RPKI it is recognized
  that the system is designed to provide information for influencing of
  routing decisions (a major difference, and one that a judge could be
  made to recognize if some service provider has a prolonged outage
  due to their own self-inflicted Whois data wrangling into routing filters.)

  Given the nature of RPKI, it is clear that ARIN needs to engineer the
  service with full awareness of the potential risks (even though such
  risks are predominantly the result of parties using RPKI data without
  appropriate best practices.)   We have no problem offering a highly-
  reliable service; the risk of concern stems from third-parties who suffer
  major damages and want to assert that it was the result of an ISP’s
  misusage of ARIN’s RPKI service or ARIN’s RPKI service itself, even
  if the underlying cause in truth was completely unrelated to ARIN’s
  RPKI services.  Recognize that large harmed parties tend to litigate
  everyone, with the innocent parties extracting themselves only after
  lengthy battles, and such battles are very difficult when it comes to
  proving the proper state of technical service at a given point in time.

  I hope this helps in outlining some of the significant differences.

/John

John Curran
President and CEO
ARIN





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20141204/d8a418e8/attachment-0001.html>


More information about the ARIN-PPML mailing list