Re: [Rfc-markdown] [Tools-discuss] getting the Acknowledgement section in the right place

Carsten Bormann <cabo@tzi.org> Tue, 29 September 2020 06:16 UTC

Return-Path: <cabo@tzi.org>
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 F08EE3A0832; Mon, 28 Sep 2020 23:16:41 -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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 dkTd2v48Rb_m; Mon, 28 Sep 2020 23:16:39 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B01F3A082C; Mon, 28 Sep 2020 23:16:38 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc60.dip0.t-ipconnect.de [84.141.204.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4C0q0J0MbszylV; Tue, 29 Sep 2020 08:16:32 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <17844.1601345216@localhost>
Date: Tue, 29 Sep 2020 08:16:31 +0200
Cc: Tools Team Discussion <tools-discuss@ietf.org>, rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 623052991.541577-d1e788ab1427f2134051ffb04949643e
Content-Transfer-Encoding: quoted-printable
Message-Id: <86177A5E-E2BE-4949-94CD-389AA02D10C3@tzi.org>
References: <17844.1601345216@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/K8oSWrmeP6QUOGvg51R2PKQUwxc>
Subject: Re: [Rfc-markdown] [Tools-discuss] getting the Acknowledgement section in the right place
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: Tue, 29 Sep 2020 06:16:42 -0000

On 2020-09-29, at 04:06, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> I noticed while reading the diff for an AUTH48 that the RFC editor had moved
> the Acknowledgement section after the references.

Yes, that’s what RFC 7322 says:

https://tools.ietf.org/html/rfc7322#section-4.10

(It may be followed by a contributors section, and then is followed by the authors’ addresses.)

> I guess we can make that happen by putting that section after the ---back
> in kramdown, and move it manually in xml.

Putting the section last (or before a contributors section, which may be automatically inserted by kramdown-rfc) in the back matter is right.
No manual moving required.

Make sure you have numbered=“no” on the section:



# Acknowledgements
{: numbered="no"}



Examples for doing this:

https://raw.githubusercontent.com/cbor-wg/CBORbis/master/draft-ietf-cbor-7049bis.md
https://raw.githubusercontent.com/core-wg/senml-more-units/master/draft-ietf-core-senml-more-units.md

Or any recent kramdown-rfc draft…

(This really belongs to the rfc-markdown list, which I have CCed.)

> It wasn't something I'd noticed before.

RFC 7322 was published in September 2014 ;-)

Grüße, Carsten