IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Sun, 26 November 2023 17:34 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00C0C151099 for <rfc-interest@ietfa.amsl.com>; Sun, 26 Nov 2023 09:34:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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
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 PSKi4UIGEZr1 for <rfc-interest@ietfa.amsl.com>; Sun, 26 Nov 2023 09:34:27 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [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 ietfa.amsl.com (Postfix) with ESMTPS id 930B3C14EB17 for <rfc-interest@rfc-editor.org>; Sun, 26 Nov 2023 09:34:25 -0800 (PST)
Received: from eduroam-0647.wlan.uni-bremen.de (eduroam-0647.wlan.uni-bremen.de [134.102.18.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4SdbSD0s84zDCbM; Sun, 26 Nov 2023 18:34:20 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8373b6b5-4a0a-4abb-8880-d618154b2f81@alum.mit.edu>
Date: Sun, 26 Nov 2023 18:34:19 +0100
Cc: rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 722712859.458517-b27bf3f40b040c003735005f44c75994
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F2DBD33-1553-4BBE-8ADB-115632C8373D@tzi.org>
References: <310371.1700735021@dyas> <7C81D316-7D04-4941-BEE5-6AE8C96F0DE1@tzi.org> <D1F8F86E-80D7-4FC7-B7B5-32648ACB5D65@tzi.org> <MN2PR11MB3757AF8CCDF388BA5CECFE1AB9B8A@MN2PR11MB3757.namprd11.prod.outlook.com> <153bde12-5773-42ce-bfdf-392e4492c06b@gmx.de> <9D66A3A2-5516-4924-8B1E-420871D862C5@tzi.org> <8373b6b5-4a0a-4abb-8880-d618154b2f81@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/u0JUp8Hw4DrMFF9Uv9XEArQDfNg>
Subject: Re: [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: Sun, 26 Nov 2023 17:34:31 -0000

On 2023-11-24, at 17:47, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
>> This could lead to:
>> https://www.rfc-editor.org/rfc/rfc9334/svg/layered-attester.svg
>> https://www.rfc-editor.org/rfc/rfc9334/ascii-art/layered-attester.ascii-art
>> https://datatracker.ietf.org/doc/draft-ietf-cbor-edn-literal/abnf/cbor-edn.abnf
> 
> Yes! This is the sort of thing I'm wishing for.

I put in a proof of concept at

https://tzi.org/~cabo/rfc

E.g., see:

https://tzi.org/~cabo/rfc/rfc9334/svg/layered-attester.svg
https://tzi.org/~cabo/rfc/rfc9334/ascii-art/layered-attester.ascii-art

I haven’t done the work for I-Ds yet, this will follow soon.

You can look at these extracted attachments in the browser, as well as save them or wget/curl them.

(Obviously, this only works reliably for RFC 8650 and later, so the PoC is limited to that.)

> There remains the issue of discovering what parts are available for a given document. It has been suggested that hovering over the part in the html rendering could show the name. Another possibility (not mutually exclusive) is to have the datatracker and the info page for the document:
> 
> https://www.rfc-editor.org/info/rfcNNNN

I just made 

https://tzi.org/~cabo/rfc/rfc9334/svg
https://tzi.org/~cabo/rfc/rfc9334/ascii-art
https://tzi.org/~cabo/rfc/rfc9334
and
https://tzi.org/~cabo/rfc

into collection pages (implemented as directory listings, as I’m lazy).
Content and styling is a bit quaint, but could be fixed easily.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email