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

Kent Watsen <kent+ietf@watsen.net> Tue, 31 March 2020 16:05 UTC

Return-Path: <010001713156ff08-ba75eac7-ed5d-4378-a23a-c3fa1d296725-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 E36FB3A238A for <netmod@ietfa.amsl.com>; Tue, 31 Mar 2020 09:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 uwRUcGZsPNOP for <netmod@ietfa.amsl.com>; Tue, 31 Mar 2020 09:05:18 -0700 (PDT)
Received: from a48-93.smtp-out.amazonses.com (a48-93.smtp-out.amazonses.com [54.240.48.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AF443A237B for <netmod@ietf.org>; Tue, 31 Mar 2020 09:05:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1585670717; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=AHIIvaF4fGCyqpxVFnsKZuJvNDtOvYS41QKytzYpaYQ=; b=CrqFg153hw9q72Jopv27MfRO7BbA6PhhJXgRhy5oHz4dBLBOIqI9DwfFY5fJ+Kzo wWresNxZhfW3y6q+ysG/pp6M61Tm2EVGrwSrK9vRlekpPnRA+KLjpsYBpL9Z+k/GKgw b9cZKcQ9kXB+cQWkUSHGJ+JJsazDGZ1WK+Ji0+5E=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <010001713156ff08-ba75eac7-ed5d-4378-a23a-c3fa1d296725-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2DFF8C91-E131-4642-89A6-CC481315F9F4"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 31 Mar 2020 16:05:17 +0000
In-Reply-To: <20200331.170449.1892418214423395231.id@4668.se>
Cc: auerswal@unix-ag.uni-kl.de, cabo@tzi.org, balazs.lengyel=40ericsson.com@dmarc.ietf.org, "netmod@ietf.org" <netmod@ietf.org>
To: =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>
References: <5F251832-0C47-4254-8A6E-8DEEA6CC7FBC@tzi.org> <DE6D0F27-B4DB-423E-80D7-63DA7F3D394A@tzi.org> <3e2333ce-d20a-60f7-3578-5199720a03d6@unix-ag.uni-kl.de> <20200331.170449.1892418214423395231.id@4668.se>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2020.03.31-54.240.48.93
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/hgtZd2aAWeiAgUyf1MhMeHBKf_g>
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: Tue, 31 Mar 2020 16:05:21 -0000

Hi Martin,

> Version 1.2 of rfcstrip (https://github.com/mbj4668/rfcstrip <https://github.com/mbj4668/rfcstrip>) can
> extract from the "artwork" element, and performs artwork unfolding, if
> needed.

Thanks for this update to rfcstrip!

If it’s not too late, may I suggest changing “-a” to “-x”?

Reasons:
   1) ‘a’ stands for “artwork” but, in the long run, we’ll only be striping out “sourcecode” elements
   2) ‘x’ could refer to the input format “XML” (as opposed to the default “txt” format)

Better, perhaps `rfcstrip` could automatically do the right thing, either by keying off the suffix (.xml vs .txt) or by first testing if the file contains XML?

Kent // contributor