Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs

Randy Bush <randy@psg.com> Mon, 14 April 2014 14:55 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB701A0489 for <sidr@ietfa.amsl.com>; Mon, 14 Apr 2014 07:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 AhcmEkxUiVqX for <sidr@ietfa.amsl.com>; Mon, 14 Apr 2014 07:55:07 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 826B21A0476 for <sidr@ietf.org>; Mon, 14 Apr 2014 07:55:07 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WZiHm-0006V0-Kl; Mon, 14 Apr 2014 14:55:03 +0000
Date: Mon, 14 Apr 2014 23:55:01 +0900
Message-ID: <m2vbucdkqi.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
In-Reply-To: <CAL9jLab5=JNbPRMji7xWWCR_+QLRpbguShU7K_Uu56jYxKymZw@mail.gmail.com>
References: <52D072F6.9030304@ops-netman.net> <52D0A0AC.5040903@ops-netman.net> <CF07E61E.AF86%wesley.george@twcable.com> <m238kcea01.wl%randy@psg.com> <CF0BE8F1.B1BE%wesley.george@twcable.com> <m2a9ehjto3.wl%randy@psg.com> <52E92B20.9060505@bbn.com> <CAL9jLaapjPL0_OU8-L0U5BiLXPPoEhkCZym=7R_qDDLSobKVjA@mail.gmail.com> <m2iosq8f9e.wl%randy@psg.com> <CAL9jLab5=JNbPRMji7xWWCR_+QLRpbguShU7K_Uu56jYxKymZw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/4pr3wQyu_MXhkRcVVXLgtIzYRx0
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] WGLC: draft-ietf-sidr-bgpsec-reqs
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 14:55:08 -0000

> I could easily replace per se with 'intrinsically' like:

yes.  do we need to play synonyms when, ab definito, they mean the same
thing?  i chose my words.  as you point out, they are correct.

> Is there a reason to keep the mention of route-leaks in this document?

i think it was shane who wanted them explicitly mentioned.  it seems to
be a fashionable term in grow this season, and i am not sure there is
any benefit to pretending we don't see it.  but i personally do not
care.

>   "As noted in the threat model, [I-D.ietf-sidr-bgpsec-threats], this
>    work is limited to threats to the BGP protocol.  Issues of business
>    relationship conformance, while quite important to operators, are
>    not security issues per se, and are outside the scope of this
>    document.  It is hoped that these issues will be better understood in
>    the future."

i can live with that

> I think this was in line with warren's suggestion, which wes agreed
> with as did stephen kent. This seems ok to me as well... I'd like to
> close the discussion sooner rather than later and send out a
> publication request.

as none of the folk you just listed were those specifically asking for
the term "route leaks," if you do not mind, it seems polite to wait a
few days to give them a chance to speak.  i can cut a new version if the
dust settles.

randy