IETF Logo Mail Archive

Re: [netmod] stable reference for tree diagram notation

Lou Berger <lberger@labn.net> Mon, 13 March 2017 18:26 UTC

Return-Path: <lberger@labn.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 886CD1297E1 for <netmod@ietfa.amsl.com>; Mon, 13 Mar 2017 11:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level:
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 8DneY39HFdJP for <netmod@ietfa.amsl.com>; Mon, 13 Mar 2017 11:26:23 -0700 (PDT)
Received: from gproxy7-pub.mail.unifiedlayer.com (gproxy7-pub.mail.unifiedlayer.com [70.40.196.235]) by ietfa.amsl.com (Postfix) with SMTP id 01F95129985 for <netmod@ietf.org>; Mon, 13 Mar 2017 11:26:21 -0700 (PDT)
Received: (qmail 13321 invoked by uid 0); 13 Mar 2017 18:26:20 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy7.mail.unifiedlayer.com with SMTP; 13 Mar 2017 18:26:20 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id vWSG1u01c2SSUrH01WSKxT; Mon, 13 Mar 2017 12:26:19 -0600
X-Authority-Analysis: v=2.1 cv=Ath9goNP c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=xqWC_Br6kY4A:10 a=6Iz7jQTuP9IA:10 a=48vgC7mUAAAA:8 a=AUd_NHdVAAAA:8 a=n82M--yd7VDAzOGejUoA:9 a=k5fpyHSxNWXC41-H:21 a=aliCRkFdxawbIyYt:21 a=pILNOxqGKmIA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=TSZmLRzkpGLBZRr3r8m8:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=6ECGzMWUlhEfLdS9HuI//NdWCoOq7gnmHFNxmOuaelI=; b=ZTZL9H4gIeQb6MWJKG1mdC1AG9 4QfOqjbEUHwTQukBbbAGFIZ4jDwEUAKXMmIq1zOGH3YcQ698A+ESK+31pzkbqkJmyS7T439C5tkeW iffT0Z704AcIR5Vy0LYm18O7e;
Received: from pool-100-15-85-191.washdc.fios.verizon.net ([100.15.85.191]:39062 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1cnUfg-0003Jh-O0; Mon, 13 Mar 2017 12:26:16 -0600
To: Robert Wilton <rwilton@cisco.com>, netmod@ietf.org, Andy Bierman <andy@yumaworks.com>
References: <271CED23-8655-45A8-8E05-3ABD460871BD@juniper.net> <20170308193434.GA10080@elstar.local> <D4E9D4E5.A12DC%acee@cisco.com> <20170311.224951.2245774412799352894.mbj@tail-f.com> <ff00c44b-e0f0-fb30-783f-a992e723da8d@cisco.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <6fe6a732-ccda-a93d-f005-63ec25cebf60@labn.net>
Date: Mon, 13 Mar 2017 14:26:15 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <ff00c44b-e0f0-fb30-783f-a992e723da8d@cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.85.191
X-Exim-ID: 1cnUfg-0003Jh-O0
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-85-191.washdc.fios.verizon.net ([IPv6:::1]) [100.15.85.191]:39062
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/9AO5SyK9frZT1UjKx13dNee6woA>
Subject: Re: [netmod] stable reference for tree diagram notation
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Mar 2017 18:26:24 -0000

FYI - just slapped together and published:

https://tools.ietf.org/html/draft-bjorklund-netmod-yang-tree-diagrams-00

Lou

(as contributor)

PS I'm happy with the definition being in 6780bis or in a standalone doc
(as above), but really think we as a WG need to decide ASAP so as not to
hold up 6780bis any further...


On 3/13/2017 2:20 PM, Robert Wilton wrote:
> Hi Andy,
>
> Would it make sense to update 6087bis section 4.4 to reference this new 
> pyang option for generated tree diagrams?
>
> Thanks,
> Rob
>
>
> On 11/03/2017 21:49, Martin Bjorklund wrote:
>> "Acee Lindem (acee)" <acee@cisco.com> wrote:
>>> Hi Juergen,
>>>
>>> On 3/8/17, 2:34 PM, "netmod on behalf of Juergen Schoenwaelder"
>>> <netmod-bounces@ietf.org on behalf of
>>> j.schoenwaelder@jacobs-university.de> wrote:
>>>
>>>> On Wed, Mar 08, 2017 at 06:56:20PM +0000, Kent Watsen wrote:
>>>>> This way, reader can focus more quickly on the diffs, but also this
>>>>> likely mimics what happened in reality (start with `pyang -f tree`
>>>>> and then manually edit from there).  What do you think?
>>>>>
>>>> Manually edited tree diagrams? I hope not.
>>> I frequently have to manually edit the pyang-generated trees to get them
>>> to fit in the xml2rfc output. Is there a work around for this that I don¹t
>>> know about?
>> In the latest pyang, I have added --tree-line-length.  Use:
>>
>>    pyang -f -tree --tree-line-length 69 ...
>>
>> to fit RFCs.
>>
>>
>> /martin
>>
>> _______________________________________________
>> 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
>

v2.23.0 | Report a Bug | By Email