IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 27 October 2023 13:21 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13B4FC15152F; Fri, 27 Oct 2023 06:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_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_BLOCKED=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfgRMZ6SWsdd; Fri, 27 Oct 2023 06:21:19 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 174CAC151533; Fri, 27 Oct 2023 06:21:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2997F1800E; Fri, 27 Oct 2023 09:21:15 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id sjjnQyPfaxHU; Fri, 27 Oct 2023 09:21:12 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5FE621800C; Fri, 27 Oct 2023 09:21:12 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1698412872; bh=dECH78u58p9veO2rv9lPkdb8VUu1z4IcSm+JjwpTP+E=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=C3gtYloN3xagHettJH0gS8g2BstHYAlIPUZyh5BYrhJb4XMBdmrJDtiR4mf8Lcj1h cH/NH01TlhZZUleXzjsCHXeBiFJ1gE1klVoiUKTmxLfdl6NM+dlywKunQyQSPyXhk3 B23y/k/qvBUPF2/S8Azfsb65aPpRopOO9lcQ1JGzJ+ZNo5nAteMBgD6pNcvr7rOyTT 4tIktrCCaFcuE2obH2DTxioaql+dnaOzeM/1UY0yDkb5adQO2A9m/ED4r6NfwDhEr8 Cmmags5bVhaOjfwJ4r18xJ83Wv0bBr3d5XYvlR1ieMwDPogaAUpLZ6bRHMOUjMxSpW BRCDNtGNvTweg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 555F19F; Fri, 27 Oct 2023 09:21:12 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Independent Submissions Editor (Eliot Lear)" <rfc-ise@rfc-editor.org>
cc: RFC Interest <rfc-interest@rfc-editor.org>, RSWG <rswg@rfc-editor.org>
In-Reply-To: <05dff7e7-9744-4ce8-9cc2-98699f7a0c7b@rfc-editor.org>
References: <05dff7e7-9744-4ce8-9cc2-98699f7a0c7b@rfc-editor.org>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 27 Oct 2023 09:21:12 -0400
Message-ID: <14700.1698412872@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/PZQbBW19dwFWyG0otbgJHdNRnow>
Subject: Re: [rfc-i] [Rswg] draft-mcquistin-augmented-ascii-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: Fri, 27 Oct 2023 13:21:23 -0000

Independent Submissions Editor (Eliot Lear) <rfc-ise@rfc-editor.org> wrote:
    > draft-mcquistin-augmented-ascii-diagrams has been submitted for consideration
    > as an independent submission.  I would like to know if this community has
    > comments about this draft.  Would you find it of value?  Does it pose any
    > concerns?  Is it well written?

It is of value!!

I think that it's wrong to do this as an independant submission.
I think that it belongs in the RSWG :-)
(Or maybe in the IETF stream in GEN Area somewhere)
If we are going to do this, then we need to do it with some authority.

Aren't there ways/tools to create the diagrams from text descriptions?
(Like the mermaid diagrams)

Decades ago I worked on https://datatracker.ietf.org/doc/draft-nossik-pax-pdl/
and I think that we actually wrote some code to generate the packet diagrams.
I remember that we argued about many minutia about how do display certain things.

The document itself I found wandered a bit, and I thought I'd get more of a
criticism of the variations and why they are a problem, and why their format
is better.  Instead it seemed to deep dive into very specifics that I was not
quite ready for.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email