IETF Logo Mail Archive

Re: [Rfc-markdown] how to reference a draft, and a section within an RFC?

Carsten Bormann <cabo@tzi.org> Thu, 26 January 2023 11:53 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 0FF04C165767 for <rfc-markdown@ietfa.amsl.com>; Thu, 26 Jan 2023 03:53:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6eestIUAkXBt for <rfc-markdown@ietfa.amsl.com>; Thu, 26 Jan 2023 03:53:08 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61C1DC15C533 for <rfc-markdown@ietf.org>; Thu, 26 Jan 2023 03:53:06 -0800 (PST)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4P2fGl3Q2xzDCbs; Thu, 26 Jan 2023 12:53:03 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CADyWQ+ER3dytaWJoZ6zyeyOFcX5eRYHWqzQ32op2+ihoX0HhKg@mail.gmail.com>
Date: Thu, 26 Jan 2023 12:53:03 +0100
Cc: Paul Wouters <paul@nohats.ca>, rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 696426782.905677-dec7f09fb4606a1b6988e4d751148adc
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DC8EC64-76D4-4F4A-8144-92481BBF9139@tzi.org>
References: <b0161e83-b2d7-9edc-50d8-ef19e5cc408e@nohats.ca> <944065C8-2CBD-4C46-AADB-D566A50C2129@tzi.org> <CADyWQ+ER3dytaWJoZ6zyeyOFcX5eRYHWqzQ32op2+ihoX0HhKg@mail.gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/ac19r2nxRmpJS56U6-D96cmkxlA>
Subject: Re: [Rfc-markdown] how to reference a draft, and a section within an RFC?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
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, 26 Jan 2023 11:53:14 -0000

On 2023-01-26, at 00:44, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
> And it seems the key is to not include the version number.

Actually, you can very well include a revision number:

normative:
  I-D.ietf-core-href:
  href-old: I-D.ietf-core-href-01

Note that I renamed the anchor of the second reference to test this example, as both references generate a default anchor of I-D.ietf-core-href, so you can’t have both in a single document (which may be the natural thing if you want to reference the current revision as well as a specific older revision in the same document).

Then there is draft-ietf-idr-deprecate-8-9-10 — no, the -10 is not a revision number, it is part of the fixed draft name; a current revision might be draft-ietf-idr-deprecate-8-9-10-00.  All tools are off on that one… (and on draft-ietf-acme-dns-account-01, which appears to have revision -00 as well: draft-ietf-acme-dns-account-01-00 — here the confusion appears to be inadvertent, although it already was in draft-todo-chariton-dns-account-01).

Grüße, Carsten

v2.23.0 | Report a Bug | By Email