Re: [sidr] AD Review of draft-ietf-sidr-rpki-validation-reconsidered-07

Tim Bruijnzeels <tim@ripe.net> Thu, 22 June 2017 09:26 UTC

Return-Path: <tim@ripe.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 1E5BA1294DC; Thu, 22 Jun 2017 02:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 lBXAxkJYWjRi; Thu, 22 Jun 2017 02:26:57 -0700 (PDT)
Received: from mahimahi.ripe.net (mahimahi.ripe.net [IPv6:2001:67c:2e8:11::c100:1372]) (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 4318C1292FD; Thu, 22 Jun 2017 02:26:57 -0700 (PDT)
Received: from titi.ripe.net ([193.0.23.11]) by mahimahi.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <tim@ripe.net>) id 1dNyO5-0007Jr-WE; Thu, 22 Jun 2017 11:26:54 +0200
Received: from sslvpn.ripe.net ([193.0.20.230] helo=vpn-45.ripe.net) by titi.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <tim@ripe.net>) id 1dNyO5-00087T-PL; Thu, 22 Jun 2017 11:26:53 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Tim Bruijnzeels <tim@ripe.net>
In-Reply-To: <5C70CE73-FEC7-4592-AF31-90B2664A9144@cisco.com>
Date: Thu, 22 Jun 2017 11:26:52 +0200
Cc: "draft-ietf-sidr-rpki-validation-reconsidered@ietf.org" <draft-ietf-sidr-rpki-validation-reconsidered@ietf.org>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>, Chris Morrow <morrowc@ops-netman.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6FD8D6D-DCA5-4908-8CB8-BB6921A6B1CD@ripe.net>
References: <5821A5CF-EFF8-4CE3-9AA4-CFDB9C903D63@cisco.com> <20170311222527.324125ACF21@minas-ithil.hactrn.net> <yj9ok27upcws.wl%morrowc@ops-netman.net> <6359B4B1-478D-4017-B259-7B60BA55FF39@zdns.cn> <68C71545-48E4-40B8-91AC-88DE44C4125D@ripe.net> <yj9ozigpz299.wl%morrowc@ops-netman.net> <8C26566E-8E22-4D35-85E1-387BA980115E@ripe.net> <C1D1FDD2-9892-4EE0-86FF-24F412AF6669@cisco.com> <DDA98C9A-F765-4922-A11B-52470A8AD2E1@ripe.net> <5C70CE73-FEC7-4592-AF31-90B2664A9144@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
X-Mailer: Apple Mail (2.3273)
X-ACL-Warn: Delaying message
X-RIPE-Spam-Level: -------
X-RIPE-Spam-Report: Spam Total Points: -7.5 points pts rule name description ---- ---------------------- ------------------------------------ -7.5 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
X-RIPE-Signature: 784d7acfe6559f2a0b602ec6519a0719f0f13221b56bf6493e02826335416f73
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/L4gFSPCRpMIaffe-u3fJYUyQKTY>
Subject: Re: [sidr] AD Review of draft-ietf-sidr-rpki-validation-reconsidered-07
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: Thu, 22 Jun 2017 09:26:59 -0000

> On 22 Jun 2017, at 11:24, Alvaro Retana (aretana) <aretana@cisco.com> wrote:
> 
> On 6/22/17, 10:36 AM, "Tim Bruijnzeels" <tim@ripe.net> wrote:
> 
> Tim:
> 
> Hi!
> 
>> All that said I will work on an update of this document following 
>> Alvaro’s review. This document will define an additional validation 
>> algorithm, but not update the existing one. We can finish this work 
>> first and then have a structured discussion about deployment - I 
>> propose that we take this work to SIDROPS.
> 
> I’m assuming that you mean: finish draft-ietf-sidr-rpki-validation-reconsidered in sidr (i.e. publish as an RFC) and then further discuss deployment in sidrops, right?

yes

> 
>> I canceled all my meetings today so I should have updated text to 
>> share with my co-authors soon. Will then send a new version to 
>> the WG asap.
> 
> Just a procedure note:  Even though there should be a good number of changes, I don’t think we need to run the result through the WG (as in a new WGLC).  I’m happy to allow time for anyone to comment further, either now or during IETF LC.  I just rather not officially send the document back to the WG.

Works for me

> 
> Thanks!
> 
> Alvaro.
> 
> 
>