The Resource Public Key Infrastructure (RPKI) to Router Protocol
draft-ietf-sidr-rpki-rtr-rfc6810-bis-08

The information below is for an old version of the document
Document Type Active Internet-Draft (sidr WG)
Last updated 2017-02-16 (latest revision 2017-01-07)
Replaces draft-austein-sidr-rpki-rtr-rfc6810bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Chris Morrow
Shepherd write-up Show (last changed 2016-03-05)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Chris Morrow" <morrowc@ops-netman.net>, aretana@cisco.com
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                            R. Bush
Internet-Draft                                 Internet Initiative Japan
Intended status: Standards Track                              R. Austein
Expires: July 11, 2017                              Dragon Research Labs
                                                         January 7, 2017

    The Resource Public Key Infrastructure (RPKI) to Router Protocol
                draft-ietf-sidr-rpki-rtr-rfc6810-bis-08

Abstract

   In order to verifiably validate the origin Autonomous Systems and
   Autonomous System Paths of BGP announcements, routers need a simple
   but reliable mechanism to receive Resource Public Key Infrastructure
   (RFC 6480) prefix origin data and router keys from a trusted cache.
   This document describes a protocol to deliver them.

   This document describes version 1 of the rpki-rtr protocol.  RFC 6810
   describes version 0.

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

Copyright Notice

   Copyright (c) 2017 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

Bush & Austein            Expires July 11, 2017                 [Page 1]
Internet-Draft            RPKI-Router Protocol              January 2017

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Changes from RFC 6810 . . . . . . . . . . . . . . . . . .   3
   2.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Deployment Structure  . . . . . . . . . . . . . . . . . . . .   4
   4.  Operational Overview  . . . . . . . . . . . . . . . . . . . .   5
   5.  Protocol Data Units (PDUs)  . . . . . . . . . . . . . . . . .   6
     5.1.  Fields of a PDU . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Serial Notify . . . . . . . . . . . . . . . . . . . . . .   9
     5.3.  Serial Query  . . . . . . . . . . . . . . . . . . . . . .   9
     5.4.  Reset Query . . . . . . . . . . . . . . . . . . . . . . .  10
     5.5.  Cache Response  . . . . . . . . . . . . . . . . . . . . .  11
     5.6.  IPv4 Prefix . . . . . . . . . . . . . . . . . . . . . . .  11
     5.7.  IPv6 Prefix . . . . . . . . . . . . . . . . . . . . . . .  13
     5.8.  End of Data . . . . . . . . . . . . . . . . . . . . . . .  13
     5.9.  Cache Reset . . . . . . . . . . . . . . . . . . . . . . .  14
     5.10. Router Key  . . . . . . . . . . . . . . . . . . . . . . .  15
     5.11. Error Report  . . . . . . . . . . . . . . . . . . . . . .  16
   6.  Protocol Timing Parameters  . . . . . . . . . . . . . . . . .  17
   7.  Protocol Version Negotiation  . . . . . . . . . . . . . . . .  18
   8.  Protocol Sequences  . . . . . . . . . . . . . . . . . . . . .  20
     8.1.  Start or Restart  . . . . . . . . . . . . . . . . . . . .  20
     8.2.  Typical Exchange  . . . . . . . . . . . . . . . . . . . .  21
     8.3.  No Incremental Update Available . . . . . . . . . . . . .  21
     8.4.  Cache Has No Data Available . . . . . . . . . . . . . . .  22
   9.  Transport . . . . . . . . . . . . . . . . . . . . . . . . . .  22
     9.1.  SSH Transport . . . . . . . . . . . . . . . . . . . . . .  24
     9.2.  TLS Transport . . . . . . . . . . . . . . . . . . . . . .  24
     9.3.  TCP MD5 Transport . . . . . . . . . . . . . . . . . . . .  25
     9.4.  TCP-AO Transport  . . . . . . . . . . . . . . . . . . . .  25
   10. Router-Cache Setup  . . . . . . . . . . . . . . . . . . . . .  26
   11. Deployment Scenarios  . . . . . . . . . . . . . . . . . . . .  27
   12. Error Codes . . . . . . . . . . . . . . . . . . . . . . . . .  28
   13. Security Considerations . . . . . . . . . . . . . . . . . . .  29
Show full document text