The I in RPKI does not stand for Identity
draft-ymbk-sidrops-rpki-has-no-identity-00

Document Type Active Internet-Draft (individual)
Authors Randy Bush  , Russ Housley 
Last updated 2021-03-16
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) 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. Bush
Internet-Draft                        Arrcus & Internet Initiative Japan
Intended status: Standards Track                              R. Housley
Expires: September 17, 2021                               Vigil Security
                                                          March 16, 2021

               The I in RPKI does not stand for Identity
               draft-ymbk-sidrops-rpki-has-no-identity-00

Abstract

   There is a false notion that Internet Number Resources (INRs) in the
   RPKI can be associated with the real world identity of the 'owner' of
   an INR.  This document attempts to put that notion to rest.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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 September 17, 2021.

Copyright Notice

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

Bush & Housley         Expires September 17, 2021               [Page 1]
Internet-Draft  The I in RPKI does not stand for Identity     March 2021

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Bottom Line . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Resource Public Key Infrastructure (RPKI), see [RFC6480],
   "represents the allocation hierarchy of IP address space and
   Autonomous System (AS) numbers."  Though since, it has grown to
   include other similar resource and routing data.

   In security terms the phrase "Public Key" implies there are also
   private keys, a la [RFC5280].  And, as the RPKI has strong authority
   over ownership of Internet Number Resources (INRs), there is a desire
   to use the private keys to sign arbitrary documents to attest that
   the 'owner' of those resources has attested to the authenticity of
   those documents.  Instead, it is an authorization to speak for the
   named IP address blocks and AS numbers themselves, not their
   unidentifiable owners.

   There is a desire is to authenticate real world business transactions
   with the signatures of INR holders.  E.g. for Bill's Bait and Sushi
   to use their AS in the RPKI to sign a Letter of Authorization (LOA)
   for some other party to rack and stack hardware owned by BB&S.
   Unfortunately, this is not formally feasible.

   The I in RPKI actually stands for "Infrastructure," as in Resource
   Public Key Infrastructure, not for "Identity".  In fact, the RPKI
   does not provide any association between INRs and the real world
   holder(s) of those INRs.  The RPKI provides authorization to speak
   for the named IP address blocks and AS numbers.

Bush & Housley         Expires September 17, 2021               [Page 2]
Internet-Draft  The I in RPKI does not stand for Identity     March 2021

2.  The Bottom Line

   The RPKI was designed and specified to sign certificates for use
Show full document text