Hi Mahesh, I think that if we leave structure to the WGs, we will end up with models that have a WG-centric view with their corresponding model being at the root and any instantiation (logical-network-element, networking-instance, VRF, etc) being done within the model. Is this what we want? In routing, we had the benefit of the routing-cfg model also being considered and concluded the debate in favor of adopting the routing-cfg structure for the routing protocol models.
Thanks, Acee From: Mahesh Jethanandani <mjethanand...@gmail.com<mailto:mjethanand...@gmail.com>> Date: Friday, August 28, 2015 at 7:44 PM To: Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>> Cc: Martin Bjorklund <m...@tail-f.com<mailto:m...@tail-f.com>>, "r...@rob.sh<mailto:r...@rob.sh>" <r...@rob.sh<mailto:r...@rob.sh>>, "netmod@ietf.org<mailto:netmod@ietf.org>" <netmod@ietf.org<mailto:netmod@ietf.org>> Subject: Re: [netmod] Motivations for Structuring Models Acee, This is going to become very interesting very quickly. Routing DT has decided to define a container for oam-protocols. LIME has decided it wants to define a generic YANG module for all OAM in draft-tissa-lime-yang-oam-model. Which model does BFD augment? Or did you just kill the whole charter for LIME?? On Aug 28, 2015, at 6:20 AM, Acee Lindem (acee) <a...@cisco.com<mailto:a...@cisco.com>> wrote: Why doesn’t it help? In the next revision of the Routing YANG DT model, we’ve switched from including specific models to defining classes of models with identities. For example, grouping oam-protocols { container oam-protocols { list oam-protocol { key "type"; leaf type { type identityref { base oam-protocol-type; } mandatory true; description "The Operations, Administration, and Maintenance (OAM) protocol type, e.g., BFD, TWAMP, CFM, etc."; } description "List of OAM protocols configured for a networking instance."; } description "Container for list of OAM protocols configured for a networking instance."; } description "Grouping for OAM protocols configured for a networking instance."; } Then the grouping is include the networking-instances. By doing this, the intent is that it would be evident as to where a particular model would be found. Mahesh Jethanandani mjethanand...@gmail.com<mailto:mjethanand...@gmail.com>
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
