RPKI Router Implementation Report
draft-ietf-sidr-rpki-rtr-impl-05

Abstract

This document is an implementation report for the RPKI Router protocol as defined in [RFC6810]. The editor did not verify the accuracy of the information provided by respondents. 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.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on June 15, 2014.

Copyright Notice

Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Implementation Forms
• 3. Protocol Data Units
• 4. Protocol Sequence
• 5. Protocol Transport
• 6. Error Codes
• 7. Incremental Updates Support
• 8. Session ID Support
• 9. Incremental Session Startup Support
• 10. Interoperable Implementations
• 10.1. Cisco Implementation
• 10.2. Juniper Implementation
• 10.3. rpki.net Implementation
• 10.4. RIPE NCC Implementation
• 10.5. RTRlib Implementation
• 10.6. BBN RPSTIR Implementation
• 11. IANA Considerations
• 12. Security considerations
• 13. Acknowledgements
• 14. Normative References
• Authors' Addresses

1. Introduction

In order to formally validate the origin Autonomous Systems (ASs) of BGP announcements, routers need a simple but reliable mechanism to receive Resource Public Key Infrastructure (RPKI) [RFC6810] prefix origin data from a trusted cache. The RPKI Router protocol defined in [RFC6810] 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 [RFC6810].

The editor 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.

2. Implementation Forms

Contact and implementation information for person filling out this form:

IOS

Name: Keyur Patel
Email: keyupate@cisco.com
Vendor: Cisco Systems, Inc.
Release: IOS
Protocol Role: Client

XR

Name: Forhad Ahmed
Email:foahmed@cisco.com
Vendor: Cisco Systems, Inc.
Release: IOS-XR
Protocol Role: Client

JUNOS

Name: Hannes Gredler
Email: hannes@juniper.net
Vendor: Juniper Networks, Inc.
Release: JUNOS
Protocol Role: Client

rpki.net

Name: Rob Austein
Email: sra@hactrn.net
Vendor: rpki.net project
Release: http://subvert-rpki.hactrn.net/trunk/
Protocol Role: Client, Server

NCC

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

RTRlib

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

BBN

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

3. Protocol Data Units

Does the implementation support Protocol Data Units (PDUs) as described in Section 5 of [RFC6810]?

P0:

Serial Notify

P1:

Serial Query

P2:

Reset Query

P3:

Cache Response

P4:

IPv4 Prefix

P6:

IPv6 Prefix

P7:

End of Data

P8:

Cache Reset

P10:

Error Report

Note 1:

No, Error PDU gets silently ignored.

4. Protocol Sequence

Does RPKI Router protocol implementation follow the four protocol sequences as outlined in Section 6 of [RFC6810]?

S1:

Start or Restart

S2:

Typical Exchange

S3:

No Incremental Update Available

S4:

Cache Has No Data Available

Note 1:

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 [RFC6810]

Note 2:

Sends Cache Reset in response to Serial Query when no data; sends Error Report PDU in response to Reset Query when no data.

5. Protocol Transport

Does RPKI Router protocol implementation support different protocol transport mechanism outlined in Section 7 of [RFC6810]?

6. Error Codes

Does RPKI Router protocol implementation support different protocol error codes outlined in Section 10 of [RFC6810]?

Note 1:

YES, but... fatal, so connection is dropped, but cache does not conclude it's inconsistent.

7. Incremental Updates Support

Does the RPKI Router implementation support Incremental Updates as defined in Section 4 of [RFC6810]?

8. Session ID Support

Session ID is used to indicate that the cache server may have restarted and that the incremental restart may not be possible.

Does RPKI Router protocol implementation support Session ID procedures outlined in Section 5.1 of [RFC6810]?

Note 1:

NO, using random, but will FIX

9. Incremental Session Startup Support

Does the RPKI Router protocol implementation support Incremental session startups with Serial Number and Session ID as defined in section 5.3 of [RFC6810]?

10. Interoperable Implementations

List other implementations that you have tested interoperability of RPKI Router Implementation.

10.1. Cisco 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.

10.2. Juniper 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.

10.3. rpki.net 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.

10.4. RIPE NCC Implementation

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 testing our validator with JUNOS and Quagga.

10.5. RTRlib Implementation

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.

10.6. BBN RPSTIR Implementation

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

11. IANA Considerations

This document makes no request of IANA.

Note to RFC Editor: The IANA has requested that this section remain in the document upon publication as an RFC. This note to the RFC Editor, however, may be removed.

12. Security considerations

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

13. Acknowledgements

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

14. Normative References

Authors' Addresses