Network Working Group                                            R. Bush
Internet-Draft                                 Internet Initiative Japan
Intended status: Standards Track                              R. Austein
Expires: July 5, 2012                               Dragon Research Labs
                                                                K. Patel
                                                           Cisco Systems
                                                              H. Gredler
                                                  Juniper Networks, Inc.
                                                         January 2, 2012


                   RPKI Router Implementation Report
                      draft-ymbk-rpki-rtr-impl-00

Abstract

   This document provides an implementation report for RPKI Router
   protocol as defined in [I-D.ietf-sidr-rpki-rtr].  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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 July 5, 2012.

Copyright Notice



Bush, et al.              Expires July 5, 2012                  [Page 1]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Implementation Forms . . . . . . . . . . . . . . . . . . . . .  3
   3.  Protocol PDUs  . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Protocol Sequence  . . . . . . . . . . . . . . . . . . . . . .  8
   5.  Protocol Transport . . . . . . . . . . . . . . . . . . . . . . 10
   6.  Error Codes  . . . . . . . . . . . . . . . . . . . . . . . . . 11
   7.  Incremental Updates Support  . . . . . . . . . . . . . . . . . 15
   8.  Session ID Support . . . . . . . . . . . . . . . . . . . . . . 15
   9.  Incremental Session Startup Support  . . . . . . . . . . . . . 15
   10. Interoperable Implementations  . . . . . . . . . . . . . . . . 16
   11. Cisco Implementation . . . . . . . . . . . . . . . . . . . . . 16
   12. Juniper Implementation . . . . . . . . . . . . . . . . . . . . 16
   13. rpki.net Implementation  . . . . . . . . . . . . . . . . . . . 16
   14. RIPE NCC Implementation  . . . . . . . . . . . . . . . . . . . 16
   15. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 17
   16. Security considerations  . . . . . . . . . . . . . . . . . . . 17
   17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
   18. Normative References . . . . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
















Bush, et al.              Expires July 5, 2012                  [Page 2]

Internet-Draft      RPKI Router Implementation Report       January 2012


1.  Introduction

   In order to formally validate the origin ASs of BGP announcements,
   routers need a simple but reliable mechanism to receive RPKI
   [I-D.ietf-sidr-rpki-rtr] prefix origin data from a trusted cache.
   The RPKI Router protocol defined in [I-D.ietf-sidr-rpki-rtr] 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 [I-D.ietf-sidr-rpki-rtr].

   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.


2.  Implementation Forms

   Contact and implementation information for person filling out this
   form:

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

   Name: Forhad Ahmed, Email: foarhad@cisco.com, Vendor: Cisco Systems,
   Inc. Release: IOS-XR

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

   Name: Rob Austein, Email: sra@hactrn.net, Vendor: rpki.net project,
   Release: N/A

   Name: Tim Bruijnzeels, Email: tim@ripe.net, Vendor: RIPE NCC Release:
   RIPE NCC validator-app 2.0.0 https://certification.ripe.net/content/
   public-repo/releases/net/ripe/rpki-validator/rpki-validator-app/
   2.0.0/rpki-validator-app-2.0.0-bin.zip


3.  Protocol PDUs

   Does the implementation support receive side functionality Sec.5.1.
   of [I-D.ietf-sidr-rpki-rtr] Serial Notify PDU?

   Cisco IOS: YES




Bush, et al.              Expires July 5, 2012                  [Page 3]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Cisco IOS-XR: YES

   Juniper JUNOS: YES

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support send side functionality for Sec.5.1.
   of [I-D.ietf-sidr-rpki-rtr] Serial Notify PDU?

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support receive side functionality for
   Sec.5.2. of [I-D.ietf-sidr-rpki-rtr] Serial Query PDU?

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support send side functionality for Sec.5.2.
   of [I-D.ietf-sidr-rpki-rtr] Serial Query PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support receive side functionality for



