datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

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

Active Internet-Draft (sidr WG)
Document Stream: IETF
Last updated: 2013-03-11
Replaces: draft-ymbk-rpki-rtr-impl
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: Waiting for WG Chair Go-Ahead (sidr)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                            R. Bush
Internet-Draft                                 Internet Initiative Japan
Intended status: Informational                                R. Austein
Expires: September 12, 2013                         Dragon Research Labs
                                                                K. Patel
                                                           Cisco Systems
                                                              H. Gredler
                                                  Juniper Networks, Inc.
                                                            M. Waehlisch
                                                               FU Berlin
                                                          March 11, 2013

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

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
   be interpreted as described in RFC 2119 [RFC2119] only when they
   appear in all upper case.  They may also appear in lower or mixed
   case as English words, without normative meaning.

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 September 12, 2013               [Page 1]
Internet-Draft     RPKI Router Implementation Report          March 2013

   This Internet-Draft will expire on September 12, 2013.

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
   2.  Implementation Forms  . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Data Units . . . . . . . . . . . . . . . . . . . . .   3
   4.  Protocol Sequence . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Protocol Transport  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Error Codes . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Incremental Updates Support . . . . . . . . . . . . . . . . .   6
   8.  Session ID Support  . . . . . . . . . . . . . . . . . . . . .   6
   9.  Incremental Session Startup Support . . . . . . . . . . . . .   7
   10. Interoperable Implementations . . . . . . . . . . . . . . . .   7
     10.1.  Cisco Implementation . . . . . . . . . . . . . . . . . .   7
     10.2.  Juniper Implementation . . . . . . . . . . . . . . . . .   7
     10.3.  rpki.net Implementation  . . . . . . . . . . . . . . . .   7
     10.4.  RIPE NCC Implementation  . . . . . . . . . . . . . . . .   8
     10.5.  RTRlib Implementation  . . . . . . . . . . . . . . . . .   8
     10.6.  BBN RPSTIR Implementation  . . . . . . . . . . . . . . .   8
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   12. Security considerations . . . . . . . . . . . . . . . . . . .   8
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8