Re: [sidr] Stephen Farrell's No Objection on draft-ietf-sidr-bgpsec-ops-13: (with COMMENT)

Randy Bush <randy@psg.com> Wed, 04 January 2017 16:48 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 117C01299C1; Wed, 4 Jan 2017 08:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.001
X-Spam-Level:
X-Spam-Status: No, score=-10.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.1, 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 AZRFhndIssJL; Wed, 4 Jan 2017 08:48:22 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3535B1299C0; Wed, 4 Jan 2017 08:48:22 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cOoja-0002PF-Hz; Wed, 04 Jan 2017 16:48:18 +0000
Date: Thu, 05 Jan 2017 01:48:17 +0900
Message-ID: <m2h95elqjy.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
In-Reply-To: <fe9d214a-a4a8-1534-e9c1-fe7068b4ed2f@cs.tcd.ie>
References: <148353764984.13034.8506727126675155642.idtracker@ietfa.amsl.com> <m2mvf6lti7.wl-randy@psg.com> <fe9d214a-a4a8-1534-e9c1-fe7068b4ed2f@cs.tcd.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 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/sidr/qH_0dFigbBu76zHbOF5SEIvZ1Yw>
Cc: The IESG <iesg@ietf.org>, sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Stephen Farrell's No Objection on draft-ietf-sidr-bgpsec-ops-13: (with COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 04 Jan 2017 16:48:23 -0000

>    As core BGPsec-capable routers may require large memory and/or modern
>    CPUs, origin validation based on the Resource Public Key
>    Infrastructure (RPKI), [RFC6811], will occur over some years and,
>    once origin validation has been deployed at an AS, then BGPsec
>    can start to deploy in that AS.
> 
> Though I'm not sure that's precisely right either.

let me get back to this tomorrow with coffee.

> And to be sure to be sure, none of the above should be blocking
> and do feel entirely free to not make any of these changes if
> you'd rather not.

i made the ones i said i was making, which was most.

randy