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 <> Fri, 02 August 2019 19:15 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CC63712014F; Fri, 2 Aug 2019 12:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id isCVpUnfwk96; Fri, 2 Aug 2019 12:15:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by (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;; 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 <>
Message-ID: <>
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, 02 Aug 2019 19:15:13 +0000
In-Reply-To: <>
Cc: Erik Auerswald <>, Ignas Bagdonas <>, "" <>,, IETF discussion list <>, "" <>
To: Paul Kyzivat <>
References: <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.08.02-
Archived-At: <>
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-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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. <>

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

Kent // as co-author