[netmod] RFC 8792 on Handling Long Lines in Content of Internet-Drafts and RFCs
rfc-editor@rfc-editor.org Mon, 29 June 2020 17:09 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 9CB263A0869; Mon, 29 Jun 2020 10:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 TQlqa12ZM26m; Mon, 29 Jun 2020 10:09:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D28B83A086D; Mon, 29 Jun 2020 10:09:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 071B2F40755; Mon, 29 Jun 2020 10:08:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, netmod@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200629170855.071B2F40755@rfc-editor.org>
Date: Mon, 29 Jun 2020 10:08:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ieEQJBchDGfwTX21srETur4HAkI>
Subject: [netmod] RFC 8792 on Handling Long Lines in Content of Internet-Drafts and RFCs
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, 29 Jun 2020 17:09:24 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8792 Title: Handling Long Lines in Content of Internet-Drafts and RFCs Author: K. Watsen, E. Auerswald, A. Farrel, Q. Wu Status: Informational Stream: IETF Date: June 2020 Mailbox: kent+ietf@watsen.net, auerswal@unix-ag.uni-kl.de, adrian@olddog.co.uk, bill.wu@huawei.com Pages: 28 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-netmod-artwork-folding-12.txt URL: https://www.rfc-editor.org/info/rfc8792 DOI: 10.17487/RFC8792 This document defines two strategies for handling long lines in width-bounded text content. One strategy, called the "single backslash" strategy, is based on the historical use of a single backslash ('') character to indicate where line-folding has occurred, with the continuation occurring with the first character that is not a space character (' ') on the next line. The second strategy, called the "double backslash" strategy, extends the first strategy by adding a second backslash character to identify where the continuation begins and is thereby able to handle cases not supported by the first strategy. Both strategies use a self-describing header enabling automated reconstitution of the original content. This document is a product of the Network Modeling Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC