Re: [sidr] Alissa Cooper's Discuss on draft-ietf-sidr-rpki-oob-setup-06: (with DISCUSS and COMMENT)

Rob Austein <sra@hactrn.net> Wed, 22 February 2017 20:50 UTC

Return-Path: <sra@hactrn.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 228AE129B13; Wed, 22 Feb 2017 12:50:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, 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 Vp9LnT9gl7xO; Wed, 22 Feb 2017 12:50:10 -0800 (PST)
Received: from khatovar.hactrn.net (khatovar.hactrn.net [IPv6:2001:418:8006::30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9C6A129A66; Wed, 22 Feb 2017 12:50:10 -0800 (PST)
Received: from minas-ithil.hactrn.net (c-73-30-72-201.hsd1.pa.comcast.net [73.30.72.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nargothrond.hactrn.net", Issuer "Grunchweather Associates" (not verified)) by khatovar.hactrn.net (Postfix) with ESMTPS id E34D0139A2; Wed, 22 Feb 2017 20:50:08 +0000 (UTC)
Received: from minas-ithil.hactrn.net (localhost [IPv6:::1]) by minas-ithil.hactrn.net (Postfix) with ESMTP id 4885347B558D; Wed, 22 Feb 2017 15:50:12 -0500 (EST)
Date: Wed, 22 Feb 2017 15:50:12 -0500
From: Rob Austein <sra@hactrn.net>
To: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <6B4349F8-F5CD-4E90-8706-831FB6BB5D72@cooperw.in>
References: <148467602955.32082.12289843566112325669.idtracker@ietfa.amsl.com> <6549BAF8-95A7-42C6-A8E6-A80754DB2867@cisco.com> <F95A3287-C1F6-4BE1-840F-683DDF045ECE@cooperw.in> <20170209231225.802F2468503F@minas-ithil.hactrn.net> <6B4349F8-F5CD-4E90-8706-831FB6BB5D72@cooperw.in>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20170222205012.4885347B558D@minas-ithil.hactrn.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/D5BUZTtldu1pn3askFsYmxGu-LQ>
Cc: Rob Austein <sra@hactrn.net>, Chris Morrow <morrowc@ops-netman.net>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, IESG <iesg@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>, "draft-ietf-sidr-rpki-oob-setup@ietf.org" <draft-ietf-sidr-rpki-oob-setup@ietf.org>
Subject: Re: [sidr] Alissa Cooper's Discuss on draft-ietf-sidr-rpki-oob-setup-06: (with DISCUSS and 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, 22 Feb 2017 20:50:14 -0000

At Wed, 22 Feb 2017 14:25:12 -0500, Alissa Cooper wrote:
> > On Feb 9, 2017, at 6:12 PM, Rob Austein <sra@hactrn.net>; wrote:
> > 
> > Sorry, missed this part:
> > 
> > At Wed, 8 Feb 2017 10:03:32 -0500, Alissa Cooper wrote:
> >>>> ----------------------------------------------------------------------
> >>>> DISCUSS:
> >>>> ----------------------------------------------------------------------
> >>>> 
> >>>> (2) If there is in fact supposed to be a protocol specified here, I have
> >>>> the same question as I had on draft-ietf-sidr-publication, which is how
> >>>> do the entities migrate from one version to another and do version
> >>>> negotiation?
> > 
> > Essentially the same answer as for draft-ietf-sidr-publication, so
> > will include some variation of same text if that's acceptable.
> 
> That would do the trick. Thanks.

Whoops, then I went and lost having promised to fix this in -07 just
like I missed the original issue the first time.  Consistency is not
always a good thing.  Sigh.  Sorry.

Since this was a DISCUSS rather than just a COMMENT I'm assuming that
there will be no objection to uploading a -08 now with the fix, so I
will do that immediately after posting this.