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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 09 August 2016 16:18 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 7015B12D097; Tue, 9 Aug 2016 09:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.548
X-Spam-Level:
X-Spam-Status: No, score=-5.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 bZqSyqYyPur1; Tue, 9 Aug 2016 09:18:33 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3798E12B04D; Tue, 9 Aug 2016 09:18:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DBB51BE32; Tue, 9 Aug 2016 17:18:31 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uLiD8ebDPKTo; Tue, 9 Aug 2016 17:18:31 +0100 (IST)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3A94EBE33; Tue, 9 Aug 2016 17:18:31 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1470759511; bh=J3y71KrXhL+1WMEffwe3li4N/BLuX1Vmp7dq08+Tx+I=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=Cj4XwTpKdl2VDCvOX1nFZJpM3ld2U40Rix9RlM5o8rfCgMptIihTdoQiquo+RkVRO rh0nI/fvSKzGF+EvJnEhtl2bHKU58YWWNAfnDl8p4cIi/PM76zzqpbdfgawNzfjghu y3GZ1epCAVVaPxZbGJJYG4UuqZdAVzcSBU2ZJkNY=
To: Gert Doering <gert@space.net>
References: <20160803153112.6173.42252.idtracker@ietfa.amsl.com> <20160809150547.GV3202@vurt.meerval.net> <7e8c0d78-9ff4-0df1-80a5-9ba03d47618c@cs.tcd.ie> <20160809160433.GW79185@Space.Net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <b8d98a77-c176-f09c-1cf2-315229dfddc4@cs.tcd.ie>
Date: Tue, 09 Aug 2016 17:18:30 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160809160433.GW79185@Space.Net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms010301020506070306020509"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/DI5ADhogBMHagHjFMtCriJQwjw4>
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:18:34 -0000


On 09/08/16 17:04, Gert Doering wrote:
> 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.

(Noting that this was an aside that I don't consider blocking...) I
think one could argue that this draft is changing that as it's here
that we're defining this community. And I'd say it would be useful
to call it out too, if there's really no sensible way to implement
this without such an additional configuration.

Cheers,
S.


> 
> Gert Doering
>         -- NetMaster
>