Re: [netmod] WGLC - draft-ietf-netmod-yang-tree-diagrams

Benoit Claise <bclaise@cisco.com> Sat, 13 January 2018 14:08 UTC

Return-Path: <bclaise@cisco.com>
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 AD99B12D7F9; Sat, 13 Jan 2018 06:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.599
X-Spam-Level:
X-Spam-Status: No, score=-12.599 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvUqmq0iP8rQ; Sat, 13 Jan 2018 06:08:32 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E2D51274D2; Sat, 13 Jan 2018 06:08:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6917; q=dns/txt; s=iport; t=1515852510; x=1517062110; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=9o2ZRYljFUzLNrN5QWHIbdVKh8SOIuR5tev6v8BtKqE=; b=QKBANeL+BoCIcAmk+s6SBbnQ3ooeWtTxkrlMfJ+vRRimxW/yJwkpY4kC K+XJNbgaBek+VaFPLgNbLJewIlPw96kurkZDzXGapI4D/MQ/jKkhcMS7D JXHgSL8krJ+Pb/RaY8IlJA26mI3wYleybPK6ojmiGO8JEhYWUs1urEMFW k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B1AQAHElpa/xbLJq1DGhkBAQEBAQEBAQEBAQEHAQEBAQGEJ3QnhBOLGI9vkVuFZYICChgBDIRHTwKFBBQBAQEBAQEBAQFrKIUjAQEBAQMBASFLCwwECxUBLAICJzAGAQwGAgEBii8QNK4jgicmihUBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYEigxqDbIFpKYF3gQ6DLwEBAQEBAReBIwEPAwGDNheCTgWKVIIvlmGIDI0/ghmGHYNvh2uNPoFeiAmBPDYiEU9wMhoIGxU9giqEWEA3AQGLBYI8AQEB
X-IronPort-AV: E=Sophos;i="5.46,353,1511827200"; d="scan'208,217";a="1435470"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jan 2018 14:08:28 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w0DE8SHG008041; Sat, 13 Jan 2018 14:08:28 GMT
To: "t.petch" <ietfc@btconnect.com>, NETMOD Working Group <netmod@ietf.org>, joel jaeggli <joelja@bogus.com>
Cc: draft-ietf-netmod-yang-tree-diagrams@ietf.org
References: <2cde8b64-0455-a513-4719-feb61c87a952@bogus.com> <022301d38c6e$e2f0cf00$4001a8c0@gateway.2wire.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <50492eeb-57ea-94dc-cb1d-0c52bda05750@cisco.com>
Date: Sat, 13 Jan 2018 15:08:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <022301d38c6e$e2f0cf00$4001a8c0@gateway.2wire.net>
Content-Type: multipart/alternative; boundary="------------9B8D4DDFAA96A45382EE9653"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/fK0DAnPJFTY861sTYlIMgGI48mQ>
Subject: Re: [netmod] WGLC - draft-ietf-netmod-yang-tree-diagrams
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 13 Jan 2018 14:08:33 -0000

Hi Tom,

IMO, the best to proceed is exactly like done in the RIP draft.
Some sections 2.* explains how the module was build, based one excerpts 
of the tree diagram.
Then we have the full tree if someone wants to see the big structure.

In the end, the tree view should be browsed with tooling.
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-rip/
    => Yang catalog entry for ietf-rip@2018-01-09.yang 
<https://www.yangcatalog.org/yang-search/module_details.php?module=ietf-rip@2018-01-09.yang>
    => [Tree View for ietf-rip] Tree View 
<https://www.yangcatalog.org/yang-search/yang_tree.php?module=ietf-rip>

Regards, Benoit
> I think that the outstanding issue is what to do with long tree
> diagrams. Yes, we have discussed it and have a statement about one page
> being a good idea but very few of the I-Ds I see can manage that.
>
> RIP has four pages, NAT has six.  OSPF and BFD have divided the diagram
> up but many if not most of the subdivisions still exceed one page (I
> would regard two as more or less ok but many exceed that).
>
> My own take is that a too long tree diagram reflects a too flat module
> structure, just as many years ago, code would be a long unbroken
> sequence and now is divided up into manageable modules, so a YANG module
> should be structured as smaller pieces, bite-size chunks, and a tree
> diagram of one page is a good indicator of a manageable chunk size.
>
> Tom Petch
>
> ----- Original Message -----
> From: "joel jaeggli" <joelja@bogus.com>
> Sent: Monday, January 01, 2018 10:01 PM
>
> Greetings,
>
> We hope  the new year is a time to make great progess on outstanding
> documents before preparation for the  London IETF begins in earnest.
>
> This starts a two-week working group last call on:
>
>   YANG Tree Diagrams
> draft-ietf-netmod-yang-tree-diagrams
>
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-tree-diagrams/
>
> Please send email to the list indicating your support or concerns.
>
> We are particularly interested in statements of the form:
>
>    * I have reviewed this draft and found no issues.
>    * I have reviewed this draft and found the following issues: ...
>
>
> Thank you,
> NETMOD WG Chairs
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
> --------
>
>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
> .
>