IETF Logo Mail Archive

Re: [GROW] I-D Action: draft-ietf-grow-simple-leak-attack-bgpsec-no-help-03.txt

Christopher Morrow <christopher.morrow@gmail.com> Tue, 26 November 2013 20:54 UTC

Return-Path: <christopher.morrow@gmail.com>
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 5C67A1AD9AE for <grow@ietfa.amsl.com>; Tue, 26 Nov 2013 12:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 sSDxhZuGlp3H for <grow@ietfa.amsl.com>; Tue, 26 Nov 2013 12:54:54 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 361831AD942 for <grow@ietf.org>; Tue, 26 Nov 2013 12:54:54 -0800 (PST)
Received: by mail-lb0-f178.google.com with SMTP id c11so4994247lbj.9 for <grow@ietf.org>; Tue, 26 Nov 2013 12:54:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=v3GLnE2T4SZ3LJs367ftNZrsJHPuaNiTUcCfUrpNpZk=; b=ArEke20cjHxCaoHD3jOb7LT3ZMZRsbmM/ctoJhfuyxbItsnohqboaTr6Xeu0gpN71F sL2t6vbdR0rYHwasmWqmqqjbionvmfvMOeGUn+IJHMyr+vFkiF8YhX7cannLbIVO6hkO POo4H6mo50MGPAiCWCu+dxUtv/ZoSTAicCLkIai2A18SUSzIloa0KxCew6cLCCczX5s3 RBTNDwEe7zmz6EwN1Ib+1OwHaasdlWutbhgzmxK2rHmkey70SExoMMDyhE23lY9yEfSu 32FPNiybckDH5LSXYgwqiVrnycb1g62O7bnOztNTGIUKBJGQVWtGdg/g9/bQQRWbxEAp IlFg==
MIME-Version: 1.0
X-Received: by 10.112.170.66 with SMTP id ak2mr271574lbc.60.1385499293251; Tue, 26 Nov 2013 12:54:53 -0800 (PST)
Received: by 10.152.37.170 with HTTP; Tue, 26 Nov 2013 12:54:53 -0800 (PST)
In-Reply-To: <CAL9jLaaEGpJ-B75EAOCCJDG14B8ZWJQ2FK7=AgXt1WQe=5geiQ@mail.gmail.com>
References: <20131118230146.22016.28407.idtracker@ietfa.amsl.com> <77143901-5DA3-4937-8162-509B62A61594@apnic.net> <CAL9jLabPjvXaAUaSEyQXdFvSDPZ_bJX4rjGxOGd0BqYhQcQYdg@mail.gmail.com> <FDFB46E9-ECD0-4CFF-A846-2E6FE9F8C9D7@apnic.net> <CAL9jLaaFszKUR0oZe-3gxR8JeFyTAjoe1BmD2ixXnjhvU7Mv5A@mail.gmail.com> <3EEF9354-766C-4687-8DD4-55759B9826CB@apnic.net> <CAL9jLaaEGpJ-B75EAOCCJDG14B8ZWJQ2FK7=AgXt1WQe=5geiQ@mail.gmail.com>
Date: Tue, 26 Nov 2013 15:54:53 -0500
Message-ID: <CAL9jLaa5-f4tmPZXSvZXDn640wm6VkfbYqS5qDBdZDVBZuJkXg@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Geoff Huston <gih@apnic.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-simple-leak-attack-bgpsec-no-help-03.txt
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, 26 Nov 2013 20:54:56 -0000

On Fri, Nov 22, 2013 at 9:13 PM, Christopher Morrow
<christopher.morrow@gmail.com> wrote:
>>
>>
>> As I read your thoughts I am left with the impression that you hold the
>> view that IDR that inherited the "requirements  for securing the routing
>> system" task. Have I got this right?
>>
>
> Your sentence didn't parse for me, one or more words are incorrect,
> somewhere around:
>   "view that IDR that inherited"
>
> I believe the path set forth by routing and ops ADs was the 3-4 step
> program above... is that your question?

Geoff, did I get your question's sense correct or not?

v2.23.0 | Report a Bug | By Email