IETF Logo Mail Archive

Re: [Rfc-markdown] 1.7.2: Handle section references into referencegroups

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 31 October 2023 10:46 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 407B9C151538 for <rfc-markdown@ietfa.amsl.com>; Tue, 31 Oct 2023 03:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 8eM9jqhR8Xxy for <rfc-markdown@ietfa.amsl.com>; Tue, 31 Oct 2023 03:46:13 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 98322C15C295 for <rfc-markdown@ietf.org>; Tue, 31 Oct 2023 03:46:12 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [5.148.108.163]) by relay.sandelman.ca (Postfix) with ESMTPS id 22C5E20B50; Tue, 31 Oct 2023 10:46:11 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id AA8EDA147F; Tue, 31 Oct 2023 03:47:10 -0400 (EDT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id A8538A1467; Tue, 31 Oct 2023 03:47:10 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>, rfc-markdown@ietf.org
In-reply-to: <DE3DA412-FB62-4AF2-9C01-1B2F9BD9A8F6@tzi.org>
References: <DE3DA412-FB62-4AF2-9C01-1B2F9BD9A8F6@tzi.org>
Comments: In-reply-to Carsten Bormann <cabo@tzi.org> message dated "Sat, 28 Oct 2023 21:50:36 +0200."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 31 Oct 2023 03:47:10 -0400
Message-ID: <3210538.1698738430@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/WV6DIL4xaAAw2fjybqdDEoqGFCA>
Subject: Re: [Rfc-markdown] 1.7.2: Handle section references into referencegroups
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: Tue, 31 Oct 2023 10:46:19 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    > For RFC 9485, the RPC devised a way to express in RFCXML section
    > references into RFCs that are in reference groups.  This convention is
    > now supported by kramdown-rfc.

    > New syntax: RFC8949@STD94 (Single RFC @ Reference Group)

    > This can be used for section references:

Good.

I think that the benefit is that we are now able reference STDxx properly,
and this improves the state for readers giving STDs more credence.

If STD94 changes, and it's no longer RFC8949 that I need to read, what
happens?
  a) if it changes while my document is an I-D. (Yes, I can fix it still, but
     let's say that I haven't done that because the STD got updated this morning)

  b) if it changes after my document is an RFC?

I realize that these aren't really kramdown-specific questions, but maybe the
form of the error is :-)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.23.0 | Report a Bug | By Email