Re: [GROW] Stephen Farrell's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)
Job Snijders <job@instituut.net> Wed, 03 August 2016 17:20 UTC
Return-Path: <job@instituut.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 CC50712D7A8 for <grow@ietfa.amsl.com>; Wed, 3 Aug 2016 10:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.com
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 EZiS9D-Ov3v1 for <grow@ietfa.amsl.com>; Wed, 3 Aug 2016 10:20:36 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03EF812D12B for <grow@ietf.org>; Wed, 3 Aug 2016 10:20:32 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id f65so456393140wmi.0 for <grow@ietf.org>; Wed, 03 Aug 2016 10:20:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=KtLGolZCFz9z8jPycFy3N3tprdljQKfcTJ5npmzn0+s=; b=rEccPDPI4SS7MKCdxwkUe/RVQwqvs06zApe7HP7ny+9tJwZZgRzDjGThn7gQ0Jiih+ Tu/dXyqL7E0kvHOoVXpgviX225ZEHQZHHqgSK4/CazRjb1bMn9Cpe+6kxLuc/zUfOhV9 NoNvgm5CB0VZINMeiOWuEJZ5MBLkFwo00DBLSDXnSn8EJvRdPerSb8Rwdp2mkh3FwffD pPQHpK/xH/U1sJ/U8a4WBLAqNhAXL5gnqLxTsoK003rijVMxeAQbB/K9G8W0w74gRxSP Wv4ElRj4k2ejZnVzMQ9l4Fhh4oTb8Uc9LRNjcnU/z9xuTnl+g6L79vSDqCBaVkyNxLsU geHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=KtLGolZCFz9z8jPycFy3N3tprdljQKfcTJ5npmzn0+s=; b=UnNX4SEWFWTh+QTfTrk8krBJRhuRu3Rg9YwmlW3mFyjH2nP51l/7tJj3IjtJbAfGOg z0wQ2h6lGv4mLzuxE2NDPSWZIJ0rIo4+RSHMwSSx5NtV3SWfO+GucfcOAmZIRYBncPYX WSs4twB0UO6DT2N82VuwsYIP22d8R/cwbg/ekSB6dr/TRoApeIxIalRjhZw0LepGvo7v ArWO+9UWpEQqdm/1jbVpvei/YFfuHedK7QUOGC9oCRhG0BcfRE1xHZlcDsNx6sgjmL/u aP+zCixoOUDStKEqErbL1wpGeLdh9s3SwFy43jhaEW9FKl8pm+wzv6r9hwrlNRqI4nk2 GUBQ==
X-Gm-Message-State: AEkoousB/EzP+rqvLxwg61LyVStiPFTAu9eoHwA7Z62WG9Ktu5sk8e6XcT4a/t36ys8cyA==
X-Received: by 10.28.20.139 with SMTP id 133mr26932500wmu.78.1470244831165; Wed, 03 Aug 2016 10:20:31 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:2053:87ec:28c7:7aca]) by smtp.gmail.com with ESMTPSA id o142sm28160516wme.20.2016.08.03.10.20.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Aug 2016 10:20:29 -0700 (PDT)
Date: Wed, 03 Aug 2016 19:20:28 +0200
From: Job Snijders <job@instituut.net>
To: "Smith, Donald" <Donald.Smith@CenturyLink.com>
Message-ID: <20160803172028.GF3202@vurt.meerval.net>
References: <20160803153112.6173.42252.idtracker@ietfa.amsl.com> <CAL9jLaZDe95T+J_3pk6LEarKuVFKEssRPWr973puoGgpeCNpaw@mail.gmail.com> <68EFACB32CF4464298EA2779B058889D3B592092@PDDCWMBXEX503.ctl.intranet>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <68EFACB32CF4464298EA2779B058889D3B592092@PDDCWMBXEX503.ctl.intranet>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.6.2 (2016-07-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/mF29HSga9ZBD-qTZwDkl_q7ThpI>
Cc: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-grow-blackholing@ietf.org" <draft-ietf-grow-blackholing@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
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: Wed, 03 Aug 2016 17:20:37 -0000
On Wed, Aug 03, 2016 at 05:06:22PM +0000, Smith, Donald wrote:
> Note everywhere this says BHF I assumed DBHF not Source based BHFing.
> I suspect SBHF is out of scope for this effort. I could be wrong.
Correct, the draft is very explicit in the first sentence:
"This document describes the use of a well-known Border Gateway
Protocol (BGP) community for destination based blackholing in IP
networks. " ^^^^^^^^^^^
> Should the draft be modified to state that or is it intended to allow
> SBHFing also?
No. IMHO that should be a different draft / community.
> So the risk looks the same, and should be mitigated with the same
> methods (md5 and GTSM?)
> I didn't hear a recommendation for GTSM but I think it should be in
> here.
The document is supposed to define a codepoint, not to be a BCP. While I
value and somewhat agree these are useful techniques, I consider them
out of scope.
> > its impact has been done? If this is new, then I don't see
> > that the security considerations text adequately describe
> > the range of possible attacks that could be mounted using
> > this scheme. (As an aside, I wonder if asking to blackhole
> > /32's and /128's might impact on routing table sizes and
> > if something ought be said about that?)
We don't put in every single BGP draft that you need to ensure that you
need adequate RAM, CPU, FIB, ASIC, Capacity, or $magic_powder. Whether
prefixes are colored with attributes or not, routing table size is a
consideration in every aspect of BGP life.
> Thus my suggestion that it be in the peering contract for how many and
> how long?
Any contractual terms are up to the network operator that implements a
routing policy that honors (or does not honor) the BLACKHOLE community,
that can't be part of the document.
Kind regards,
Job
- [GROW] Stephen Farrell's Discuss on draft-ietf-gr… Stephen Farrell
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Smith, Donald
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Job Snijders
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Gert Doering
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… heasley
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Christopher Morrow
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… David Farmer
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Nick Hilliard
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Randy Bush
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Smith, Donald
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Gert Doering
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Smith, Donald
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Stephen Farrell
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Joel Jaeggli
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Jeffrey Haas
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… joel jaeggli
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Job Snijders
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Stephen Farrell
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Gert Doering
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Stephen Farrell
- Re: [GROW] Stephen Farrell's Discuss on draft-iet… Job Snijders