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

Carsten Bormann <cabo@tzi.org> Sat, 28 October 2023 19:57 UTC

Return-Path: <cabo@tzi.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 D2212C14F747 for <rswg@ietfa.amsl.com>; Sat, 28 Oct 2023 12:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 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] 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 z4SvlHHVz9FS for <rswg@ietfa.amsl.com>; Sat, 28 Oct 2023 12:57:15 -0700 (PDT)
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 D40A4C14F738 for <rswg@rfc-editor.org>; Sat, 28 Oct 2023 12:57:13 -0700 (PDT)
Received: from eduroam-pool10-182.wlan.uni-bremen.de (eduroam-pool10-182.wlan.uni-bremen.de [134.102.90.181]) (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 4SHr0R3w9kzDCbs; Sat, 28 Oct 2023 21:57:11 +0200 (CEST)
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: <B853BF73-0A1D-4A50-BC23-3E74C19C0379@smcquistin.uk>
Date: Sat, 28 Oct 2023 21:57:11 +0200
Cc: Colin Perkins <csp@csperkins.org>, rswg@rfc-editor.org
X-Mao-Original-Outgoing-Id: 720215831.137823-7d37cda002f83ae0f1b81fa11816cac4
Content-Transfer-Encoding: quoted-printable
Message-Id: <338DA1D0-5534-4055-8854-D1734D8EEA73@tzi.org>
References: <20231027211651.842B65B85677@ary.fritz.box> <23c31faa-0a02-4d50-bce1-f5675fdcbe8c@gmx.de> <2F1EAE87-FB96-44E1-A0D1-38EC69A1EA02@csperkins.org> <B853BF73-0A1D-4A50-BC23-3E74C19C0379@smcquistin.uk>
To: Stephen McQuistin <sm@smcquistin.uk>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/gi4oyt3wMNIHaKaJdi1-EqrPagE>
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: Sat, 28 Oct 2023 19:57:17 -0000

On 2023-10-28, at 21:46, Stephen McQuistin <sm@smcquistin.uk> wrote:
> 
> To that end, would it make sense to split this document into two: (i) a definition of the underlying data model (essentially defining what _any_ protocol description language would need to capture to be able to do what we want to do); and (ii) a definition of the Augmented Packet Header Diagram format.

That depends a lot on what other tools generate/consume (i).
To me, being able to do this would be the main point of introducing this work into specification practice.
An ingestor of (ii) is what you seem to have now; I’d expect a complementary generator to emerge (which would be a pretty-printer in combination with the ingestor).

> I’m not sure which (R|W)G would be the best place for either/both of those.

Definitely the worst place: RSWG (which is neither an RG nor a WG).

Grüße, Carsten