IETF Logo Mail Archive

Re: [Rfc-markdown] [rfc-i] Markdown template for draft?

Lars Eggert <lars@eggert.org> Thu, 03 February 2022 07:35 UTC

Return-Path: <lars@eggert.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 6C1CA3A20F5 for <rfc-markdown@ietfa.amsl.com>; Wed, 2 Feb 2022 23:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 c4yjZLwFfduK for <rfc-markdown@ietfa.amsl.com>; Wed, 2 Feb 2022 23:35:44 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB0573A20F3 for <rfc-markdown@ietf.org>; Wed, 2 Feb 2022 23:35:44 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:54fa:be87:1e8d:ffae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id E5A7B1D4129; Thu, 3 Feb 2022 09:35:34 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1643873735; bh=M4EQBUumJ9rRReLRr3D4QAvlYOcvwaZ/QNoSWge8j1w=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=i3c5geY1OrjEq/UJEfICLBS25hqKVXrTgC0YEBLE+A0Or5kNGEaNgap3WKme8RlGX 2k8jFt1ULVf2k2xd0PRUuVbf4VR4SBEbQYLqsCvEJbP98jsHy71wAp4JE6qHq/JOQ5 dXVCUG+BUrmyP8rQGE7E66Kj9y5OZjsP4rP+LYto=
Content-Type: multipart/signed; boundary="Apple-Mail=_79C01F19-4A3A-4616-9964-B42847CC9C8F"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <d1cd3a24-317e-4cd9-b0e1-8250354484a1@beta.fastmail.com>
Date: Thu, 03 Feb 2022 09:35:34 +0200
Cc: rfc-markdown@ietf.org
Message-Id: <97283106-20E7-4B08-9294-384706C0726D@eggert.org>
References: <c801cad9-c562-ff8b-cdc9-1ead2b4bfa7e@alum.mit.edu> <625BB285-2460-4A8F-B79A-5BB5ECF3B54C@akamai.com> <5a8f7b73-283e-4395-f056-52c416bad9c9@nostrum.com> <0FA92417-7E9D-4842-B4B7-83A6E1C9621F@tzi.org> <A553DDC3-4B27-4275-838A-E6F0CDDA057A@tzi.org> <d1cd3a24-317e-4cd9-b0e1-8250354484a1@beta.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-MailScanner-ID: E5A7B1D4129.A26F4
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/T8ciEuPjXYkEIrhCj05aCFiUW80>
Subject: Re: [Rfc-markdown] [rfc-i] Markdown template for draft?
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: Thu, 03 Feb 2022 07:35:50 -0000

Hi,

On 2022-2-3, at 0:43, Martin Thomson <mt@lowentropy.net> wrote:
> 
> I recently decided to play Internet-Draft golf: https://raw.githubusercontent.com/martinthomson/empty-draft/main/draft-mt-empty.md
> 
> Not sure if that is as helpful as those other links, but it demonstrates how easy it is to use markdown.

this is nice, thanks.

It might be slightly less minimal and somewhat more useful if you also added the bits that generated the RFC2119 boilerplate and maybe gave an example about how to reference a draft and an RFC.

Lars

v2.23.0 | Report a Bug | By Email