[Sidrops] RFC 8893 on Resource Public Key Infrastructure (RPKI) Origin Validation for BGP Export

rfc-editor@rfc-editor.org Fri, 25 September 2020 23:46 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA12F3A0BEE; Fri, 25 Sep 2020 16:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aAAb4RQSJwGV; Fri, 25 Sep 2020 16:46:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFCDA3A0BDB; Fri, 25 Sep 2020 16:46:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A96AFF40766; Fri, 25 Sep 2020 16:46:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sidrops@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200925234620.A96AFF40766@rfc-editor.org>
Date: Fri, 25 Sep 2020 16:46:20 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/932kJnMWV6j6UuyKKjrLv8qgMBQ>
Subject: [Sidrops] =?utf-8?q?RFC_8893_on_Resource_Public_Key_Infrastructu?= =?utf-8?q?re_=28RPKI=29_Origin_Validation_for_BGP_Export?=
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2020 23:46:36 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8893

        Title:      Resource Public Key Infrastructure (RPKI) 
                    Origin Validation for BGP Export 
        Author:     R. Bush,
                    R. Volk,
                    J. Heitz
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2020
        Mailbox:    randy@psg.com, 
                    ietf@rewvolk.de, 
                    jheitz@cisco.com
        Pages:      5
        Updates:    RFC 6811

        I-D Tag:    draft-ietf-sidrops-ov-egress-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8893

        DOI:        10.17487/RFC8893

A BGP speaker may perform Resource Public Key Infrastructure (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 use the 'effective origin AS' of
the processed route, which may specifically be altered by the
commonly available knobs, such as removing private ASes,
confederation handling, and other modifications of the origin AS. 
This document updates RFC 6811.

This document is a product of the SIDR Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC