Re: [Rfc-markdown] [netmod] too long lines from IANA module inclusion

Kent Watsen <kent@watsen.net> Fri, 17 December 2021 16:31 UTC

Return-Path: <0100017dc93be244-843adcee-efda-49d4-9814-fbf91153126b-000000@amazonses.watsen.net>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E14BC3A0793; Fri, 17 Dec 2021 08:31:30 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 UMpo2KVeinBH; Fri, 17 Dec 2021 08:31:26 -0800 (PST)
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 8F5513A078F; Fri, 17 Dec 2021 08:31:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1639758685; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=ezijLfQKhQdIBzmCmWmlbWctjMPUh1edGRGe9KRqFko=; b=U7YKMDGepktz8bUnQorpfKwLwZWsV6bPxneo89hoojZU+DqkLKxEZ0uuvv2oUpAs 0VGFFdfMlYt9ptAaeurBvQx4cvmxVM7yUcHQVsl8l9m/dvecTioHb1eUp3qz4pvHcNT JuDa8u1iveGpbUXTY2ID6e8sJWPw1INGDawwD6Qk=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100017dc93be244-843adcee-efda-49d4-9814-fbf91153126b-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_535612DE-D426-46B9-98B6-2329B17BFD53"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Fri, 17 Dec 2021 16:31:24 +0000
In-Reply-To: <FB6407ED-BA9D-415A-AFCB-0D4D327679ED@tzi.org>
Cc: "netmod@ietf.org" <netmod@ietf.org>, Benoit Claise <benoit.claise=40huawei.com@dmarc.ietf.org>, Slavomír Mazúr <Slavomir.Mazur@pantheon.tech>, Miroslav Kováč <miroslav.kovac@pantheon.tech>, rfc-markdown@ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Carsten Bormann <cabo@tzi.org>
References: <43BBAD20-D816-4D01-8326-1D67185CCC19@tzi.org> <24856.1639347093@localhost> <0100017db6a106f8-a9773885-6347-4fd6-a2d6-69ec6941bc7b-000000@email.amazonses.com> <20211214.083324.1824911592330241723.id@4668.se> <3782772c-b5b4-4285-f65e-67b1113e1b07@huawei.com> <0100017dc8e0fcbd-8899bb50-f0bf-4537-a87b-64eb82d9664a-000000@email.amazonses.com> <FB6407ED-BA9D-415A-AFCB-0D4D327679ED@tzi.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2021.12.17-54.240.48.93
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/n7mF_RqFs_Z7ldBZRMow7qQXSe0>
Subject: Re: [Rfc-markdown] [netmod] too long lines from IANA module inclusion
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Dec 2021 16:31:31 -0000


> (15 equals signs left, 16 equals signs right) seems to be the favorite lead-in; however, draft-wing-dnsop-structured-dns-error-page-01.txt had a version indented by 2 characters that has 14+15 accordingly.  About 5 % 10+11, apparently before RFC 8792 was published so there was less space.)

Undoubtedly because it is the rfcfold (https://github.com/ietf-tools/rfcfold) default.  The goal is to hit column-69 so as to provide a visual scanning aid.


> Examples from the HTTP ecosystem (GNAP, HTTPAPI, HTTPBIS) didn’t have any “===“ decoration, though.  (Why the heck was this left open as a choice for the author?  I like “%%%” decoration instead, should I use that as a personal fashion statement?)

Because sometimes it is desirable for the bracketing to match the native file commenting syntax (e.g., “#“ for shell/Python, “//“ for C++, “;” for ABNF, etc.)

K.