IETF Logo Mail Archive

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

Nick Hilliard <nick@foobar.org> Sat, 13 August 2016 21:25 UTC

Return-Path: <nick@foobar.org>
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 DDDC112B068; Sat, 13 Aug 2016 14:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 aayyRr5JWIuC; Sat, 13 Aug 2016 14:25:03 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBE73126579; Sat, 13 Aug 2016 14:25:02 -0700 (PDT)
X-Envelope-To: iesg@ietf.org
Received: from cupcake.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id u7DLOw9u063225 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Aug 2016 22:24:59 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be cupcake.local
Message-ID: <57AF9029.9050106@foobar.org>
Date: Sat, 13 Aug 2016 22:24:57 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: heasley <heas@shrubbery.net>
References: <20160804011604.9572.65960.idtracker@ietfa.amsl.com> <20160809160259.GX3202@vurt.meerval.net> <57AF100C.3040009@foobar.org> <20160813145607.GB67315@shrubbery.net>
In-Reply-To: <20160813145607.GB67315@shrubbery.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/N_ax7F--yvkO2zsP4_WRKIpVWsE>
Cc: grow-chairs@ietf.org, grow@ietf.org, draft-ietf-grow-blackholing@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [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
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: Sat, 13 Aug 2016 21:25:05 -0000

heasley wrote:
> Sat, Aug 13, 2016 at 01:18:20PM +0100, Nick Hilliard:
>> The second adds a note to say that both the receiving and the sending
>> party should explicitly filter out more-specifics unless they're tagged
>> with BLACKHOLE.  I would be in favour of seeing this noted in the
>> security considerations section, as it is a security related problem.
> 
> though I agree with you, that seems unrelated to blackholing, and thus out
> of scope.  an informational rfc about best standard practices toward being
> a positive functioning member of the DFZ would be a better place for that;
> which may already exist unbeknownst to me.

the intention of this is to explicitly document good practice which some
operators are going to overlook, but I hear what you're saying.

Nick

v2.46.0 | Report a Bug | By Email | System Status