Re: [Sidrops] Rtgdir last call review of draft-ietf-sidrops-lta-use-cases-05

Randy Bush <randy@psg.com> Thu, 18 April 2019 23:51 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C913812021C; Thu, 18 Apr 2019 16:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 34h6LUK90Na3; Thu, 18 Apr 2019 16:51:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C4EA12020A; Thu, 18 Apr 2019 16:51:08 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1hHGo6-0007Q2-55; Thu, 18 Apr 2019 23:51:06 +0000
Date: Thu, 18 Apr 2019 16:51:05 -0700
Message-ID: <m25zrarhxy.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stewart Bryant via Datatracker <noreply@ietf.org>
Cc: <rtg-dir@ietf.org>, sidrops@ietf.org
In-Reply-To: <155562409732.25526.1571500373372550686@ietfa.amsl.com>
References: <155562409732.25526.1571500373372550686@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/hkU5CunkPPTY1HLvTftWGPD5Rgg>
Subject: Re: [Sidrops] Rtgdir last call review of draft-ietf-sidrops-lta-use-cases-05
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 23:51:10 -0000

thanks stewart; review appreciated

> 6.  Security Considerations
> 
>    Though the above use cases are all constrained to local contexts,
>    they violate the model of a single global PKI, albeit to meet real
>    operational needs.  Hence they MUST be implemented to assure the
>    local constraint.
> 
> SB> I can see why RFC2119 language is used, and it seems correct to use it,
> however Nits is complaining that there is no RFC2119 boilerplate.

<doh>  will fix

>    [I-D.ietf-sidr-bgpsec-overview]
>               Lepinski, M. and S. Turner, "An Overview of BGPSEC",
>               draft-ietf-sidr-bgpsec-overview-02 (work in progress), May
>               2012.
> 
> SB> Nits asks if you mean this version or -08?

the ref is from pre ww2.  it's an rfc now.  will fix.

thanks again

randy