Hi Rob,
I’ve taken all your comments. However, I’ve deferred adding the examples as 
this is best done with confd and I don’t have time to get that all setup right 
now.
Thanks,
Acee

From: Robert Wilton <[email protected]>
Date: Monday, February 18, 2019 at 6:19 AM
To: Jeff Tantsura <[email protected]>, Routing WG <[email protected]>, 
Routing WG <[email protected]>, "[email protected]" 
<[email protected]>
Subject: Re: WG Adoption for "RIB YANG Data Model" - 
draft-acee-rtgwg-yang-rib-extend
Resent-From: <[email protected]>
Resent-To: Acee Lindem <[email protected]>, Yingzhen Qu <[email protected]>
Resent-Date: Monday, February 18, 2019 at 6:19 AM


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

[email protected]<mailto:[email protected]>

https://www.ietf.org/mailman/listinfo/rtgwg
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to