[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 draft-ietf-sidr-rpki-rtr-impl

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


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

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.  Respondents were asked to only use the YES answer if the
   feature had at least been tested in the lab.

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




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

Internet-Draft      RPKI Router Implementation Report       January 2012


   This Internet-Draft will expire on July 11, 2012.

Copyright Notice

   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.



































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

Internet-Draft      RPKI Router Implementation Report       January 2012


Table of Contents

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




























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

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

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

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

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

   NCC  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

   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/






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

Internet-Draft      RPKI Router Implementation Report       January 2012


   BBN  Name: David Mandelberg, Email: dmandelb@bbn.com, Vendor:
      Raytheon/BBN Technologies, Release: RPSTIR 0.2
      http://sourceforge.net/projects/rpstir/


3.  Protocol Data Units

   Does the implementation support Protocol Data Units (PDUs) as
   described in Section 5 of [I-D.ietf-sidr-rpki-rtr]?

   +-----------+-----+-----+-------+--------+--------+--------+--------+
   |           | IOS |  XR | JUNOS |  rpki  |   NCC  |  RTR-  |   BBN  |
   |           |     |     |       |  .net  |        |   lib  |        |
   +-----------+-----+-----+-------+--------+--------+--------+--------+
   | Rcv.      | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | Serial    |     |     |       |        |  TEST  |        |  TEST  |
   | Notify    |     |     |       |        |        |        |        |
   | Snd.      |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | Serial    |     |     |       |        |        |        |        |
   | Notify    |     |     |       |        |        |        |        |
   | Rcv.      |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | Serial    |     |     |       |        |        |        |        |
   | Query     |     |     |       |        |        |        |        |
   | Snd.      | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | Serial    |     |     |       |        |  TEST  |        |  TEST  |
   | Query     |     |     |       |        |        |        |        |
   | Rcv.      |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | Reset     |     |     |       |        |        |        |        |
   | Query     |     |     |       |        |        |        |        |
   | Snd.      | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | Reset     |     |     |       |        |  TEST  |        |  TEST  |
   | Query     |     |     |       |        |        |        |        |
   | Rcv.      | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | Cache     |     |     |       |        |  TEST  |        |  TEST  |
   | Resp.     |     |     |       |        |        |        |        |
   | Snd.      |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | Cache     |     |     |       |        |        |        |        |
   | Resp.     |     |     |       |        |        |        |        |
   | Rcv. IPv4 | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | Prefix    |     |     |       |        |  TEST  |        |  TEST  |
   | Snd. IPv4 |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | Prefix    |     |     |       |        |        |        |        |
   | Rcv. IPv6 | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | Prefix    |     |     |       |        |  TEST  |        |  TEST  |
   | Snd. IPv6 |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | Prefix    |     |     |       |        |        |        |        |
   | Rcv. End  | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | of Data   |     |     |       |        |  TEST  |        |  TEST  |



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

Internet-Draft      RPKI Router Implementation Report       January 2012


   | Snd. End  |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | of Data   |     |     |       |        |        |        |        |
   | Rcv.      | YES | YES |  YES  |   YES  |  UNIT  |   YES  |   SYS  |
   | Cache     |     |     |       |        |  TEST  |        |  TEST  |
   | Reset     |     |     |       |        |        |        |        |
   | Snd.      |  NO |  NO |   NO  |   YES  |   YES  |   NO   |   YES  |
   | Cache     |     |     |       |        |        |        |        |
   | Reset     |     |     |       |        |        |        |        |
   | Rcv.      | YES | YES |  NO~1 |   YES  |   YES  |   YES  |   YES  |
   | Error     |     |     |       |        |        |        |        |
   | Report    |     |     |       |        |        |        |        |
   | Snd.      | YES |  NO |   NO  |   YES  |   YES  |   YES  |   YES  |
   | Error     |     |     |       |        |        |        |        |
   | Report    |     |     |       |        |        |        |        |
   +-----------+-----+-----+-------+--------+--------+--------+--------+

   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 [I-D.ietf-sidr-rpki-rtr]?

   S1:  Start or Restart

   S2:  Typical Exchange

   S3:  Generation of Incremental Updates Sequence

   S4:  Receipt of Incremental Updates Sequence

   S5:  Generation of Cache has No data Sequence

        +----+-----+-----+-------+----------+------+--------+-----+
        |    | IOS |  XR | JUNOS | rpki.net |  NCC | RTRlib | BBN |
        +----+-----+-----+-------+----------+------+--------+-----+
        | S1 | YES | YES |  YES  |    YES   |  YES |   YES  | YES |
        | S2 | YES | YES |  YES  |    YES   | NO~1 |   YES  | YES |
        | S3 |  NO |  NO |   NO  |    YES   |  NO  |   YES  | YES |
        | S4 | YES | YES |  YES  |    YES   |  NO  |   YES  |  NO |
        | S5 |  NO |  NO |   NO  |    YES   |  YES |   YES  | YES |
        +----+-----+-----+-------+----------+------+--------+-----+

   1) NO, we always respond as described in 6.3 of
   [I-D.ietf-sidr-rpki-rtr]





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

