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

Paul Hoffman <> Sun, 26 November 2023 23:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4C9D1C14CF13 for <>; Sun, 26 Nov 2023 15:07:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.001, 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
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FmirgEDxtjjt for <>; Sun, 26 Nov 2023 15:07:46 -0800 (PST)
Received: from (Opus1.Proper.COM []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 20B06C14F747 for <>; Sun, 26 Nov 2023 15:07:46 -0800 (PST)
Received: from [] ( []) (authenticated bits=0) by (8.15.2/8.15.2) with ESMTPSA id 3AQN7f9H015960 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 26 Nov 2023 16:07:42 -0700 (MST) (envelope-from
X-Authentication-Warning: Host [] claimed to be []
From: Paul Hoffman <>
To: Paul Kyzivat <>
Date: Sun, 26 Nov 2023 15:07:41 -0800
X-Mailer: MailMate (1.14r5937)
Message-ID: <>
In-Reply-To: <>
References: <310371.1700735021@dyas> <> <> <> <> <> <> <> <> <> <>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
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: Sun, 26 Nov 2023 23:07:47 -0000

On 26 Nov 2023, at 14:53, Paul Kyzivat wrote:

> OK, it seems Carsten and I are in violent agreement.
> Can we hear from some others here on rfc-interest on whether this is popular enough to pursue further? At some point it probably needs to be discussed on the tools list.

This discussion started with "I want to be able to extract $x" and veered into "the RPC should be making $x available to everyone for every RFC". A different path would be "it would be nice if I could extract $x from one or more RFCs locally".

Given that no one has asked the original question before now, it seems likely to only be needed by a small number (maybe less than a few dozen) people. Thus, a discoverable tool that does it might be better than making the RPC add the tool and the process for everyone.

--Paul Hoffman