RFC 8792: Handling Long Lines in Content of Internet-Drafts and RFCs
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8792
- Published
- June 2020
- Authors
- K. Watsen; E. Auerswald; A. Farrel; Q. Wu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8791YANG Data Structure ExtensionsCurrent
June 2020
- RFC 8806Running a Root Server Local to a ResolverCurrent
June 2020
- RFC 8807Login Security Extension for the Extensible Provisioning Protocol (EPP)Current
August 2020
- RFC 8777DNS Reverse IP Automatic Multicast Tunneling (AMT) DiscoveryCurrent
April 2020
- RFC 8808A YANG Data Model for Factory Default SettingsCurrent
August 2020
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
- RFC 8767Serving Stale Data to Improve DNS ResiliencyCurrent
March 2020
- RFC 8819YANG Module TagsCurrent
January 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?