Re: [rfc-i] getting SVG of RFC diagrams

Carsten Bormann <> Thu, 23 November 2023 16:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7403BC14F5E0 for <>; Thu, 23 Nov 2023 08:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IpM2q4QmMc3q for <>; Thu, 23 Nov 2023 08:47:57 -0800 (PST)
Received: from ( [IPv6:2001:638:708:32::21]) (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 (Postfix) with ESMTPS id BEAD0C14CEFF for <>; Thu, 23 Nov 2023 08:47:56 -0800 (PST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4SbkZ237sszDCbw; Thu, 23 Nov 2023 17:47:54 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Thu, 23 Nov 2023 17:47:54 +0100
Cc: RFC Interest <>
X-Mao-Original-Outgoing-Id: 722450873.653818-97cb90d71ee5264eafb4d581d5de9da5
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <310371.1700735021@dyas> <> <> <>
To: Paul Kyzivat <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [rfc-i] getting SVG of RFC diagrams
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Nov 2023 16:48:00 -0000

On 2023-11-23, at 17:39, Paul Kyzivat <> wrote:
> On 11/23/23 10:01 AM, Marc Petit-Huguenin wrote:
>> XPointer can be used as a URI fragment[1].  Firefox does not implement it[2] but I found an obsolete extension that did[3], so maybe such extension is still possible.
> I would like there to be a sufficient naming convention so that someone that wants a piece of the rfc can construct the URL based on what is visible in the rendering of the RFC.

I don’t think this is attainable in general.

> That may be easy for figures that are labeled, but might be a problem for some source code such as ABNF that often is interleaved with text, without any label.

Indeed, artwork (including SVG) often is not embedded in a figure, so it doesn’t have a natural “Figure 4711” label.

(It also turns the numbered labels are rather brittle during development, so giving the artwork a name= attribute for external referencing generally is good practice.  Slugified names can stand in for that, but also are more brittle than given names.)

Grüße, Carsten