Bush, et al.              Expires July 5, 2012                  [Page 4]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Sec.5.3. of [I-D.ietf-sidr-rpki-rtr] Reset Query PDU?

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support send side functionality for Sec.5.3.
   of [I-D.ietf-sidr-rpki-rtr] Reset Query PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support receive side functionality for
   Sec.5.4. of [I-D.ietf-sidr-rpki-rtr] Cache Response PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support send side functionality for Sec.5.4.
   of [I-D.ietf-sidr-rpki-rtr] Cache Response PDU?

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES



Bush, et al.              Expires July 5, 2012                  [Page 5]

Internet-Draft      RPKI Router Implementation Report       January 2012


   RIPE: YES

   Does the implementation support receive side functionality for
   Sec.5.5. of [I-D.ietf-sidr-rpki-rtr] IPv4 Prefix PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support send side functionality for Sec.5.5.
   of [I-D.ietf-sidr-rpki-rtr] IPv4 Prefix PDU?

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support receive side functionality for
   Sec.5.6. of [I-D.ietf-sidr-rpki-rtr] IPv6 Prefix PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support send side functionality for Sec.5.6.
   of [I-D.ietf-sidr-rpki-rtr] IPv6 Prefix PDU?

   Cisco IOS: NO

   Cisco IOS-XR: NO




Bush, et al.              Expires July 5, 2012                  [Page 6]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support receive side functionality for
   Sec.5.7. of [I-D.ietf-sidr-rpki-rtr] End Of Data PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support send side functionality for Sec.5.7.
   of [I-D.ietf-sidr-rpki-rtr] End Of Data PDU?

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support receive side functionality for
   Sec.5.8. of [I-D.ietf-sidr-rpki-rtr] Cache Reset PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: UNIT TEST

   Does the implementation support send side functionality for Sec.5.8.
   of [I-D.ietf-sidr-rpki-rtr] Cache Reset PDU?




Bush, et al.              Expires July 5, 2012                  [Page 7]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support send side functionality for Sec.5.9.
   of [I-D.ietf-sidr-rpki-rtr] Error Report PDU?

   Cisco IOS: YES

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Does the implementation support receive side functionality for
   Sec.5.9. of [I-D.ietf-sidr-rpki-rtr] Error Report PDU?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO, Error PDU gets silently ignored

   rpki.net: YES

   RIPE: YES


4.  Protocol Sequence

   Does RPKI Router protocol implementation follow the four protocol
   sequences as outlined in Section 6 of [I-D.ietf-sidr-rpki-rtr]?

   Start or Restart Sequence

   Cisco IOS: YES

   Cisco IOS-XR: YES




Bush, et al.              Expires July 5, 2012                  [Page 8]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: YES

   Typical Exchange

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: NO, we always respond as described in 6.3

   Generation of Incremental Updates Sequence

   Cisco IOS: No

   Cisco IOS-XR: No

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: NO

   Receipt of Incremental Updates Sequence

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: NO

   Generation of Cache has No data Sequence

   Cisco IOS: NO

   Cisco IOS-XR: NO




Bush, et al.              Expires July 5, 2012                  [Page 9]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES


5.  Protocol Transport

   Does RPKI Router protocol implementation support different protocol
   transport mechanism outlined in Section 7 of
   [I-D.ietf-sidr-rpki-rtr]?

   SSH Transport

   Cisco IOS: NO

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: NO

   TLS Transport

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: NO

   RIPE: NO

   TCP Transport

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: YES



Bush, et al.              Expires July 5, 2012                 [Page 10]

Internet-Draft      RPKI Router Implementation Report       January 2012


   TCP-MD5 Transport

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS:NO

   rpki.net: NO

   RIPE: NO

   TCP-AO Transport

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS:NO

   rpki.net: NO

   RIPE: NO


6.  Error Codes

   Does RPKI Router protocol implementation support different protocol
   error codes outlined in Section 10 of [I-D.ietf-sidr-rpki-rtr]?

   Receiving Error Code 1

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Sending Error Code 1

   Cisco IOS: YES

   Cisco IOS-XR: YES




Bush, et al.              Expires July 5, 2012                 [Page 11]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Receiving Error Code 2

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: N/A

   Sending Error Code 2

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Receiving Error Code 3

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: N/A

   Sending Error Code 3

   Cisco IOS: NO

   Cisco IOS-XR: NO




