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

Carsten Bormann <> Thu, 23 November 2023 11:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3830AC1522AF for <>; Thu, 23 Nov 2023 03:53:25 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Pn-p_T6cGZDd for <>; Thu, 23 Nov 2023 03:53:21 -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 47CAEC1519B7 for <>; Thu, 23 Nov 2023 03:53:19 -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 4Sbc236P6KzDCbG; Thu, 23 Nov 2023 12:53:15 +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 12:53:15 +0100
X-Mao-Original-Outgoing-Id: 722433195.317526-cfa3abb27e5b8c4c10f0836a25f52b92
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <310371.1700735021@dyas> <>
To: Michael Richardson <>
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 11:53:25 -0000

On 2023-11-23, at 12:06, Carsten Bormann <> wrote:
> If you have the XML, I would have said "use `kramdown-rfc-extract-sourcecode -tfiles rfc4711.xml` and look into sourcecode/svg”, but I apparently never tested this…  Will fix.

Fixed in kramdown-rfc version 1.7.3.  As usual, update

  gem update kramdown-rfc

(using any options you used for initially installing kramdown-rfc).

Then you can 

  kramdown-rfc-extract-sourcecode -tfiles rfc4711.xml

and will find the svg files under


If you have a workable (and non-brittle) idea how to name the SVG files, please tell me (*).


Back to on-topic content:

This is really one of the many examples where RFCs include “attachments”, and we should make it easier to get at them.

Grüße, Carsten

(*) RFCs in publication format have an attribute “slugifiedName” (apparently undocumented at on an ancestor of that <svg element, but that only is available after prepping, so it is not useful for I-Ds which are in authoring format.