RPKI Validation Reconsidered
draft-ietf-sidr-rpki-validation-reconsidered-07

Document Type Active Internet-Draft (sidr WG)
Last updated 2017-03-09 (latest revision 2016-10-03)
Replaces draft-huston-rpki-validation
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Chris Morrow
Shepherd write-up Show (last changed 2016-10-26)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Chris Morrow" <morrowc@ops-netman.net>, aretana@cisco.com
Network Working Group                                          G. Huston
Internet-Draft                                             G. Michaelson
Updates: 3779 6482 6484 6487 (if                                   APNIC
         approved)                                           C. Martinez
Intended status: Standards Track                                  LACNIC
Expires: April 6, 2017                                    T. Bruijnzeels
                                                                RIPE NCC
                                                               A. Newton
                                                                    ARIN
                                                                 D. Shaw
                                                                 AFRINIC
                                                         October 3, 2016

                      RPKI Validation Reconsidered
            draft-ietf-sidr-rpki-validation-reconsidered-07

Abstract

   This document proposes an update to the certificate validation
   procedure specified in RFC 6487 that reduces aspects of operational
   fragility in the management of certificates in the RPKI, while
   retaining essential security features.

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 April 6, 2017.

Copyright Notice

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

Huston, et al.            Expires April 6, 2017                 [Page 1]
Internet-Draft               RPKI Validation                October 2016

   (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
   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.  Certificate Validation in the RPKI  . . . . . . . . . . . . .   2
   3.  Operational Considerations  . . . . . . . . . . . . . . . . .   3
   4.  An Amended RPKI Certification Validation Process  . . . . . .   5
     4.1.  Verified Resource Sets  . . . . . . . . . . . . . . . . .   5
     4.2.  Changes to existing standards . . . . . . . . . . . . . .   5
       4.2.1.  Changes to RFC6484  . . . . . . . . . . . . . . . . .   5
       4.2.2.  Changes to RFC3779  . . . . . . . . . . . . . . . . .   6
       4.2.3.  Addendum to RFC6268 . . . . . . . . . . . . . . . . .   9
       4.2.4.  Changes to RFC6487  . . . . . . . . . . . . . . . . .  11
       4.2.5.  Changes to RFC6482  . . . . . . . . . . . . . . . . .  15
       4.2.6.  Changes to BGPSec PKI Profiles  . . . . . . . . . . .  16
     4.3.  An example  . . . . . . . . . . . . . . . . . . . . . . .  16
   5.  Deployment Considerations . . . . . . . . . . . . . . . . . .  17
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  19
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   This document proposes an update to the certificate validation
   procedure specified in [RFC6487] that reduces aspects of operational
   fragility in the management of certificates in the RPKI, while
   retaining essential security features.

2.  Certificate Validation in the RPKI

   As currently defined in section 7.2 of [RFC6487], validation of PKIX
   certificates that conform to the RPKI profile relies on the use of a
Show full document text