Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis

Kent Watsen <kent@watsen.net> Mon, 04 March 2024 21:29 UTC

Return-Path: <0100018e0b5eb910-c53e3d00-3856-4049-8bd9-394d25b3bde3-000000@amazonses.watsen.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258C9C18DB89 for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2024 13:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 cVcfRp0w4A97 for <netmod@ietfa.amsl.com>; Mon, 4 Mar 2024 13:29:02 -0800 (PST)
Received: from a48-95.smtp-out.amazonses.com (a48-95.smtp-out.amazonses.com [54.240.48.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38718C180B75 for <netmod@ietf.org>; Mon, 4 Mar 2024 13:29:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1709587741; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=gRO46WZIDyvG+giEO/nJd83cKd/msJw/rtgJ+3/XTMc=; b=QCDB40H4fM/lzlCjXLFE+t9y7IpFb3Ek6QK0OCElDGzZwVAWKBB+CNA6mu+jFNGh WrKYjsWvwVNtzgaoOkLOroxu7TL+ermN/Qu1Ls+TTrCIPfqf0z7bUCAgBs5ENiEJngi s32GPvPCkQTSIAzM2NXUwbno5TkHT4vxWGCi+4MU=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100018e0b5eb910-c53e3d00-3856-4049-8bd9-394d25b3bde3-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_144C16FC-096C-4820-8C52-23C3B262526A"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Mon, 04 Mar 2024 21:29:00 +0000
In-Reply-To: <5c0d327d90b14b0f88cae8f610b20727@huawei.com>
Cc: Qin Wu <bill.wu@huawei.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "netmod@ietf.org" <netmod@ietf.org>
To: Italo Busi <Italo.Busi=40huawei.com@dmarc.ietf.org>
References: <8a9d527a81db4ec9b9fc396691346fad@huawei.com> <5c0d327d90b14b0f88cae8f610b20727@huawei.com>
X-Mailer: Apple Mail (2.3774.400.31)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.03.04-54.240.48.95
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/cmQHOipjEEyvzAvz-WpIfrenhkY>
Subject: Re: [netmod] Long trees RE: Next steps for draft-ietf-netmod-rfc8407bis
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Mar 2024 21:29:04 -0000

Hi Italo,

> On Mar 4, 2024, at 1:38 PM, Italo Busi <Italo.Busi=40huawei.com@dmarc.ietf.org> wrote:
> 
> I am wondering whether the issue of YANG tree too-long could be resolved by updating the IETF tooling. For example, I have noted that the html-ized version of the I-Ds is now working well with artwork exceeding the 72 characters limit …
>  
> Maybe the html or html-ized version of the I-D/RFC might include the jstree pyang output instead of the tree pyang output

This is what I’ve been saying for awhile now.

Datatracker should unfold folded-artwork for formats like HTML that can provide horizontal scrollbars.

That said, the desire to break tree-diagrams into pieces won’t be resolved, as authors still need to support plain-text output…  grrr


Personally, I prefer whole-trees (if not folded), which are much easier to place into a document, but many in the WG push for tree-diagram snippets.   Hope we can reach a consensus on this…

K