[rfc-i] getting SVG of RFC diagrams

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 23 November 2023 10:23 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EC9BBC1519B7 for <rfc-interest@ietfa.amsl.com>; Thu, 23 Nov 2023 02:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wGuOQkApgf22 for <rfc-interest@ietfa.amsl.com>; Thu, 23 Nov 2023 02:23:49 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 B0445C14CE33 for <rfc-interest@rfc-editor.org>; Thu, 23 Nov 2023 02:23:49 -0800 (PST)
Received: from dyas.sandelman.ca (unknown []) by relay.sandelman.ca (Postfix) with ESMTPS id 149E51F951 for <rfc-interest@rfc-editor.org>; Thu, 23 Nov 2023 10:23:47 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="j/4h/Kqr"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 56C42A05FE; Thu, 23 Nov 2023 11:23:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1700735021; bh=MGBN5JyzbVxiUPpfNat7c3usY0HYA6IUqQGOSXT56rI=; h=From:To:Subject:Date:From; b=j/4h/Kqr6A6A603D2npOpwiP0rOPxHeqqOlr4Ck3cS9QooVsJxg0gWH26mKyPbZ25 tQnbfh7SxmJDWSUEN2xAwAY7QXIJocWLujut4KtyCvXH6dSJaBCCVfjnkYXUJAJI0W QeYn6LxiBbcLuUflCIS5JZA9HEVPlW/SchL8aYG1y+iprNlEQ5lpKAy3TnMp9fzQnq Tbz5nB4333RUT3W0Wlzx2S2NsZApsL0eRiubxg/544oWbjytvGj7LLH6jwtjnKgKC2 LmB+LsHrvmCtu6e6fwULcomsBnj2cDzcgL5aEbb1AHeXHP94AxLMQnR+MujqBRtUiF fJsn8teNYao4g==
Received: from dyas (localhost []) by dyas.sandelman.ca (Postfix) with ESMTP id 5213DA05F7 for <rfc-interest@rfc-editor.org>; Thu, 23 Nov 2023 11:23:41 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: rfc-interest@rfc-editor.org
X-Attribution: mcr
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: Thu, 23 Nov 2023 11:23:41 +0100
Message-ID: <310371.1700735021@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/p_5zdMO2HHuShqxu5LBi3ZIGyHc>
Subject: [rfc-i] getting SVG of RFC diagrams
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Nov 2023 10:23:54 -0000

RFC9334, for instance, as a few really nice SVG diagrams in it.

I know how to Show-Source, and then find the diagram I want, and then copy
and paste the SVG out into a file.  Others might find that harder to work
out.  In general, I'd prefer that people citing the document and diagrams did
so using the vector form of the diagram, rather than some 100dpi screen shot.

Perhaps for some use cases, there are some copyright issues, but certainly
not for talks about the RFC itself (reasonable use, criticism, etc.), or for
other I-D.

The question is: how to make these SVG files more easily available from the
HTML version of the RFC?

{I hope this belongs on this list}

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