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

Miek Gieben <miek@miek.nl> Sat, 04 November 2023 13:10 UTC

Return-Path: <miek@miek.nl>
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 69E98C0A8575 for <rfc-markdown@ietfa.amsl.com>; Sat, 4 Nov 2023 06:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FSL_HELO_FAKE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20230601.gappssmtp.com
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 NXs0zV3nsHQH for <rfc-markdown@ietfa.amsl.com>; Sat, 4 Nov 2023 06:10:22 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 674C1C16F3E4 for <rfc-markdown@ietf.org>; Sat, 4 Nov 2023 06:10:21 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-9db6cf8309cso414193066b.0 for <rfc-markdown@ietf.org>; Sat, 04 Nov 2023 06:10:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20230601.gappssmtp.com; s=20230601; t=1699103420; x=1699708220; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=d7pvPKgIXwRPE+6xvU1MGgG8XMqqo0yOY9+6rgvTIiI=; b=d4pvvtdANDzRNI8fOhyWVFI71J238D8j4X1CjkyVPCcgs9dUqtjdn7gUyjyZgLzolZ X56qpqXtulPkrDi2fKddnSfvqpSEpPbtiYrSLwmP2epY6TB+fS4qxe02/N01bUcg+8/m UadnQygLd8dRWufvN1Aldbmvi/geeAYxaxrn12XcyJb3JdtTiay7Oh4zeZMfVGYbOHnk gfV7XVmMsBWSv3SWPbV/o7EUpzTatQ7fk/Ux+rHi0mSKs53ZsKVMmZZ0YledXGG9GZCO ck8Iq5kpmnfntC5kgOlHzOedXwxa7Fqsa8ixaCKMF0h606/n7ZKtXOEQWBkB5mZSQtF/ 6pxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699103420; x=1699708220; h=in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=d7pvPKgIXwRPE+6xvU1MGgG8XMqqo0yOY9+6rgvTIiI=; b=G2ukbcJ1hcm2QENCaoNDwxEQ4RKVo7FGZqzbr3UEFsbdgbZrsJcoWB5WnivrMgm5Rz P36kBYJNsnxBVMJlfAj6BxlFfa27R0cwBckSqVNeYbebuEcrK15jl3mvRBKb1lG+4R0k S2z7V6HY/1PseRhtYkBbd7HgLyFa9Za1TRYff9gHGChDhWSZ1TsIu/9Dtz7XMyMnTU+4 73uCr+DLIzNmwIo/+rXaufNYeOkavi3Ytcc3u6NXaFcCfY4lzXmeriapUy/Qvff5w2ws vcg93Wdq2M1YMncWHJeiKHIMZjP1n0/oMPlJTMTBvSqBdgyZv1d8VCxahoM6atxgd4ds sO9w==
X-Gm-Message-State: AOJu0Yx5NIQC4h6QGltP36YFnZaFtovuvu2J+GTUfRbnDBmoCkKSFIrs p0bajIOeRcCqM+hO9iGLTtIlMw==
X-Google-Smtp-Source: AGHT+IGiVZqUwOqnLZy7np3VnZeI+MrN8YRexBPfjtpTHLHoxq3F5tFBkCsGUkX0SuONozo5mdYSDw==
X-Received: by 2002:a17:907:9301:b0:9b2:89ec:d701 with SMTP id bu1-20020a170907930100b009b289ecd701mr10288033ejc.27.1699103419977; Sat, 04 Nov 2023 06:10:19 -0700 (PDT)
Received: from gmail.com ([2a10:3781:2dc2:1:8ba3:af8c:ae64:24c8]) by smtp.gmail.com with ESMTPSA id ad24-20020a170907259800b009dda94509casm1176134ejc.102.2023.11.04.06.10.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 04 Nov 2023 06:10:18 -0700 (PDT)
Date: Sat, 04 Nov 2023 14:10:17 +0100
From: Miek Gieben <miek@miek.nl>
To: Carsten Bormann <cabo@tzi.org>
Cc: rfc-markdown@ietf.org
Message-ID: <20231104131017.xwqcej7s3ziclynm@gmail.com>
Mail-Followup-To: Carsten Bormann <cabo@tzi.org>, rfc-markdown@ietf.org
References: <DE3DA412-FB62-4AF2-9C01-1B2F9BD9A8F6@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <DE3DA412-FB62-4AF2-9C01-1B2F9BD9A8F6@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/q8kWh6ZdOwdFuBLRQAp_xybE3lk>
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: Sat, 04 Nov 2023 13:10:24 -0000

[ Quoting <cabo@tzi.org> in "[Rfc-markdown] 1.7.2: Handle sectio..." ]
>
>Up to now, it was really hard to reference into a referencegroup (STD
>or BCP reference), as that reference could possibly contain multiple
>RFCs, and one would need to be explicit which one was meant with the
>section reference.
>
>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 is a really nice idea, I've adopted this syntax into mmark as well.

Regards,
Miek