IETF Logo Mail Archive

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

Christopher Morrow <morrowc.lists@gmail.com> Mon, 14 April 2014 15:24 UTC

Return-Path: <christopher.morrow@gmail.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 AB7121A02CF for <sidr@ietfa.amsl.com>; Mon, 14 Apr 2014 08:24:58 -0700 (PDT)
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 CKItBRUAap-E for <sidr@ietfa.amsl.com>; Mon, 14 Apr 2014 08:24:57 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id BB2581A02C7 for <sidr@ietf.org>; Mon, 14 Apr 2014 08:24:56 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id c11so5841933lbj.31 for <sidr@ietf.org>; Mon, 14 Apr 2014 08:24:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=dqFe2YMeeZ5GQ13VIApV0WNx5W3nDFSGFl0WGe9QKys=; b=iocGbinvZrx2HK2Hw8DQeR66jwKW73hAbKjqTPdHQK0AJ9VDJ0i3mKqkV/8XRvA/Q8 2pw7Sg2CF3S5R8+2G86gTNPuPO4FipWf20WLnWm7Iw0oWIvDt6y51NuCYperG6cftG2s WAEMVI9cEG9x0Fi69EHdz8PBWafME5teYlRRoUO7ofcjxXz6crxJosp4wOpxgY38bAP9 Un/CVm72yAyAmUBYWbDLFROcB8X1luuPkVRAXZ8CYGCRH1FqWnSwdwU9Jwk1OikIk5nE Ufw40k5DdO5lwOGS7CbcAzQhIVvNhQ/8rdFoHxXYknO6/Ev6nMJxRRLUktVASkwxDeXS fJtw==
MIME-Version: 1.0
X-Received: by 10.152.4.201 with SMTP id m9mr838003lam.61.1397489093455; Mon, 14 Apr 2014 08:24:53 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.45.196 with HTTP; Mon, 14 Apr 2014 08:24:53 -0700 (PDT)
In-Reply-To: <m2tx9wdkh1.wl%randy@psg.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> <m2tx9wdkh1.wl%randy@psg.com>
Date: Mon, 14 Apr 2014 11:24:53 -0400
X-Google-Sender-Auth: GwlHdZeeAKji0gBA39SR0IxaARc
Message-ID: <CAL9jLaZ+tpD52=BkWB-D+doschxixi8brL2gdifufbdY3zPQ3A@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/TUA9eski7hi8sPpCA-sfBrd7tcY
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 15:24:58 -0000

On Mon, Apr 14, 2014 at 11:00 AM, Randy Bush <randy@psg.com> wrote:
> while checking the docco, i found
>
>    3.14  While the trust level of a route should be determined by the
>          BGPsec protocol, local routing preference and policy MUST then
>          be applied to best path and other routing decisions.  Such
>          mechanisms SHOULD conform with [I-D.ietf-sidr-ltamgmt].
> ...
>    3.17  If a BGPsec design makes use of a security infrastructure, that
>          infrastructure SHOULD enable each network operator to select
>          the entities it will trust when authenticating data in the
>          security infrastructure.  See, for example,
>          [I-D.ietf-sidr-ltamgmt].
>
> those references would seem to be obe.  dunno what to do with the first,
> drop it?  the second might ref lta-use-cases.

losing the last sentence in the first seems ok.
and the second moving to use-cases seems ok to me...

-chris

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