Re: [sidr] Alexey Melnikov's Discuss on draft-ietf-sidr-publication-10: (with DISCUSS and COMMENT)

Rob Austein <sra@hactrn.net> Tue, 31 January 2017 00:14 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 8AE1F1296F3; Mon, 30 Jan 2017 16:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.1
X-Spam-Level:
X-Spam-Status: No, score=-5.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, 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 h-nNMAjD05qK; Mon, 30 Jan 2017 16:14:06 -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 3B4B41296EA; Mon, 30 Jan 2017 16:13:59 -0800 (PST)
Received: from minas-ithil.hactrn.net (c-73-47-197-23.hsd1.ma.comcast.net [73.47.197.23]) (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 97AF11398C; Tue, 31 Jan 2017 00:13:57 +0000 (UTC)
Received: from minas-ithil.hactrn.net (localhost [IPv6:::1]) by minas-ithil.hactrn.net (Postfix) with ESMTP id 2DFE04664F1A; Mon, 30 Jan 2017 19:13:21 -0500 (EST)
Date: Mon, 30 Jan 2017 19:13:20 -0500
From: Rob Austein <sra@hactrn.net>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
In-Reply-To: <148442017790.24124.2732462706586628755.idtracker@ietfa.amsl.com>
References: <148442017790.24124.2732462706586628755.idtracker@ietfa.amsl.com>
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: <20170131001321.2DFE04664F1A@minas-ithil.hactrn.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/htMogoRB2nDp7e11U4GfmORjq6A>
Cc: morrowc@ops-netman.net, sidr-chairs@ietf.org, draft-ietf-sidr-publication@ietf.org, The IESG <iesg@ietf.org>, sidr@ietf.org
Subject: Re: [sidr] Alexey Melnikov's Discuss on draft-ietf-sidr-publication-10: (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: Tue, 31 Jan 2017 00:14:07 -0000

[Sorry for delay, was out for a while with a nasty flu, still catching up.]

At Sat, 14 Jan 2017 10:56:17 -0800, Alexey Melnikov wrote:
...
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> I find the document to be a bit short on normative references and some
> implementation details. Other than that the document looks fine. My
> specific questions and concern are as follows:
> 
> 1) Please add a normative reference for HTTP, URI and RelaxNG on first
> use.

Added, will be in -11

> 2) Base64 needs a normative reference (including the section number, as
> there are 2 variants).

Added, will be in -11.

> 3) Section 2 says that all payloads use CMS. None of your examples show
> CMS. Can you please elaborate on how CMS is used.

The short version is already in the running text (section "Protocol
Specification" describes the CMS wrapping).   Not shown in examples
because CMS is, um, rather verbose, and looks like dog food.

A full-blown exposition on use of CMS would look like RFC 6492 section
3.1 ("CMS Profile") and all of its subsections.  Sure you want that?

Should we incorporate RFC 6492 3.1 by reference?

> 4) How can URI of the service be discovered?

Out of scope, but draft-ietf-sidr-oob-setup would be one way.

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> In 2.5: is the list of error reasons extensible?

Probably, given sufficient cause.

> Was Relax NG schema validated with a tool?

Yes, using trang and xmllint.

> In Section 5 you should reference the document, as IANA registrations cut
> & pasted to IANA website as separate files.

Would be happy to do so but does not appear to be on IANA website.
Chicken and egg problem?  Leave for RFC Editor?