[Sidrops] Robert Wilton's No Objection on draft-ietf-sidrops-ov-egress-02: (with COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Mon, 06 April 2020 17:43 UTC

Return-Path: <noreply@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 41B033A0D06; Mon, 6 Apr 2020 10:43:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sidrops-ov-egress@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org, sidrops-chairs@ietf.org, keyur@arrcus.com, warren@kumari.net, nathalie@ripe.net, keyur@arrcus.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.124.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <158619498278.23732.2401194914615255069@ietfa.amsl.com>
Date: Mon, 06 Apr 2020 10:43:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/_KkDQgkQKhOuLp8FICDiB51OGPk>
Subject: [Sidrops] Robert Wilton's No Objection on draft-ietf-sidrops-ov-egress-02: (with COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 06 Apr 2020 17:43:03 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-sidrops-ov-egress-02: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-ov-egress/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm not a BGP expert, but this document seems sensible to me.

Some comments:

1) In the first sentence of the introduction: Is it really correct that the
"This document does not change semantics of [RFC6811] RPKI-based origin
validation"?  Given that the 4th paragraph in the introduction then states that
"This document clarifies ..."

2) I wasn't entirely sure that section 2 (Suggested Reading) is required at
all, given that this is effectively what section 8.1 and 8.2 is listing anyway,
but equally I'm okay if the section is left in.

3) The security section is terse, and I agree that this doesn't introduce any
new security issues.  But I was wondering if the purpose of this clarification
is to improve security with more reliable filtering, and if so, would it be
helpful to have a sentence in the security section that states that?

One nit:

1) In the first sentence of the introduction "of [RFC6811] of RPKI-based origin
validation" -> "of [RFC6811] RPKI-based origin validation"?