BGP RPKI-Based Origin Validation on Export

Document Type Active Internet-Draft (sidrops WG)
Last updated 2019-10-30
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            R. Bush
Internet-Draft                        Internet Initiative Japan & Arrcus
Updates: 6811 (if approved)                                      R. Volk
Intended status: Standards Track                        Deutsche Telekom
Expires: May 2, 2020                                            J. Heitz
                                                        October 30, 2019

               BGP RPKI-Based Origin Validation on Export


   A BGP speaker may perform RPKI origin validation not only on routes
   received from BGP neighbors and routes that are redistributed from
   other routing protocols, but also on routes it sends to BGP
   neighbors.  For egress policy, it is important that the
   classification uses the effective origin AS of the processed route,
   which may specifically be altered by the commonly available knobs
   such as removing private ASs, confederation handling, and other
   modifications of the origin AS.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   be interpreted as described in [RFC2119] only when they appear in all
   upper case.  They may also appear in lower or mixed case as English
   words, without normative meaning.

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

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

Bush, et al.               Expires May 2, 2020                  [Page 1]
Internet-Draft BGP RPKI-Based Origin Validation on Export   October 2019

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

1.  Introduction

   This document does not change the protocol or semantics of [RFC6811]
   of RPKI-based origin validation.  It highlights an important use case
   of origin validation in eBGP egress policies, explaining specifics of
   correct implementation in this context.

   As the origin AS may be modified by outbound policy, policy semantics
   based on RPKI Origin Validation state MUST be able to be applied
   separately on distribution into BGP and on egress.

   When applied to egress policy, the effective origin AS MUST be used
   to determine the Origin Validation state.  The effective origin AS is
   that which will actually be the origin AS in the announcement.  It
   might be affected by removal of private AS(s), confederation, AS
   migration, etc.  If there are any AS_PATH modifications resulting in
   origin AS change, then these MUST be taken into account.

2.  Suggested Reading

   It is assumed that the reader understands BGP, [RFC4271], the RPKI,
   [RFC6480], Route Origin Authorizations (ROAs), [RFC6482], RPKI-based
   Prefix Validation, [RFC6811], and Origin Validation Clarifications,

3.  Egress Processing

   BGP implementations supporting RPKI-based origin validation SHOULD
   provide the same policy configuration primitives for decisions based
   on validation state available for use in ingress, redistribution, and
   egress policies.  When applied to egress policy, validation state
   MUST be determined using the effective origin AS of the route as it
   will (or would) be announced to the peer.  The effective origin AS

Bush, et al.               Expires May 2, 2020                  [Page 2]
Internet-Draft BGP RPKI-Based Origin Validation on Export   October 2019

   may differ from that of the route in the RIB due to commonly
   available knobs such as: removal of private ASs, AS path
   manipulation, confederation handling, etc.

   Egress policy handling can provide more robust protection for
Show full document text