Last Call: <draft-ietf-sidrops-ov-egress-01.txt> (BGP RPKI-Based Origin Validation on Export) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 04 March 2020 22:59 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FBE53A0B4E; Wed, 4 Mar 2020 14:59:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-sidrops-ov-egress-01.txt> (BGP RPKI-Based Origin Validation on Export) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.119.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: sidrops@ietf.org, keyur@arrcus.com, draft-ietf-sidrops-ov-egress@ietf.org, warren@kumari.net, nathalie@ripe.net, sidrops-chairs@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <158336274444.29483.18238070064182080116@ietfa.amsl.com>
Date: Wed, 04 Mar 2020 14:59:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/QkyjZe5CYsbOgMxTh-J1D4ciNDw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2020 22:59:05 -0000
The IESG has received a request from the SIDR Operations WG (sidrops) to consider the following document: - 'BGP RPKI-Based Origin Validation on Export' <draft-ietf-sidrops-ov-egress-01.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2020-03-18. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-sidrops-ov-egress/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-sidrops-ov-egress/ballot/ No IPR declarations have been submitted directly on this I-D.