Re: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend

Robert Wilton <rwilton@cisco.com> Mon, 18 February 2019 11:19 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4E94130ED4; Mon, 18 Feb 2019 03:19:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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, 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 dwzoGjA7SZ5B; Mon, 18 Feb 2019 03:19:12 -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 56EC3130EB0; Mon, 18 Feb 2019 03:19:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6449; q=dns/txt; s=iport; t=1550488751; x=1551698351; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=+lvdblYHHoD/4fyZbi3zBBrHLHgMCy47mDtJ5LXNLH8=; b=iXmQIdPOSO5KjXFVP+MGyo3BQ67X++X+Rh+J+sRUYM2MDrkGqVN0qeIE r+MnyfpiG0CScM+P68Hh3IGz32pVmkh3EymED0+qTxAEWU0mQsBDRcEg+ rgBchh78v9BYeCfo4XfjybtjtRw98WQoNHwPZF8wE4NYrJUS8kzLlfOBY w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A+AABsk2pc/xbLJq0YAUoaAQEBAQECAQEBAQcCAQEBAYFTAwEBAQELAQGBDIFcUSASJ4x/jGQtkimFcRSBZw0YAQqESQKEETYHDQEDAQECAQECbRwMhUsBAQEDAQFsBAIVCxguJzAGAQwGAgEBgxwBgXIPjBCgch+FJYReBYxbgUA/gTiCa4MeAQGBKQUBEgGFfwKXQowCCYpvh2IGGYFwhVWDGoghikOKe4cngU0DLmVxMxoIGxU7gmyLHoU/PwMwjSeCPgEB
X-IronPort-AV: E=Sophos; i="5.58,384,1544486400"; d="scan'208,217"; a="10200953"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Feb 2019 11:19:09 +0000
Received: from [10.63.23.93] (dhcp-ensft1-uk-vla370-10-63-23-93.cisco.com [10.63.23.93]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id x1IBJ8t3020492; Mon, 18 Feb 2019 11:19:09 GMT
Subject: Re: WG Adoption for "RIB YANG Data Model" - draft-acee-rtgwg-yang-rib-extend
To: Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, Routing WG <rtgwg-chairs@ietf.org>, draft-acee-rtgwg-yang-rib-extend@ietf.org
References: <d352c810-1b50-4843-b86d-45f1e9d08257@Spark> <a95eb664-4a20-458d-a894-93693c9e31eb@Spark>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <b0d9411f-19ad-2cef-359e-b722ac84e5ad@cisco.com>
Date: Mon, 18 Feb 2019 11:19:08 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <a95eb664-4a20-458d-a894-93693c9e31eb@Spark>
Content-Type: multipart/alternative; boundary="------------79DD52C55CD25D2F78371FD8"
Content-Language: en-US
X-Outbound-SMTP-Client: 10.63.23.93, dhcp-ensft1-uk-vla370-10-63-23-93.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/mMPhh024z_UG6913rQ8iB0-Eu1M>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2019 11:19:14 -0000

Support.

I think that it is important for IETF to continue to work towards 
complete YANG models for managing network devices, and I see this work 
as another part of that.

To the authors, please may I also suggest:
1) Referencing RFC 8340 for the tree diagram text in section 4. E.g. the 
current explanation text could be replaced with something like:

    The tree associated with the "ietf-rib-extensions" module follows.  The
    meaning of the symbols can be found in [RFC8340].

2) Perhaps adding the full tree output (i.e. inc the nodes from RFC8349) 
into an appendix.  As long as it is not too verbose, seeing the entire 
structure can be helpful for folks checking completeness, and for 
understanding the structure.

3) Adding some examples to the appendix.  No need to do every 
augmentation where the same groupings are being used, but seeing the 
output can greatly help the reader properly understand the structure and 
relationship between the data described in the model.

Thanks,
Rob


On 15/02/2019 19:18, Jeff Tantsura wrote:
> Dear RTGWG,
>
> The authors have requested the RTGWG to adopt 
> draft-acee-rtgwg-yang-rib-extend
> as the working group documents.
>
> The authors have addressed the comments raised.
>
> Please indicate support or no-support by March 3rd, 2019.
>
> If you are listed as a document author or contributor please
> respond to this email stating of whether or not you are aware of
> any relevant IPR. The response needs to be sent to the RTGWG
> mailing list. The document will not advance to the next stage
> until a response has been received from each author and each
> individual that has contributed to the document.
>
> Cheers,
> Jeff
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg