Re: [GROW] Stephen Farrell's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)

Gert Doering <gert@space.net> Tue, 09 August 2016 16:04 UTC

Return-Path: <gert@space.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D45E412D5D8 for <grow@ietfa.amsl.com>; Tue, 9 Aug 2016 09:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.847
X-Spam-Level:
X-Spam-Status: No, score=-3.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.247] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rQjHt5b6Zdjw for <grow@ietfa.amsl.com>; Tue, 9 Aug 2016 09:04:39 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DF8312D624 for <grow@ietf.org>; Tue, 9 Aug 2016 09:04:35 -0700 (PDT)
X-Original-To: grow@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id C193861B49 for <grow@ietf.org>; Tue, 9 Aug 2016 18:04:33 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 743876012B; Tue, 9 Aug 2016 18:04:33 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 622623E25C; Tue, 9 Aug 2016 18:04:33 +0200 (CEST)
Date: Tue, 09 Aug 2016 18:04:33 +0200
From: Gert Doering <gert@space.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <20160809160433.GW79185@Space.Net>
References: <20160803153112.6173.42252.idtracker@ietfa.amsl.com> <20160809150547.GV3202@vurt.meerval.net> <7e8c0d78-9ff4-0df1-80a5-9ba03d47618c@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha-256"; boundary="/XqONRrzRebDWlSK"
Content-Disposition: inline
In-Reply-To: <7e8c0d78-9ff4-0df1-80a5-9ba03d47618c@cs.tcd.ie>
X-NCC-RegID: de.space
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/NEEPt4aiQeX8QzjHLAkLcoJ1BPA>
Cc: grow-chairs@ietf.org, grow@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-grow-blackholing@ietf.org
Subject: Re: [GROW] Stephen Farrell's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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, 09 Aug 2016 16:04:40 -0000

Hi,

On Tue, Aug 09, 2016 at 04:50:58PM +0100, Stephen Farrell wrote:
> Ok - I assume that means that being able to accept a blackholed /32
> doesn't therefore mean having to accept other BGP announcements for
> /32's without any additional controls. Would it be sensible to say
> that implementers MUST/SHOULD allow treating blackholing differently
> in that respect? (e.g. to keep some different configured limits for
> the length of prefix they accept for blackholes vs. other BGP stuff?)

I think this is implicit by the statement that there must be a covering
prefix permitted by routing policy - so the assumption is "the blackhole
can be more specific".

All existing deployments I know do it that way - that is, for regular
traffic, prefixes are permitted as documented (like: 192.0.2.0/24 is
accepted, and no more specifics) while blackhole-tagged prefixes
go up to /32 ("if blackhole-community present, accept 192.0.2.0/24../32").

I'm not sure if we need to spell this out - it's not something this draft
is changing.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279