RPKI Validation State Unverified
draft-borchert-sidrops-rpki-state-unverified-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-23
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Internet Engineering Task Force (IETF)                       O. Borchert
Internet-Draft                                             D. Montgomery
Updates: 6811, 8097 (if approved)                               USA NIST
Intended status: Standards Track                                        
Expires: April 26, 2019                                 October 23, 2018

                    RPKI Validation State Unverified
            draft-borchert-sidrops-rpki-state-unverified-00

Abstract

   In case operators decide not to evaluate BGP route prefixes according
   to RPKI origin validation, none of the available states as specified
   in RFC 6811 do properly represent this decision. This document
   introduces "Unverified" as well-defined validation state which allows
   to properly identify route prefixes as not evaluated according to
   RPKI route origin validation.

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

 

Borchert & Montgomery    Expires April 26, 2019                 [Page 1]
Internet Draft      RPKI Validation State Unverified    October 23, 2018

Copyright Notice

   Copyright (c) 2018 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
   (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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Suggested Reading  . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Initializing route prefixes  . . . . . . . . . . . . . . . . .  3
     3.1. Update to RFC 6811  . . . . . . . . . . . . . . . . . . . .  4
     3.2. Update to RFC 8097  . . . . . . . . . . . . . . . . . . . .  4
   3.  Usage Considerations . . . . . . . . . . . . . . . . . . . . .  5
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     6.1.  Normative References . . . . . . . . . . . . . . . . . . .  6
     8.2.  Informative References . . . . . . . . . . . . . . . . . .  6
   Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

 

Borchert & Montgomery    Expires April 26, 2019                 [Page 2]
Internet Draft      RPKI Validation State Unverified    October 23, 2018

1.  Introduction

   Prefix origin validation provides well-defined validation states.
   Though, there are instances in which no evaluation of a route prefix
   is performed, not through RPKI route origin validation [RFC6811],
   signaling via the extended community string as specified in
   [RFC8097], or operator configuration. In these circumstances RFC 6811
   specifies the implementation SHOULD initialize the validation state
   of such route to "NotFound". Here, the absence of a well-defined
   validation state for a route prefix not evaluated, requires the usage
   of a state otherwise reserved as outcome of the evaluation of such.
   This "waters" down the meaning of the used state. The specification
   of a proper validation state that allows identifying non-evaluated
   routes, becomes of essence once an operator decides to write policies
   on the validation state "NotFound". A route prefix labeled "NotFound"
   cannot be considered same as an unverified route prefix.

   Hence, this document updates RFC 6811 and RFC 8097 by adding the
   proposed validation state "Unverified".
Show full document text