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

Alissa Cooper <alissa@cooperw.in> Wed, 08 February 2017 15:03 UTC

Return-Path: <alissa@cooperw.in>
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 32562129B93; Wed, 8 Feb 2017 07:03:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=ZDvegnLU; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=GdxZ+MTp
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 Gbh7kQptBYq2; Wed, 8 Feb 2017 07:03:37 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30B9E129B81; Wed, 8 Feb 2017 07:03:34 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 93A85206C9; Wed, 8 Feb 2017 10:03:33 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 08 Feb 2017 10:03:33 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=yCuOs7jYziZLULZnuTHW+MOSmco=; b=ZDvegn LUTWHefJ+hhXjYdokDw0Bm3q307bfJuzM+9Jg3a3uYtW1mZUgxXi0KHdphEf/hFG NQhbXvFwKS8ZigoPM2Ev8MhQuMY4JyKOWgtxbqRwji/9QD7ZIyw3RmmV/6+xXizH Xhc5cZ3eSJ0jNmmyhnxaqD5HgZ7pP9Nqcqu84=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=yCuOs7jYziZLUL ZnuTHW+MOSmco=; b=GdxZ+MTpqn7y23w8xTrnUBEuFNMfjsra1WE+pu0xiEgfRc wNZb8HOUkNapIQ2ElDgGjxS0GJIUZJRbCROKgoBqgTBtoZoYuEsdLcEh6af8Lszx EwL2DTRWSLqgCn1Pb0MENrWSppmL20W3cAehzl4AJtBU+1TYq1n00ksIFKt5s=
X-ME-Sender: <xms:RTObWIUYog7PY-BlFCNRChGFo19hIabfHsTGbwNCwnPj--y_a8BmiQ>
X-Sasl-enc: qrUpfa/naqBFqoqX86gMospw/HkXy+vHbVPOQbZlorOT 1486566213
Received: from sjc-alcoop-8812.cisco.com (unknown [128.107.241.186]) by mail.messagingengine.com (Postfix) with ESMTPA id 230B624641; Wed, 8 Feb 2017 10:03:31 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8442B271-A476-4EEE-B31E-AA0F328F2DE8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <6549BAF8-95A7-42C6-A8E6-A80754DB2867@cisco.com>
Date: Wed, 8 Feb 2017 10:03:32 -0500
Message-Id: <F95A3287-C1F6-4BE1-840F-683DDF045ECE@cooperw.in>
References: <148467602955.32082.12289843566112325669.idtracker@ietfa.amsl.com> <6549BAF8-95A7-42C6-A8E6-A80754DB2867@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/olUC-vhPmDnGckWgPs9wW-ztOds>
Cc: Chris Morrow <morrowc@ops-netman.net>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, IESG <iesg@ietf.org>, "draft-ietf-sidr-rpki-oob-setup@ietf.org" <draft-ietf-sidr-rpki-oob-setup@ietf.org>, "sidr@ietf.org" <sidr@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, 08 Feb 2017 15:03:38 -0000

> On Jan 19, 2017, at 9:34 AM, Alvaro Retana (aretana) <aretana@cisco.com>; wrote:
> 
> Hi!
>  
> I was going to wait for the author, but he has been out sick this week… L
>  
> Picking up from Benoit’s comment – the use of “protocol” is misleading.  What is described is a process that can be followed and the necessary information exchanged “to simplify configuration…by setting up relationships and exchanging keying material used to authenticate those relationships.”

Is this going to be clarified in the document?

Thanks,
Alissa

>  
> Thanks!
>  
> Alvaro.
>  
>> On 1/17/17, 1:00 PM, "Alissa Cooper" <alissa@cooperw.in <mailto:alissa@cooperw.in>> wrote:
>>  
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>  
>> (1) I agree with Mirja that this document seems to be missing the actual
>> protocol specification, unless Section 6 is meant to provide the
>> normative specification of how the messages are to be exchanged. Is it?
>> If so, I would expect that to be explicit in the document.
>>  
>> (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?
>>