Re: [Rswg] draft-mcquistin-augmented-ascii-diagrams

"John R. Levine" <johnl@iecc.com> Sun, 29 October 2023 12:08 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56555C14E513 for <rswg@ietfa.amsl.com>; Sun, 29 Oct 2023 05:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.408
X-Spam-Level:
X-Spam-Status: No, score=-4.408 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_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=iecc.com
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 IyM-Kbetzi_D for <rswg@ietfa.amsl.com>; Sun, 29 Oct 2023 05:08:30 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 66199C14CE5E for <rswg@rfc-editor.org>; Sun, 29 Oct 2023 05:08:30 -0700 (PDT)
Received: (qmail 4685 invoked from network); 29 Oct 2023 12:01:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=123a653e49ac.k2310; bh=KHl5Oy1AZRm6M1C3cxO2hT8+FXNzTFzUQZ3VBjfjdL0=; b=jGWLq75CN0A+ulC3SXiG6IxFEhneb2Dxav3NgIo7tM8ed5KT7L9oVnitHveDuebSdF8jZ12bcCsDz4liPzS4yv4MYmMmCoGpVX4PQlMWe6tLdRUHxG8tgSNRubNwC5ExkwPK+0mrECz/1hM+QvgGq+tCBAFn+hLFvEdyZstKUQiBKbC57CzxGMpEvdNeIcTd6mZkD2qrdhf14eWF2ObyPQIW5Po374oN7YsRHfbpD8PmzQ4Z+qA6g3xYHs4OHb77nQLRy7y0bzTlcMAGgGkIeAhQ3VMa3ZEBve/KHGIhapLCM1rIR8kTivbr1WfrjlplMFh2YwaB/AiAEw88q9866A==
Received: from ary.fritz.box ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 29 Oct 2023 12:01:47 -0000
Received: by ary.fritz.box (Postfix, from userid 501) id E8AB26479FC1; Sat, 28 Oct 2023 22:55:01 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by ary.fritz.box (Postfix) with ESMTP id 92A0F606F2F8; Sat, 28 Oct 2023 22:55:01 +0200 (CEST)
Date: Sat, 28 Oct 2023 22:55:01 +0200
Message-ID: <d2dbeac9-600e-2c9c-3bdf-99c54343d91e@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Colin Perkins <csp@csperkins.org>, rswg@rfc-editor.org
X-X-Sender: johnl@ary.fritz.box
In-Reply-To: <2F1EAE87-FB96-44E1-A0D1-38EC69A1EA02@csperkins.org>
References: <20231027211651.842B65B85677@ary.fritz.box> <23c31faa-0a02-4d50-bce1-f5675fdcbe8c@gmx.de> <2F1EAE87-FB96-44E1-A0D1-38EC69A1EA02@csperkins.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/IMtVM4YKUN9xxBDYjn7WM6mjcGA>
Subject: Re: [Rswg] draft-mcquistin-augmented-ascii-diagrams
X-BeenThere: rswg@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Working Group \(RSWG\)" <rswg.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rswg>, <mailto:rswg-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg/>
List-Post: <mailto:rswg@rfc-editor.org>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rswg>, <mailto:rswg-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Oct 2023 12:08:35 -0000

> The entire point of this draft is that it doesn't require any change to the 
> RFC format. It doesn't need to be embedded into artwork, source code, media 
> types, or anything of the sort. It's a structured way of using the existing 
> RFC format, unchanged, and usable **today** (and, indeed, with any variant of 
> the RFC format we've had in the last few decades).

It would look OK in the text rendering, horrible in the HTML and PDF, and 
would be a challenge to represent in XML since the line breaks are 
critical.  (Unless you're secretly planning to wrap it in XML <artwork> or 
the like.)

As I think I said in another message, my suggestion it to take out the 
kludgery to try to embed the diagrams in text and just define the format.

We can separately figure out what kind of RFCXML artwork or sourcecode 
elements would be the best container.

R's,
John