datatracker.ietf.org
Sign in
Version 5.3.1, 2014-04-16
Report a bug

A Publication Protocol for the Resource Public Key Infrastructure (RPKI)
draft-ietf-sidr-publication-05

Document type: Active Internet-Draft (sidr WG)
Document stream: IETF
Last updated: 2014-02-12
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

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

Network Working Group                                          S. Weiler
Internet-Draft                                              SPARTA, Inc.
Intended status: Standards Track                             A. Sonalker
Expires: August 16, 2014                     Battelle Memorial Institute
                                                              R. Austein
                                                    Dragon Research Labs
                                                       February 12, 2014

A Publication Protocol for the Resource Public Key Infrastructure (RPKI)
                     draft-ietf-sidr-publication-05

Abstract

   This document defines a protocol for publishing Resource Public Key
   Infrastructure (RPKI) objects.  Even though the RPKI will have many
   participants issuing certificates and creating other objects, it is
   operationally useful to consolidate the publication of those objects.
   This document provides the protocol for doing so.

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 August 16, 2014.

Copyright Notice

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

Weiler, et al.           Expires August 16, 2014                [Page 1]
Internet-Draft          RPKI Publication Protocol          February 2014

   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Specification  . . . . . . . . . . . . . . . . . . .   3
     2.1.  Common XML Message Format . . . . . . . . . . . . . . . .   4
     2.2.  Publication and Withdrawal  . . . . . . . . . . . . . . .   4
     2.3.  Error handling  . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  XML Schema  . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  <publish/> Query  . . . . . . . . . . . . . . . . . . . .   7
     3.2.  <publish/> Reply  . . . . . . . . . . . . . . . . . . . .   8
     3.3.  <withdraw/> Query . . . . . . . . . . . . . . . . . . . .   9
     3.4.  <withdraw/> Reply . . . . . . . . . . . . . . . . . . . .   9
     3.5.  <report_error/> With Text . . . . . . . . . . . . . . . .   9
     3.6.  <report_error/> Without Text  . . . . . . . . . . . . . .   9
   4.  Operational Considerations  . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   This document assumes a working knowledge of the Resource Public Key
   Infrastructure (RPKI), which is intended to support improved routing
   security on the Internet.  [RFC6480]

   In order to make participation in the RPKI easier, it is helpful to
   have a few consolidated repositories for RPKI objects, thus saving
   every participant from the cost of maintaining a new service.
   Similarly, relying parties using the RPKI objects will find it faster
   and more reliable to retrieve the necessary set from a smaller number
   of repositories.

   These consolidated RPKI object repositories will in many cases be
   outside the administrative scope of the organization issuing a given

[include full document text]