Bush, et al.              Expires July 5, 2012                 [Page 12]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Juniper JUNOS: NO

   rpki.net: NO

   RIPE: YES

   Receiving Error Code 4

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Sending Error Code 4

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: NO

   RIPE: YES

   Receiving Error Code 5

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: YES

   RIPE: YES

   Sending Error Code 5

   Cisco IOS: YES

   Cisco IOS-XR: YES




Bush, et al.              Expires July 5, 2012                 [Page 13]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Juniper:

   rpki.net: NO

   RIPE: YES

   Receiving Error Code 6

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS: NO

   rpki.net: YES

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

   Sending Error Code 6

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: NO

   RIPE: N/A

   Receiving Error Code 7

   Cisco IOS: NO

   Cisco IOS-XR: No

   Juniper JUNOS: NO

   rpki.net: YES

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

   Sending Error Code 7

   Cisco IOS: YES




Bush, et al.              Expires July 5, 2012                 [Page 14]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Cisco IOS-XR: YES

   Juniper JUNOS: NO

   rpki.net: NO

   RIPE: N/A


7.  Incremental Updates Support

   RPKI Router protocol does support Incremental Updates defined in a
   section 4 of [I-D.ietf-sidr-rpki-rtr].

   Cisco IOS: NO

   Cisco IOS-XR: NO

   Juniper JUNOS:YES, (Receive side support)

   rpki.net: YES

   RIPE: NO


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
   proecedures outlined in Section 5.10 of [I-D.ietf-sidr-rpki-rtr]?

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: NO, using random, but will FIX


9.  Incremental Session Startup Support

   RPKI Router protocol does support Incremental session startups with
   Serial Number and Session ID defined in the protocol.  Does RPKI



Bush, et al.              Expires July 5, 2012                 [Page 15]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Router protocol implementation support Incremental Session Startup
   Support as defined in section 5.10 of [I-D.ietf-sidr-rpki-rtr].

   Cisco IOS: YES

   Cisco IOS-XR: YES

   Juniper JUNOS:YES

   rpki.net: YES

   RIPE: NO


10.  Interoperable Implementations

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


11.  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.


12.  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
   RIPEs RPKI Router Cache implementation.


13.  rpki.net Implementation

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


14.  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



Bush, et al.              Expires July 5, 2012                 [Page 16]

Internet-Draft      RPKI Router Implementation Report       January 2012


   testing our validator with JUNOS and Quagga.


15.  IANA Considerations

   This document makes no request of IANA.

   Note to RFC Editor: this section may be removed on publication as an
   RFC.


16.  Security considerations

   No new security issues are introduced to the RPKI Router protocol
   defined in [I-D.ietf-sidr-rpki-rtr].


17.  Acknowledgements

   TBD....


18.  Normative References

   [I-D.ietf-sidr-rpki-rtr]
              Bush, R. and R. Austein, "The RPKI/Router Protocol",
              draft-ietf-sidr-rpki-rtr-22 (work in progress),
              December 2011.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.


Authors' Addresses

   Randy Bush
   Internet Initiative Japan
   5147 Crystal Springs
   Bainbridge Island, Washington  98110
   US

   Phone:
   Fax:
   Email: randy@psg.com
   URI:






Bush, et al.              Expires July 5, 2012                 [Page 17]

Internet-Draft      RPKI Router Implementation Report       January 2012


   Rob Austein
   Dragon Research Labs


   Phone:
   Fax:
   Email: sra@hactrn.net
   URI:


   Keyur Patel
   Cisco Systems
   170 West Tasman Drive
   San Jose, CA  95134
   US

   Phone:
   Fax:
   Email: keyupate@cisco.com
   URI:


   Hannes Gredler
   Juniper Networks, Inc.
   1194 N. Mathilda Ave.
   Sunnyvale, CA  94089
   US

   Email: hannes@juniper.net






















Bush, et al.              Expires July 5, 2012                 [Page 18]