Re: [sidr] WGLC: draft-ietf-sidr-rtr-keying - finishes - 10/16/2017 - Oct 16, 2017

Di Ma <madi@rpstir.net> Sat, 07 October 2017 02:02 UTC

Return-Path: <madi@rpstir.net>
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 88B1213219C; Fri, 6 Oct 2017 19:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 KULgyA0VO6rU; Fri, 6 Oct 2017 19:02:30 -0700 (PDT)
Received: from out20-38.mail.aliyun.com (out20-38.mail.aliyun.com [115.124.20.38]) (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 EF03E132125; Fri, 6 Oct 2017 19:02:28 -0700 (PDT)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.07242032|-1; FP=0|0|0|0|0|-1|-1|-1; HT=e02c03310; MF=madi@rpstir.net; NM=1; PH=DS; RN=6; RT=6; SR=0; TI=SMTPD_---.93eJPkS_1507341744;
Received: from 192.168.3.3(mailfrom:madi@rpstir.net ip:118.247.20.217) by smtp.aliyun-inc.com(10.147.41.138); Sat, 07 Oct 2017 10:02:25 +0800
Content-Type: text/plain; charset=gb2312
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Di Ma <madi@rpstir.net>
In-Reply-To: <3EECD8A0-03BE-42D8-9C93-7420EE205EEF@sn3rd.com>
Date: Sat, 7 Oct 2017 10:02:51 +0800
Cc: Tim Bruijnzeels <tim@ripe.net>, sidr-ads@ietf.org, Christopher Morrow <christopher.morrow@gmail.com>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <51178B8F-44D6-4E14-B491-6A88C96FE6F5@rpstir.net>
References: <CAL9jLaYXK4vLGtNgqs_ofPmEBez=AmrgD+dPwUhG-=A_NHokTg@mail.gmail.com> <470CB4A7-8639-4889-AF51-C0B8B4CCA4C9@ripe.net> <3EECD8A0-03BE-42D8-9C93-7420EE205EEF@sn3rd.com>
To: Sean Turner <sean@sn3rd.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/awoooXKekbZOLXwVThztE81e4lU>
Subject: Re: [sidr] WGLC: draft-ietf-sidr-rtr-keying - finishes - 10/16/2017 - Oct 16, 2017
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 07 Oct 2017 02:02:33 -0000

I think this document is ready to go through IESG review.

Ship it.

Di


> 在 2017年10月6日,02:36,Sean Turner <sean@sn3rd.com> 写道:
> 
> Always happy to see the “ship it” response to a WGLC :)
> 
> Note that we weren’t restrictive on purpose.   There’s a whole bunch of ways how the CSR could get delivered based on where it was made and it would be silly for us to have said you must do it this way. 
> 
> spt
> 
>> On Oct 5, 2017, at 05:27, Tim Bruijnzeels <tim@ripe.net> wrote:
>> 
>> Hi,
>> 
>> This looks reasonable to me, but I can’t speak really to the router implementation - being neither a network operator nor a router vendor. As a CA operator I note that the draft is not restrictive about exactly how the RPKI CA gets the CSR, and the signed certificate is returned. That’s a good thing to me at this point, so I would say ship it. But I believe it would be good to keep this in mind in the sidr-ops WG - if this proves operationally difficult then it may be something to discuss further later.
>> 
>> Tim
>> 
>>> On 3 Oct 2017, at 05:14, Christopher Morrow <christopher.morrow@gmail.com> wrote:
>>> 
>>> WG Folk,
>>> I thought I had sent this note our previously, but... better late then never sent:
>>> 
>>> Please consider this the WGLC for:
>>> https://tools.ietf.org/html/draft-ietf-sidr-rtr-keying-13
>>> 
>>> Abstract:
>>> "BGPsec-speaking routers are provisioned with private keys in order to
>>>  sign BGPsec announcements.  The corresponding public keys are
>>>  published in the global Resource Public Key Infrastructure, enabling
>>>  verification of BGPsec messages.  This document describes two methods
>>>  of generating the public-private key-pairs: router-driven and
>>>  operator-driven."
>>> 
>>> Please send along comments/complaints/issues/kudos (to the authors), to the list and I'll see you all in ~14 or so days.
>>> 
>>> Thanks!
>>> -chris
>>> co-chair
>>> _______________________________________________
>>> sidr mailing list
>>> sidr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sidr
>> 
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
> 
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr