Resource Public Key Infrastructure (RPKI) Router Implementation Report

In order to formally validate the origin Autonomous Systems (ASes) of BGP announcements, routers need a simple but reliable mechanism to receive Resource Public Key Infrastructure (RPKI) prefix origin data from a trusted cache. The RPKI Router protocol defined in provides a mechanism to deliver validated prefix origin data to routers. This document provides an implementation report for the RPKI Router protocol as defined in RFC 6810. The authors did not verify the accuracy of the information provided by respondents or by any alternative means. The respondents are experts with the implementations they reported on, and their responses are considered authoritative for the implementations for which their responses represent. Respondents were asked to only use the "YES" answer if the feature had at least been tested in the lab.

Contact and implementation information for person filling out this form: Name: Keyur Patel Email: keyupate@cisco.com Vendor: Cisco Systems, Inc. Release: IOS Protocol Role: Client Name: Forhad Ahmed Email:foahmed@cisco.com Vendor: Cisco Systems, Inc. Release: IOS-XR Protocol Role: Client Name: Hannes Gredler Email: hannes@juniper.net Vendor: Juniper Networks, Inc. Release: JUNOS Protocol Role: Client Name: Rob Austein Email: sra@hactrn.net Vendor: rpki.net project Release: <http://subvert-rpki.hactrn.net/trunk/> Protocol Role: Client, Server Name: Tim Bruijnzeels Email: tim@ripe.net Vendor: RIPE NCC Release: RIPE NCC validator-app 2.0.0 <https://github.com/RIPE-NCC/rpki-validator> Protocol Role: Server Name: Fabian Holler, Matthias Waehlisch Email: waehlisch@ieee.org Vendor: HAW Hamburg, FU Berlin, RTRlib project Release: RTRlib 0.2 <http://rpki.realmv6.org/> Protocol Role: Client Name: David Mandelberg, Andrew Chi Email: dmandelb@bbn.com Vendor: Raytheon/BBN Technologies Release: RPSTIR 0.2 <http://sourceforge.net/projects/rpstir/> Protocol Role: Server

Does the implementation support Protocol Data Units (PDUs) as described in Section 5 of ? Serial Notify Serial Query Reset Query Cache Response IPv4 Prefix IPv6 Prefix End of Data Cache Reset Error Report IOS XR JUNOS rpki .net clnt rpki .net srvr NCC RTR- lib BBN Rcv.P0 YES YES YES YES --- --- YES --- Snd.P0 --- --- --- --- YES YES --- YES Rcv.P1 --- --- --- --- YES YES --- YES Snd.P1 YES YES YES YES --- --- YES --- Rcv.P2 --- --- --- --- YES YES --- YES Snd.P2 YES YES YES YES --- --- YES --- Rcv.P3 YES YES YES YES --- --- YES --- Snd.P3 --- --- --- --- YES YES --- YES Rcv.P4 YES YES YES YES --- --- YES --- Snd.P4 --- --- --- --- YES YES --- YES Rcv.P6 YES YES YES YES --- --- YES --- Snd.P6 --- --- --- --- YES YES --- YES Rcv.P7 YES YES YES YES --- --- YES --- Snd.P7 --- --- --- --- YES YES --- YES Rcv.P8 YES YES YES YES --- --- YES --- Snd.P8 --- --- --- --- YES YES --- YES Rcv.P10 YES YES NO~1 YES YES YES YES YES Snd.P10 YES NO NO YES YES YES YES YES No, Error PDU gets silently ignored.

Does the RPKI Router protocol implementation follow the four protocol sequences as outlined in Section 6 of ? Start or Restart Typical Exchange No Incremental Update Available Cache Has No Data Available IOS XR JUNOS rpki .net clnt rpki .net srvr NCC RTRlib BBN S1 YES YES YES YES YES YES YES YES S2 YES YES YES YES YES NO~1 YES YES S3 YES YES YES YES YES YES YES YES S4 YES YES YES YES YES YES YES YES~2 Does not implement Serial Query, thus Incremental Update is never available, so responds to Serial Query with Cache Reset as described in Section 6.3 of Sends Cache Reset in response to Serial Query when no data; sends Error Report PDU in response to Reset Query when no data.