Internet-Draft      RPKI Router Implementation Report       January 2012


5.  Protocol Transport

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

     +---------+-----+-----+-------+----------+-----+--------+-------+
     |         | IOS |  XR | JUNOS | rpki.net | NCC | RTRlib |  BBN  |
     +---------+-----+-----+-------+----------+-----+--------+-------+
     | SSH     |  NO | YES |   NO  |    YES   |  NO |   YES  | YES~1 |
     | TLS     |  NO |  NO |   NO  |    YES   |  NO |   NO   | YES~2 |
     | TCP     | YES | YES |  YES  |    YES   | YES |   YES  |  YES  |
     | TCP-MD5 |  NO |  NO |   NO  |    NO    |  NO |   NO   |   NO  |
     | TCP-AO  |  NO |  NO |   NO  |    NO    |  NO |   NO   |   NO  |
     +---------+-----+-----+-------+----------+-----+--------+-------+

   1) Yes, using netcat as the ssh subsystem to connect to the RTR
   server on localhost via TCP.  This is currently untested.

   2) Yes, using stunnel to verify client certificates and forward
   traffic to the server on localhost via TCP.  This is currently
   untested.


6.  Error Codes

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























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

Internet-Draft      RPKI Router Implementation Report       January 2012


   +-------+-----+-----+-------+----------+-------+--------+----------+
   |       | IOS |  XR | JUNOS | rpki.net |  NCC  | RTRlib |    BBN   |
   +-------+-----+-----+-------+----------+-------+--------+----------+
   | Rcv.0 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Snd.0 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Rcv.1 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Snd.1 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Rcv.2 | YES | YES |   NO  |    YES   |  N/A  |   YES  |    YES   |
   | Snd.2 | YES | YES |   NO  |    YES   |  YES  |   N/A  |    YES   |
   | Rcv.3 | YES | YES |   NO  |    YES   |  N/A  |   YES  |    YES   |
   | Snd.3 |  NO |  NO |   NO  |    YES   |  YES  |   NO   |    YES   |
   | Rcv.4 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Snd.4 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Rcv.5 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Snd.5 | YES | YES |   NO  |    YES   |  YES  |   YES  |    YES   |
   | Rcv.6 |  NO |  NO |   NO  |    YES   | YES~1 |   N/A  |    YES   |
   | Snd.6 | YES | YES |   NO  |    NO    |  N/A  |   YES  | SYS TEST |
   | Rcv.7 |  NO |  NO |   NO  |    YES   | YES~1 |   N/A  |    YES   |
   | Snd.7 | YES | YES |   NO  |    NO    |  N/A  |   YES  | SYS TEST |
   +-------+-----+-----+-------+----------+-------+--------+----------+

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


7.  Incremental Updates Support

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

           +-----+----+-------+----------+-----+--------+-----+
           | IOS | XR | JUNOS | rpki.net | NCC | RTRlib | BBN |
           +-----+----+-------+----------+-----+--------+-----+
           |  NO | NO | YES~1 |    YES   |  NO |   YES  | YES |
           +-----+----+-------+----------+-----+--------+-----+

   1) YES, receive side support


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.10 of [I-D.ietf-sidr-rpki-rtr]?





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

Internet-Draft      RPKI Router Implementation Report       January 2012


          +-----+-----+-------+----------+------+--------+-----+
          | IOS |  XR | JUNOS | rpki.net |  NCC | RTRlib | BBN |
          +-----+-----+-------+----------+------+--------+-----+
          | YES | YES |  YES  |    YES   | NO~1 |   YES  | YES |
          +-----+-----+-------+----------+------+--------+-----+

   1) 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
   Router protocol implementation support Incremental Session Startup
   Support as defined in section 5.4 of [I-D.ietf-sidr-rpki-rtr].

           +-----+-----+-------+----------+-----+--------+-----+
           | IOS |  XR | JUNOS | rpki.net | NCC | RTRlib | BBN |
           +-----+-----+-------+----------+-----+--------+-----+
           | YES | YES |  YES  |    YES   |  NO |   YES  | YES |
           +-----+-----+-------+----------+-----+--------+-----+


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
   NCCs 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
   interoperability with Cisco IOS, Cisco IOS-XR, and Juniper.




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

Internet-Draft      RPKI Router Implementation Report       January 2012


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: this section may be removed on publication as an
   RFC.


12.  Security considerations

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


13.  Acknowledgements

   TBD....


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





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

Internet-Draft      RPKI Router Implementation Report       January 2012


Authors' Addresses

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

   Email: randy@psg.com


   Rob Austein
   Dragon Research Labs

   Email: sra@hactrn.net


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

   Email: keyupate@cisco.com


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

   Email: hannes@juniper.net


   Matthias Waehlisch
   FU Berlin
   Takustr. 9
   Berlin  14195
   Germany

   Email: waehlisch@ieee.org
   URI:   http://www.inf.fu-berlin.de/~waehl








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


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/