[no subject]

  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