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

Robert Wilton <rwilton@cisco.com> Mon, 15 January 2018 13:56 UTC

Return-Path: <rwilton@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 2768D12D0C3; Mon, 15 Jan 2018 05:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_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 Yx7VSmqdwa1P; Mon, 15 Jan 2018 05:56:10 -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 A056412D574; Mon, 15 Jan 2018 05:56:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7009; q=dns/txt; s=iport; t=1516024570; x=1517234170; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=f9ohAF9PNkhf8ipSloFJBkmgVOivzxDZ2Aw85tiLQCE=; b=P1988XFvegskTAtt/nqeHxtrj1a8QrlTw04/HjJe62A9nANjbrodjnEr YRhjxWbW7SOPSwwXBs7XTssHjMAk03QpDECnGog6bj1ny+RN864WatPa2 n9SjvCHpFKUAq+QgICsc8lFGwDNiLx+ckxQe99sTtUP/oNNopOw/d3Usp I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CTAQBcsFxa/xbLJq1dGQEBAQEBAQEBAQEBAQcBAQEBAYJKgV10J4QTixiPbJFbhWWCAgoYAQqESU8ChRIUAQEBAQEBAQEBayiFJAEBAQMBASFLGwsYKgICJzAGAQwGAgEBii8QqjKCJyaKDgEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhDyDbIFpKYMFgy8BAQIBAYE6AQ8DAYM2gmUFkieHS4lyiAyNP4IZhh2DbyaHRY0+gV6ICYE8NiJgcDIaCBsVPYIqhFdBN4l/gjwBAQE
X-IronPort-AV: E=Sophos;i="5.46,363,1511827200"; d="scan'208,217";a="1463186"
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; 15 Jan 2018 13:56:07 +0000
Received: from [10.63.23.131] (dhcp-ensft1-uk-vla370-10-63-23-131.cisco.com [10.63.23.131]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w0FDu7vp000585; Mon, 15 Jan 2018 13:56:07 GMT
To: joel jaeggli <joelja@bogus.com>, NETMOD Working Group <netmod@ietf.org>, draft-ietf-netmod-yang-tree-diagrams@ietf.org
References: <2cde8b64-0455-a513-4719-feb61c87a952@bogus.com> <d66db346-9ca8-c08d-ea25-4c239d265ad4@bogus.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <66857af8-80b4-8c7c-f952-f04c3f2adaa7@cisco.com>
Date: Mon, 15 Jan 2018 13:56:07 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <d66db346-9ca8-c08d-ea25-4c239d265ad4@bogus.com>
Content-Type: multipart/alternative; boundary="------------DA38265615B0C7F0C6D4DFD7"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/NPPYh0Ue-1bBnKAwDVIJOjgcjr0>
Subject: Re: [netmod] Reminder: 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: Mon, 15 Jan 2018 13:56:12 -0000

Hi Lou, Martin

I've done a quick review of draft -04.

It looks well written to me.

I have a spotted a few minor nits/questions.

Section 1:

(i) "Such diagrams are commonly used to provided " => "Such diagrams are 
used to provide"?

(ii) "This document provides the syntax used in YANG Tree Diagrams." => 
"This document describes the syntax used in YANG Tree Diagrams", or if 
not "describes", perhaps "specifies"?

(iii) "common practice is include" => "common practice is to include"

Section 2:
(iv) Are the top level data nodes really offset by 4 spaces, or should 
this be 2 spaces?  The example in section 2, and section 4 seem to 
differ here.  The submodule example in Sec 2.1 looks like it is using 2 
spaces.

(v) "is prefaces with" => "is prefaced with"

(vi) Section 2.2, should there be an example of an unexpanded uses 
statement?  I was wondering if this section was under specified?

Section 2.6:
(vii) "If the node is augmented into the tree from another module, its 
name is printed as <prefix>:<name>."  Does there need to be a 
clarification that the prefix name used is the one used by the module's 
import statement?  Or does it use the prefix statement from the imported 
modules instead (I know that these should normally be the same, but this 
is not guaranteed).

Section 3.2.
(viii) It would be slightly easier to read if there wasn't a linebreak 
between "--" and "tree-print-groupings", not sure if that is feasible to 
force this.

Thanks,
Rob

On 10/01/2018 16:16, joel jaeggli wrote:
> Just a reminder given the date that this was posted. This last call is
> expected to complete Monday 1/15/18.
>
> Thanks
>
> joel
>
>
> On 1/1/18 2:01 PM, joel jaeggli wrote:
>> 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
> .
>