IETF Logo Mail Archive

Re: [netmod] rfcstrip does not work on https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-12

Kent Watsen <kent@watsen.net> Mon, 30 March 2020 23:47 UTC

Return-Path: <010001712dd7864e-c179c424-9424-4fc3-acb5-1bc0cc23041f-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 6803F3A15C5 for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 16:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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 5k6tLCBq22eV for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 16:47:13 -0700 (PDT)
Received: from a48-94.smtp-out.amazonses.com (a48-94.smtp-out.amazonses.com [54.240.48.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAB7A3A15C3 for <netmod@ietf.org>; Mon, 30 Mar 2020 16:47:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1585612031; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=QhfcuvuTwponjaJDkVV2kgO0+9N1bliIPebja5Q24sU=; b=A36i4k8Hn41QEsy6yMgwwbYJQZi8X2s/5k7jZ4Hewnm9tVxXnr5yH6O/v4QIeVA2 fiX3A77i2WJcCPgDbkm+IoyAc9teJRUEnlX9r3nM166zwePrjb4U7mg4mpmV3/MIHGj sQ+Dz+V6N35vkyG6yUZe66vC+igpNIwFfrbRdQW0=
From: Kent Watsen <kent@watsen.net>
Message-ID: <010001712dd7864e-c179c424-9424-4fc3-acb5-1bc0cc23041f-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_92CFEC22-2EE6-4216-8A86-43EB1F7C6F33"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 30 Mar 2020 23:47:11 +0000
In-Reply-To: <70e30e73-983c-8c60-d7dc-4ae863363fe2@unix-ag.uni-kl.de>
Cc: Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
To: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
References: <DB7PR07MB4011D9AAE36903D951C86C7EF0CC0@DB7PR07MB4011.eurprd07.prod.outlook.com> <010001711d349b01-d87da5d4-0638-4d76-aaf2-a6b94d777685-000000@email.amazonses.com> <70e30e73-983c-8c60-d7dc-4ae863363fe2@unix-ag.uni-kl.de>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2020.03.30-54.240.48.94
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/4q55aS6_5rH-ZF-fVZsUKtu1tns>
Subject: Re: [netmod] rfcstrip does not work on https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-12
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: Mon, 30 Mar 2020 23:47:14 -0000

Erik,

I can’t find a definition.

I thought someone said that `xml2rfc` was going to support a “markers” attribute for the <sourcecode> element, but I don’t see that here yet: https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/blob/master/draft-iab-rfc7991bis.xml#L8514 <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/blob/master/draft-iab-rfc7991bis.xml#L8514>.

Kent



> On Mar 30, 2020, at 6:22 AM, Erik Auerswald <auerswal@unix-ag.uni-kl.de> wrote:
> 
> Hi Kent, Balázs,
> 
> On 27.03.20 19:15, Kent Watsen wrote:
>>> On Mar 27, 2020, at 1:36 PM, Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org> wrote:
>>> 
>>> https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-12 <https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-12> contains a section with <CODE BEGINS> <CODE ENS>.
>> Looking at -12, I see "<CODE ENDS>” (not <CODE ENS>), is this just a typo in your message?
>>> However rfcstrip cannot extract this part. Is that a problem?
>> It seems that the <CODE BEGINS> line is messed up:
>> OLD:
>>    <CODE BEGINS>
>> NEW:
>>    <CODE BEGINS> file "rfcfold"
>> Fixes it.
> 
> Do you know of a written explanation on how to use the <CODE BEGINS> ...
> <CODE ENDS> markers?  I tried to find one without success.  I found only
> usage hints, and the licensing connection.
> 
> RFC 8407 says:
> 
>    The "<CODE BEGINS>" tag SHOULD be followed by a string identifying
>    the file name specified in Section 5.2 of [RFC7950]."
> 
> The predecessor RFC 6087 contains similar text.  Thus it seems the
> netmod WG convention is to specify a file name.  The rfcstrip utility
> mentioned in RFC 8407 requires the file name, although the file name
> seems to be optional.
> 
> But some RFCs do not specify a file name for code sections.  Some
> random examples are RFC 5662, RFC 6287, RFC 7861, and RFC 8290. Those
> are from WGs other than netmod, though.
> 
> Just curious. :-)
> 
> Thanks,
> Erik
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

v2.23.0 | Report a Bug | By Email