[GROW] Terry Manderson's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)
"Terry Manderson" <terry.manderson@icann.org> Thu, 04 August 2016 01:16 UTC
Return-Path: <terry.manderson@icann.org>
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 0E9AF12B028; Wed, 3 Aug 2016 18:16:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Terry Manderson <terry.manderson@icann.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160804011604.9572.65960.idtracker@ietfa.amsl.com>
Date: Wed, 03 Aug 2016 18:16:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/doTgROpDLTK0MAbB77rgVuHuJH0>
Cc: grow-chairs@ietf.org, grow@ietf.org, draft-ietf-grow-blackholing@ietf.org
Subject: [GROW] Terry Manderson's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and 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: Thu, 04 Aug 2016 01:16:04 -0000
Terry Manderson has entered the following ballot position for draft-ietf-grow-blackholing-02: Discuss 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-blackholing/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Firstly, thank you for documenting operational practice. With regards to section 3.3: "BGP speakers SHOULD only accept and honor BGP announcements carrying the BLACKHOLE community .." I really question why this is a "SHOULD" and not a "MUST", even in an informational RFC. Is the ability for a transit provider so loose that appropriate route filters from a peer ASN can't be applied so that only a "SHOULD" is practical? In which case I do question the sanity of making such a recommendation and thus service available if some other ASN might be able to inject the route and affect another service, even by mistake. Potentially if RPKI is in use, then a peer AS might be able to validate the announcement against a ROA. But it strikes me that this is not the machinery you would want to tack on in this case. The same could be said for section 3.2. I would be rather wary of NOT adding a NO_ADVERTISE (at the very least) and to be honest SHOULD still seems far too loose for me. Almost all of the recipe's that I've gazed upon ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- >From a comment point of view, this informational document is agnostic on any operational differences between 2-byte and 4-byte ASNs. Is that intentional? Are there any operational differences worth calling out in regard to using extended communities etc?
- [GROW] Terry Manderson's Discuss on draft-ietf-gr… Terry Manderson
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Terry Manderson's Discuss on draft-iet… joel jaeggli
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Terry Manderson
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Terry Manderson's Discuss on draft-iet… David Farmer
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Terry Manderson
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Terry Manderson
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Terry Manderson's Discuss on draft-iet… heasley
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Job Snijders
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Nick Hilliard
- Re: [GROW] Terry Manderson's Discuss on draft-iet… heasley
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Randy Bush
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Pedro Andrés Aranda Gutiérrez
- Re: [GROW] Terry Manderson's Discuss on draft-iet… heasley
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Randy Bush
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Joel Jaeggli
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Randy Bush
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Marco Marzetti
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Job Snijders
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Nick Hilliard
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Job Snijders
- Re: [GROW] Terry Manderson's Discuss on draft-iet… joel jaeggli
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Terry Manderson
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Nick Hilliard
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Job Snijders
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Nick Hilliard
- Re: [GROW] Terry Manderson's Discuss on draft-iet… heasley
- Re: [GROW] Terry Manderson's Discuss on draft-iet… Nick Hilliard