[Sidrops] Last Call: <draft-ietf-sidrops-ov-clarify-03.txt> (Origin Validation Clarifications) to Internet Standard
The IESG <iesg-secretary@ietf.org> Wed, 25 July 2018 22:17 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 137DC130F2D; Wed, 25 Jul 2018 15:17:36 -0700 (PDT)
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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.82.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-sidrops-ov-clarify@ietf.org, keyur@arrcus.com, sidrops@ietf.org, Keyur Patel <keyur@arrcus.com>, sidrops-chairs@ietf.org, warren@kumari.net
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-ID: <153255705607.15385.11338294621699870268.idtracker@ietfa.amsl.com>
Date: Wed, 25 Jul 2018 15:17:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/a_YUG8OVy9tpDwyXRJyNYKfm90Q>
Subject: [Sidrops] Last Call: <draft-ietf-sidrops-ov-clarify-03.txt> (Origin Validation Clarifications) to Internet Standard
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 25 Jul 2018 22:17:41 -0000
The IESG has received a request from the SIDR Operations WG (sidrops) to consider the following document: - 'Origin Validation Clarifications' <draft-ietf-sidrops-ov-clarify-03.txt> as Internet 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 ietf@ietf.org mailing lists by 2018-08-08. 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 Deployment of RPKI-based BGP origin validation is hampered by, among other things, vendor mis-implementations in two critical areas: which routes are validated and whether policy is applied when not specified by configuration. This document is meant to clarify possible misunderstandings causing those mis-implementations; and thus updates RFC6811 by clarifying that all prefixes should be marked, and that policy must not be applied without operator configuration" The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-sidrops-ov-clarify/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-sidrops-ov-clarify/ballot/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc6482: A Profile for Route Origin Authorizations (ROAs) (Proposed Standard - IETF stream) rfc8097: BGP Prefix Origin Validation State Extended Community (Proposed Standard - IETF stream) rfc6811: BGP Prefix Origin Validation (Proposed Standard - IETF stream)