[sidr] Mirja Kühlewind's No Objection on draft-ietf-sidr-rpki-oob-setup-06: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Mon, 16 January 2017 13:01 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: sidr@ietf.org
Delivered-To: sidr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E72F1299D7; Mon, 16 Jan 2017 05:01:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148457170764.22584.8933948525563491675.idtracker@ietfa.amsl.com>
Date: Mon, 16 Jan 2017 05:01:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/fge7nTTPdZNTYBdSuWyPKz_cePI>
Cc: morrowc@ops-netman.net, sidr-chairs@ietf.org, draft-ietf-sidr-rpki-oob-setup@ietf.org, sidr@ietf.org
Subject: [sidr] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-sidr-rpki-oob-setup-06=3A_=28with_COMMENT=29?=
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 16 Jan 2017 13:01:47 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-sidr-rpki-oob-setup-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sidr-rpki-oob-setup/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

High level comment:
I'm not sure if 'protocol' is the right term for this spec. For me this
doc rather defines a set of messages, however given it does  not specify
any action that must follow as a reaction to a message (as well as no
choice of the publication nor BPKI protocol), I find the term 'protocol'
here rather confusing.

Smaller comments:
- Some more abbreviations could be spelled out, e.g. CMS
- section 2 is not needed
- sec 5: "Appendix A is a [RelaxNG] schema for this protocol.  The schema
is
   normative: in the event of a disagreement between the schema and the
   following textual description, the schema is authoritative."
   I guess in this case the schema should not be in the appendix. And
would it be possible to make sure the schema does not disagree with the
text...?