IETF Logo Mail Archive

Re: [GROW] WGLC: draft-ietf-grow-simple-leak-attack-bgpsec-no-help

Danny McPherson <danny@tcb.net> Tue, 20 May 2014 01:12 UTC

Return-Path: <danny@tcb.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2A01A022B for <grow@ietfa.amsl.com>; Mon, 19 May 2014 18:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level:
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, USER_IN_WHITELIST=-100] autolearn=unavailable
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 lpCR1M_TjPvq for <grow@ietfa.amsl.com>; Mon, 19 May 2014 18:12:30 -0700 (PDT)
Received: from mail.tcb.net (mail.tcb.net [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id F10F81A0460 for <grow@ietf.org>; Mon, 19 May 2014 18:12:28 -0700 (PDT)
Received: from dspam (unknown [127.0.0.1]) by mail.tcb.net (Postfix) with SMTP id CAAC5300096 for <grow@ietf.org>; Tue, 20 May 2014 01:12:28 +0000 (UTC)
Received: from [192.168.1.8] (pool-98-118-253-16.clppva.fios.verizon.net [98.118.253.16]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.tcb.net (Postfix) with ESMTPSA id B8213300090; Mon, 19 May 2014 19:12:27 -0600 (MDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_577E6247-FA4D-4C6A-87F0-52DE9466FF06"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <CD783686-9D5B-4D0B-92CC-3D4ACF1A6D07@puck.nether.net>
Date: Mon, 19 May 2014 21:12:27 -0400
Message-Id: <AAF0DA78-E619-43E1-8D02-F47504E0AF5F@tcb.net>
References: <CAL9jLabRKA2gezfRdzND1TSYMJO+a_4mVV+M302cLBFTUwYmTQ@mail.gmail.com> <CF96AEDB.1B684%wesley.george@twcable.com> <CAL9jLaZ9J52Dt5n1Wk2KYTqwzmefGxvq-bRcfMfhWBNwf_6ZGg@mail.gmail.com> <EFD759C6-6F35-4397-A27E-BF1E650663BC@tislabs.com> <34076248-B77A-418F-9ED2-E5A607D39B51@tcb.net> <CD783686-9D5B-4D0B-92CC-3D4ACF1A6D07@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.1874)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Mon May 19 19:12:28 2014
X-DSPAM-Confidence: 0.9899
X-DSPAM-Improbability: 1 in 9809 chance of being spam
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 537aabfc42071822018524
X-DSPAM-Factors: 27, Cc*ietf.org+grow, 0.01000, Cc*ietf.org+grow, 0.01000, Mime-Version*OS+X, 0.01000, Cc*ietf.org+#+ietf.org, 0.01000, Cc*ietf.org+#+ietf.org, 0.01000, Subject*Re+#+WGLC, 0.01000, Mime-Version*X+#+#+1874, 0.01000, be+#+#+#+the, 0.01000, be+#+#+#+the, 0.01000, Mime-Version*Mac+#+#+#+7.2, 0.01000, Mime-Version*Mail+#+1874, 0.01000, Cc*grow+#+#+ietf.org, 0.01000, Cc*grow+#+#+ietf.org, 0.01000, Mime-Version*OS+#+#+7.2, 0.01000, On+May, 0.01000, On+May, 0.01000, On+#+#+2014, 0.01000, On+#+#+2014, 0.01000, Subject*Re+#+#+draft-ietf-grow-simple-leak-attack-bgpsec-no-help, 0.01000, wrote+#+#+a, 0.01000, wrote+#+#+a, 0.01000, Mime-Version*Mail+7.2, 0.01000, Mime-Version*1.0+Mac, 0.01000, the+#+of, 0.01000, the+#+of, 0.01000, is+a, 0.01000, is+a, 0.01000
Archived-At: http://mailarchive.ietf.org/arch/msg/grow/-OSQCMgynQCWGe6UpbZna41PkiU
Cc: grow-chairs@ietf.org, "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] WGLC: draft-ietf-grow-simple-leak-attack-bgpsec-no-help
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 20 May 2014 01:12:31 -0000

Where else would it be documented?  If the IETF is designing protocols that operators will have to deploy, should this not be here?  I thought that was the point of an “operations” working group?

-danny

On May 19, 2014, at 9:11 PM, Jared Mauch <jared@puck.nether.net> wrote:

> Is there a need for this to be explicitly documented within the IETF?  I certainly agree there is a problem, but this feels like operational guidance or perhaps a BCP or similar document? (eg: Filter your peer ASNs from your other peers).

v2.23.0 | Report a Bug | By Email