IETF Logo Mail Archive

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

Erik Auerswald <auerswal@unix-ag.uni-kl.de> Mon, 30 March 2020 10:23 UTC

Return-Path: <auerswal@unix-ag.uni-kl.de>
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 E65CC3A1294 for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 03:23: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=[MAY_BE_FORGED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 JCUbzrWG-noN for <netmod@ietfa.amsl.com>; Mon, 30 Mar 2020 03:23:13 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D5EB3A1296 for <netmod@ietf.org>; Mon, 30 Mar 2020 03:23:13 -0700 (PDT)
Received: from [172.20.10.2] (x2e7203b4.dyn.telefonica.de [46.114.3.180] (may be forged)) (authenticated bits=0) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 02UAMt6m036482 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Mar 2020 12:23:06 +0200
To: Kent Watsen <kent@watsen.net>, Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org>
Cc: "netmod@ietf.org" <netmod@ietf.org>
References: <DB7PR07MB4011D9AAE36903D951C86C7EF0CC0@DB7PR07MB4011.eurprd07.prod.outlook.com> <010001711d349b01-d87da5d4-0638-4d76-aaf2-a6b94d777685-000000@email.amazonses.com>
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Message-ID: <70e30e73-983c-8c60-d7dc-4ae863363fe2@unix-ag.uni-kl.de>
Date: Mon, 30 Mar 2020 12:22:55 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <010001711d349b01-d87da5d4-0638-4d76-aaf2-a6b94d777685-000000@email.amazonses.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/6P2VGdmWs-kA_PXi3i4rvDDx_Hc>
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 10:23:15 -0000

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

v2.23.0 | Report a Bug | By Email