Re: [netmod] Roman Danyliw's No Objection on draft-ietf-netmod-artwork-folding-09: (with COMMENT)

Kent Watsen <kent+ietf@watsen.net> Wed, 04 September 2019 18:55 UTC

Return-Path: <0100016cfda15fcf-3dfee6d4-dbfd-4ef4-8fcf-425cf412f924-000000@amazonses.watsen.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1078120BD6; Wed, 4 Sep 2019 11:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 mj62da4tmCwn; Wed, 4 Sep 2019 11:55:09 -0700 (PDT)
Received: from a8-31.smtp-out.amazonses.com (a8-31.smtp-out.amazonses.com [54.240.8.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D50A4120BB4; Wed, 4 Sep 2019 11:55:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1567623307; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=ijvJ7Exk0TLh2N0gjsjEJqrt4wAnK+df45dnucoK7ZE=; b=Bf1+O20PM5SLvrcGzDuqinKvZIgItt4VteWINVTqKYq+O1Y48S39VWxP+jAQZfQz +3Tw6e1thswGK21EQ2SHr1oEJ33PPl2zySCqa98+YjTVvzFIOhC1rnkSXVF7nxUtOsx vbmOxyqHfeLZ0/kdQi6d2cCwK8NUg4P9IkNskrbw=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016cfda15fcf-3dfee6d4-dbfd-4ef4-8fcf-425cf412f924-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D6881309-A6D9-48A4-B94C-633C237E5A56"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 4 Sep 2019 18:55:07 +0000
In-Reply-To: <156761980945.22719.16082541805323491673.idtracker@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-netmod-artwork-folding@ietf.org, Lou Berger <lberger@labn.net>, "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
To: Roman Danyliw <rdd@cert.org>
References: <156761980945.22719.16082541805323491673.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.09.04-54.240.8.31
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/cTEQdECndMe2Vq522f4hUIlE9kw>
Subject: Re: [netmod] Roman Danyliw's No Objection on draft-ietf-netmod-artwork-folding-09: (with COMMENT)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2019 18:55:12 -0000

Hi Roman,

Thanks for your review.  I'll prepare an update accounting for your (and Adam's) comments shortly. 

First, I have a couple questions:


> (1) Section 1.  To make this document more enduring, Ib
> the capabilities of xml2rfc  (i.e., no line wrapping is done) to a version
> number.

Do you mean, e.g., s/ The `xml2rfc` utility / The `xml2rfc` utility, at least up until the time of this document's publication, / ???

[BTW, I just noticed that `xml2rfc` needs a reference...I'll point it to https://pypi.org/project/xml2rfc <https://pypi.org/project/xml2rfc>]


> (2) Section 2. Is it worth saying that in addition to the primary target being
> <sourcecode> and <artwork> (xml2rfc tags), it is also anything authors
> currently put between b
> using xml tooling for rendering the draft)?

I think that the word "primarily" already provides the flexibility to use it in other contexts.  That said, I don't know what other `xml2rfc` context exists currently, or do you a future version of the `xml2rfc` specification or, perhaps, a `foo2rfc` specification?  In either case, could you provide a snippet of what you'd like to see?



Thanks again,
Kent