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

Colin Perkins <csp@csperkins.org> Sun, 29 October 2023 15:33 UTC

Return-Path: <csp@csperkins.org>
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 B73D4C151071 for <rswg@ietfa.amsl.com>; Sun, 29 Oct 2023 08:33:26 -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=csperkins.org
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 qCH1uU3ugf3K for <rswg@ietfa.amsl.com>; Sun, 29 Oct 2023 08:33:22 -0700 (PDT)
Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E03AC15106E for <rswg@rfc-editor.org>; Sun, 29 Oct 2023 08:33:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=Date:Subject:To:From; bh=x5b1h+Of5eiJ99GS8C1B64EgMiEqvbUZhW/IlpbQeHg=; b=H0NXXLOHS89SnQHNN2+a3jabqg TmCJF2ePXJH433Nd+UwjDCRwSetK5rn/u5WTktPmEntLK4Nzf7E0J/txXGb1iX2J+FWqoSeyXeevM a5wUGc9rey6icc8klp5PCM2AXqn757v34c0LFJmuQBUMSLnpRHYiY3Za+fNGNiSpZDnd3iQg4hJLe ZSjj9pe5/yeIfQjPj/p8XZyrMuIGSZHoZ8uY/TWTRr0cYxg6xuGAXIoqfAgSWzPHgxRLcLGEiGEdg AnuZeS//vjfal+XNu8TEepkBtooSaR61RMAvM9pEmsh9Xsi5jZFPBKSdxkEty09RMq3ykTPRXLLEh qxM3nszg==;
Received: by mailhub-cam-d.mythic-beasts.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <csp@csperkins.org>) id 1qx7mz-003q7D-42; Sun, 29 Oct 2023 15:33:21 +0000
From: Colin Perkins <csp@csperkins.org>
To: John R Levine <johnl@taugh.com>
Cc: rswg@rfc-editor.org
Date: Sun, 29 Oct 2023 15:33:11 +0000
X-Mailer: MailMate (1.14r5998)
Message-ID: <C7EE10F9-7983-4057-9E79-CAA91388CEF7@csperkins.org>
In-Reply-To: <c3076914-db17-d24e-a218-dd7004cada32@taugh.com>
References: <20231027211651.842B65B85677@ary.fritz.box> <23c31faa-0a02-4d50-bce1-f5675fdcbe8c@gmx.de> <2F1EAE87-FB96-44E1-A0D1-38EC69A1EA02@csperkins.org> <c3076914-db17-d24e-a218-dd7004cada32@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; markup="markdown"
Content-Transfer-Encoding: quoted-printable
X-BlackCat-Spam-Score: 24
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/9xQ0XxkzYqPCFI9HkNmS9LbZpRw>
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 15:33:26 -0000


On 29 Oct 2023, at 11:59, John R Levine wrote:

> On Sat, 28 Oct 2023, Colin Perkins wrote:
>> 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.
>
> Sorry, but no.  For these things to be legible, they need to be wrapped in XML elements to say to preserve the line breaks and to display them in fixed pitch text.  By the time you do that, it's easier to wrap them in <sourcecode>, which has the added benefit of working with all the other tools people have to extract and manage sourcecode elements

Sorry, I realise I wasn't clear. We wrap the packet diagrams in <artwork> as usual. What I meant to say is that it doesn't require any new embedding mechanisms.

> without needing an extra kludge to look for the special phrase.

The "special phrase" is semantically meaningful to name the packet format. Similarly, the structured text following the diagram conveys meaning. These are both semantically part of the packet description format.

> So once again it seems reasonable to move the definition of the diagrams ahead, and leave the embedding methods for later.

The diagrams aren't meaningful without the surrounding text. The way they are embedded within the text is part of the format.

Colin