Towards a Rigorous Methodology for Measuring Adoption of RPKI Route Validation and Filtering

A proposal to improve routing security---Route Origin Authorization (ROA)---has been standardized. A ROA specifies which network is allowed to announce a set of Internet destinations. While some networks now specify ROAs, little is known about whether other networks check routes they receive against these ROAs, a process known as Route Origin Validation (ROV). Which networks blindly accept invalid routes? Which reject them outright? Which de-preference them if alternatives exist? Recent analysis attempts to use uncontrolled experiments to characterize ROV adoption by comparing valid routes and invalid routes. However, we argue that gaining a solid understanding of ROV adoption is impossible using currently available data sets and techniques. Instead, we devise a verifiable methodology of controlled experiments for measuring ROV. Our measurements suggest that, although some ISPs are not observed using invalid routes in uncontrolled experiments, they are actually using different routes for (non-security) traffic engineering purposes, without performing ROV. We conclude with presenting three AS that do implement ROV as confirmed by the operators.

[1]  Yakov Rekhter,et al.  A Border Gateway Protocol 4 (BGP-4) , 1994, RFC.

[2]  Matthew Roughan,et al.  BGP beacons , 2003, IMC '03.

[3]  Susan Hares,et al.  A Border Gateway Protocol 4 (BGP-4) , 1994, RFC.

[4]  Walter Willinger,et al.  In search of the elusive ground truth: the internet's as-level connectivity structure , 2008, SIGMETRICS '08.

[5]  Thomas E. Anderson,et al.  Reverse traceroute , 2010, NSDI.

[6]  Walter Willinger,et al.  10 Lessons from 10 Years of Measuring and Modeling the Internet's Autonomous Systems , 2011, IEEE Journal on Selected Areas in Communications.

[7]  T. Schmidt,et al.  Towards detecting BGP route hijacking using the RPKI , 2012, CCRV.

[8]  Olaf Maennel,et al.  Towards a Framework for Evaluating BGP Security , 2012, CSET.

[9]  Stephen T. Kent,et al.  An Infrastructure to Support Secure Internet Routing , 2012, RFC.

[10]  Ítalo S. Cunha,et al.  PoiRoot: investigating the root cause of interdomain path changes , 2013, SIGCOMM.

[11]  John G. Scudder,et al.  BGP Prefix Origin Validation , 2013, RFC.

[12]  S. Goldberg Why Is It Taking So Long to Secure Internet Routing? , 2014 .

[13]  From the Consent of the Routed: Improving the Transparency of the RPKI , 2014 .

[14]  Randy Bush,et al.  Resource Public Key Infrastructure (RPKI) Router Implementation Report , 2014, RFC.

[15]  Sharon Goldberg,et al.  Why is it taking so long to secure internet routing? , 2014, Commun. ACM.

[16]  Ítalo S. Cunha,et al.  PEERING: An AS for Us , 2014, HotNets.

[17]  Ítalo S. Cunha,et al.  Investigating Interdomain Routing Policies in the Wild , 2015, Internet Measurement Conference.

[18]  Olaf Maennel,et al.  RiPKI: The Tragic Story of RPKI Deployment in the Web Ecosystem , 2014, HotNets.

[19]  Randy Bush,et al.  Measuring BGP Route Origin Registration and Validation , 2015, PAM.

[20]  Amir Herzberg,et al.  Are We There Yet? On RPKI's Deployment and Security , 2017, NDSS.

[21]  Job Snijders,et al.  The Use of Maxlength in the RPKI , 2018 .

[22]  Ítalo S. Cunha,et al.  Towards a Rigorous Methodology for Measuring Adoption of RPKI Route Validation and Filtering , 2018, ANRW.