Use Cases for Localized Versions of the RPKI
draft-ietf-sidrops-lta-use-cases-02

Document Type Active Internet-Draft (sidrops WG)
Last updated 2017-10-16
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            R. Bush
Internet-Draft                                 Internet Initiative Japan
Intended status: Informational                          October 16, 2017
Expires: April 19, 2018

              Use Cases for Localized Versions of the RPKI
                  draft-ietf-sidrops-lta-use-cases-02

Abstract

   There are a number of critical circumstances where a localized
   routing domain needs to augment or modify its view of the Global
   RPKI.  This document attempts to outline a few of them.

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 https://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 April 19, 2018.

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
   (https://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                     Expires April 19, 2018                 [Page 1]
Internet-DraftUse Cases for Localized Versions of the RPKI  October 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Suggested Reading . . . . . . . . . . . . . . . . . . . . . .   2
   3.  What is 'Local' . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Example Uses  . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Some Approaches . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Today RPKI-based Origin Validation, [RFC6811], relies on widespread
   deployment of the Global Resource Public Key Infrastructure (RPKI),
   [RFC6480].  In the future, RPKI-based Path Validation,
   [I-D.ietf-sidr-bgpsec-overview], will be even more reliant on the
   Global RPKI.

   But there are critical circumstances in which a local, clearly-
   scoped, administrative and/or routing domain will want to augment
   and/or modify their internal view of the Global RPKI.

   This document attempts to lay out a few of those use cases.  It is
   not intended to be authoritative, complete, or to become a standard.
   It merely tries to lay out a few critical examples to help frame the
   issues.

2.  Suggested Reading

   It is assumed that the reader understands the RPKI, see [RFC6480],
   the RPKI Repository Structure, see [RFC6481], Route Origin
   Authorizations (ROAs), see [RFC6482], and GhostBusters Records, see
   [RFC6493].

3.  What is 'Local'

   The RPKI is a distributed database containing certificates, CRLs,
   manifests, ROAs, and GhostBusters Records as described in [RFC6481].
   Policies and considerations for RPKI object generation and
   maintenance are discussed elsewhere.

   Like the DNS, the Global RPKI tries to present a single global view,
   although only a loosely consistent view, depending on timing,

Bush                     Expires April 19, 2018                 [Page 2]
Internet-DraftUse Cases for Localized Versions of the RPKI  October 2017

   updating, fetching, etc.  There is no 'fix' for this, it is not
   broken, it is the nature of distributed data with distributed caches.
Show full document text