Re: [netmod] Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice

Kent Watsen <kent@watsen.net> Fri, 02 August 2019 19:15 UTC

Return-Path: <0100016c53c1e9f1-83ffddb3-1a59-4deb-b08a-1e16869eb8f2-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 CC63712014F; Fri, 2 Aug 2019 12:15:16 -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, SPF_HELO_NONE=0.001, SPF_NONE=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 isCVpUnfwk96; Fri, 2 Aug 2019 12:15:14 -0700 (PDT)
Received: from a8-32.smtp-out.amazonses.com (a8-32.smtp-out.amazonses.com [54.240.8.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58E821200E9; Fri, 2 Aug 2019 12:15:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1564773313; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=yW+Qq/WlXuXPKD0iHgPiP7wgXAzUORVkJpHeaUv84N8=; b=PpOFjVunervMxYCRzzKzjEYUNVBY/haqUY/EQeZ7RZWcuM3xGtr9u6KPvZEiP83K UFHOuVtwmys5Y1snfcbN2KaNdrTKLBMdmMOV6V8SXfioiChgOffnoUolsu+mNe/go4q wCabx3Fra56uSKNDonfUIUPzy5FXgDOEIrQ1DSA0=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100016c53c1e9f1-83ffddb3-1a59-4deb-b08a-1e16869eb8f2-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4703C420-ED37-4888-BC66-2B089870853E"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 2 Aug 2019 19:15:13 +0000
In-Reply-To: <a1b26190-ab74-01f5-bad6-8e09c696bca6@alum.mit.edu>
Cc: Erik Auerswald <auerswal@unix-ag.uni-kl.de>, Ignas Bagdonas <ibagdona@gmail.com>, "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, draft-ietf-netmod-artwork-folding@ietf.org, IETF discussion list <ietf@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <156451937390.14101.5438428659513611953.idtracker@ietfa.amsl.com> <1e399e65-4cc9-1e46-018f-5d6427e953c9@alum.mit.edu> <0100016c498d2a40-f6b9bf13-15c9-4d20-9be2-bea7147d60e5-000000@email.amazonses.com> <53836925-6f9a-0c04-28fd-4471328db345@alum.mit.edu> <99a7009d-7ec4-f4b1-c157-961f2566a6ad@unix-ag.uni-kl.de> <a1b26190-ab74-01f5-bad6-8e09c696bca6@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.08.02-54.240.8.32
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ScMxHgX5m-Ezrt2sVy4VUzBXA50>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-artwork-folding-07.txt> (Handling Long Lines in Inclusions in Internet-Drafts and RFCs) to Best Current Practice
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: Fri, 02 Aug 2019 19:15:17 -0000

Hi Paul,

> But now that I am thinking about this, it occurs to me that maybe the two methods can be collapsed into one:
> 
> just make the sequence to be inserted for folding be (using ABNF):
> 
> "\" %x0C [%x0A] *" " ["\"]
> 
> The trailing backslash only needs to be inserted if the character following it is a space or backslash. (IOW it is *optional* if the next character is *not* space or backslash.)
> 
> So, when removing the folding, upon finding ("\" %x0C [%x0A] *" ") you remove that and if there is then a backslash remove that too.


Are you suggesting a hybrid approach where, within a folded file, a line may be folded one way one the other based on context?  Would that detract from readability?

FWIW, I just posted -08 that adds forced-folding support to the single-backslash strategy as well as a couple forced folding examples.   

	https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-08 <https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-08>

Thank you for requesting these examples, as an issue in the `rfcfold` script was found and fixed.

Kent // as co-author