Does the RPKI Router protocol implementation support the different protocol transport mechanisms outlined in Section 7 of ? IOS XR JUNOS rpki .net clnt rpki .net srvr NCC RTRlib BBN SSH NO YES NO YES YES NO YES YES TLS NO NO NO NO NO NO NO NO TCP YES YES YES YES YES YES YES YES TCP-MD5 NO NO NO NO NO NO NO NO TCP-AO NO NO NO NO NO NO NO NO IPsec NO NO NO NO NO NO NO NO

Does the RPKI Router protocol implementation support the different protocol error codes outlined in Section 10 of ? IOS XR JUNOS rpki .net clnt rpki .net srvr NCC RTRlib BBN Rcv.0 YES YES NO YES YES YES YES YES Snd.0 YES YES NO YES YES YES YES YES Rcv.1 YES YES NO YES YES YES YES YES Snd.1 YES YES NO YES YES YES YES YES Rcv.2 YES YES NO YES --- --- YES --- Snd.2 --- --- ------ YES YES --- YES Rcv.3 YES YES NO YES --- --- YES --- Snd.3 --- --- ------ YES YES --- YES Rcv.4 YES YES NO YES YES YES YES YES Snd.4 YES YES NO YES YES YES YES YES Rcv.5 YES YES NO YES YES YES YES YES Snd.5 YES YES NO YES YES YES YES YES Rcv.6 --- --- ------ YES YES~1 --- YES Snd.6 YES YES NO NO --- --- YES --- Rcv.7 --- --- ------ YES YES~1 --- YES Snd.7 YES YES NO NO --- --- YES --- YES, but... fatal, so connection is dropped, but cache does not conclude it's inconsistent.

Does the RPKI Router implementation support Incremental Updates as defined in Section 4 of ? IOS XR JUNOS rpki.net clnt rpki.net srvr NCC RTRlib BBN NO NO YES YES YES NO YES YES

Session ID is used to indicate that the cache server may have restarted and that the incremental restart may not be possible. Does the RPKI Router protocol implementation support the Session ID procedures outlined in Section 5.1 of ? IOS XR JUNOS rpki.net clnt rpki.net srvr NCC RTRlib BBN YES YES YES YES YES NO~1 YES YES NO, using random, but will FIX

Does the RPKI Router protocol implementation support Incremental session startups with Serial Number and Session ID as defined in Section 5.3 of ? IOS XR JUNOS rpki.net clnt rpki.net srvr NCC RTRlib BBN YES YES YES YES YES NO YES YES

List other implementations with which you have tested the interoperability of the RPKI Router implementation.

Cisco: The Cisco IOS and IOS-XR implementation should be interoperable with other vendor RPKI Router Protocol implementations. In particular, we have tested our interoperability with rpki.net's RPKI Router implementation.

Juniper: The Juniper Networks, Inc. JUNOS implementation should be interoperable with other vendor RPKI Router Protocol implementations. In particular, we have tested our interoperability with rpki.net's and NCC's RPKI Router Cache implementation.

rpki.net: The rpki.net implementation should operate with other rpki-rtr implementations. In particular, we have tested our rpki-rtr server's interoperability with Cisco IOS, Cisco IOS-XR, and Juniper.

RIPE NCC: The RIPE NCC validator has been tested by us with other rpki-rtr implementations. In particular, we have tested with RTRlib and CISCO IOS. We received positive feedback from close contacts who tested our validator with JUNOS and Quagga.

RTRlib: The RTRlib has been tested by us with other rpki-rtr implementations. In particular, we have tested with rtr-origin from rpki.net and RIPE NCC Validator.

BBN RPSTIR: We have not yet tested with any other implementations.

No new security issues are introduced to the RPKI Router protocol defined in .

The authors would like to thank Andrew Chi, David Mandelberg, Fabian Holler, Forhad Ahmed, and Tim Bruijnzeels for their contributions to this document.