Resource Transfer in the Resource Public Key Infrastructure
draft-ymbk-sidrops-transfer-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         R. Austein
Internet-Draft                                                    Arrcus
Intended status: Standards Track                                 R. Bush
Expires: May 7, 2020                  Arrcus & Internet Initiative Japan
                                                               G. Huston
                                                           G. Michaelson
                                 Asia Pacific Network Information Centre
                                                        November 4, 2019

      Resource Transfer in the Resource Public Key Infrastructure
                     draft-ymbk-sidrops-transfer-00

Abstract

   Transfer within the RPKI of actual address space and/or autonomous
   system number resources between two Internet registries (ISPs, RIRs,
   NIRs, etc.) is reasonably achievable for most useful operational
   needs.  In this paper, we describe, at a high level, how this may be
   accomplished.

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 May 7, 2020.

Copyright Notice

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

Austein, et al.            Expires May 7, 2020                  [Page 1]
Internet-Draft        Resource Transfer in the RPKI        November 2019

   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 and Terms  . . . . . . . . . . . . . . . . . . .   2
   2.  A Simplistic Case . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Steps in Simple Case  . . . . . . . . . . . . . . . . . .   4
     2.2.  The Torn Euro Protocol  . . . . . . . . . . . . . . . . .   4
   3.  A More Complex Case . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  The Indirect Buyer  . . . . . . . . . . . . . . . . . . .   6
     3.2.  The Difference Between Buyer and Seller Chain . . . . . .   8
   4.  Transfer in the Absence of a Common Ancestor  . . . . . . . .   8
   5.  Transfer in process: Resources Change Forced from Above . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction and Terms

   To paraphrase the Introduction of [RFC6480], the "Resource Public Key
   Infrastructure (RPKI) represents the allocation hierarchy of IP
   address space and Autonomous System (AS) numbers; and is a
   distributed repository system for storing and disseminating the data
   objects that comprise the RPKI, as well as other signed objects
   necessary for improved routing security."

   An Internet Registry (IR) is the IANA, a Regional Internet Registry
   (RIR), a National Internet Registry (NIR), a Local Internet Registry
   (LIR), a Internet Service Provider (ISP), or an end site which may
   hold IP resources and is the subject of one or more certificates
   using [RFC3779] extensions in the Resource Public Key Infrastructure
   (RPKI), see [RFC6480].

   It is increasingly necessary to transfer resources between resource-
   holding entities in the RPKI, to do so without violating contracts,
   policies, etc., and while maintaining operational reliability and
   administrative accuracy with minimal administrative overhead.

Austein, et al.            Expires May 7, 2020                  [Page 2]
Internet-Draft        Resource Transfer in the RPKI        November 2019

Show full document text