RPKI Validation Re-reconsidered
draft-spaghetti-sidrops-rpki-validation-update-00

Document Type Active Internet-Draft (individual)
Authors Job Snijders  , Ben Maddison 
Last updated 2021-02-22
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                        J. Snijders
Internet-Draft                                                    Fastly
Obsoletes: 8360 (if approved)                                B. Maddison
Updates: 6482,6487 (if approved)                              Workonline
Intended status: Standards Track                       February 22, 2021
Expires: August 26, 2021

                    RPKI Validation Re-reconsidered
           draft-spaghetti-sidrops-rpki-validation-update-00

Abstract

   This document describes an improved validation procedure for Resource
   Public Key Infrastructure (RPKI) signed objects.  This document
   updates RFC 6482.  This document updates RFC 6487.  This document
   obsoletes RFC 8360.

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 August 26, 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
   (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

Snijders & Maddison      Expires August 26, 2021                [Page 1]
Internet-Draft          RPKI Validation Algorithm          February 2021

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Deprecation of RFC 8360 . . . . . . . . . . . . . . . . . . .   2
   3.  Updates to RFC 6482 . . . . . . . . . . . . . . . . . . . . .   3
   4.  Updates to RFC 6487 . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Updates to Section 7.2  . . . . . . . . . . . . . . . . .   4
     4.2.  Updates to Section 9  . . . . . . . . . . . . . . . . . .   6
   5.  Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   [RFC8360] describes an improved validation algorithm for signed
   objects published in the RPKI.  The improved validation algorithm
   would help in situations such as described in this [Report].
   However, operational experience has shown the described procedure for
   deploying updates to the validation algorithm, as described in
   [RFC6487] Section 9, is impractical.  This document deprecates the
   original [RFC6487] section 7 algorithm in favour of the [RFC8360]
   algorithm, and obsoletes [RFC8360] because a migration via those
   codepoints is infeasible.  This document also deprecates the
   procedure set out in [RFC6487] section 9 for future changes to the
   validation algorithm.

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

2.  Deprecation of RFC 8360

   [RFC8360] defines several alternative OIDs for use in Resource
   Certificates [RFC6487]:

Snijders & Maddison      Expires August 26, 2021                [Page 2]
Internet-Draft          RPKI Validation Algorithm          February 2021

   o  id-cp-ipAddr-asNumber-v2 - Section 4.2.1 [RFC8360]

   o  id-pe-ipAddrBlocks-v2 - Sections 4.2.2.1 and 4.2.2.2 [RFC8360]

   o  id-pe-autonomousSysIds-v2 - Sections 4.2.2.3 and 4.2.2.4 [RFC8360]

   The stated purpose of the above OIDs is rendered obsolete by the
Show full document text