[GROW] Stephen Farrell's Yes on draft-ietf-grow-route-leak-problem-definition-05: (with COMMENT)

"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Tue, 03 May 2016 23:04 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7377812D9E8; Tue, 3 May 2016 16:04:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160503230420.8256.28751.idtracker@ietfa.amsl.com>
Date: Tue, 03 May 2016 16:04:20 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/IhKcIkUNW8gbo9JcnYk5ZddY5OA>
Cc: draft-ietf-grow-route-leak-problem-definition@ietf.org, grow-chairs@ietf.org, grow@ietf.org
Subject: [GROW] Stephen Farrell's Yes on draft-ietf-grow-route-leak-problem-definition-05: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2016 23:04:20 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-grow-route-leak-problem-definition-05: Yes

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-grow-route-leak-problem-definition/



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


- Thanks for doing this. The set of references alone seems
particularly valuable.

- section 2, does "propagation" in the definition mean
that purely faked announcement messages (ignoring RPKI for
the moment) that overlap with genuine announcements cannot
be considered route-leaks?  From the receiver POV, those
would not be distinct. It was probably already suggested
but if not, do you think would s/propagation/receipt/ or
similar be a little better?