On 8/28/15, 9:24 AM, "Martin Bjorklund" <m...@tail-f.com> wrote:
>"Acee Lindem (acee)" <a...@cisco.com> wrote: >> >> >> On 8/28/15, 8:55 AM, "netmod on behalf of Martin Bjorklund" >> <netmod-boun...@ietf.org on behalf of m...@tail-f.com> wrote: >> >> >Rob Shakir <r...@rob.sh> wrote: >> >> >> >> Hi Martin, >> >> >> >> Thanks for the reply. >> >> > Martin Bjorklund <mailto:m...@tail-f.com> >> >> > August 28, 2015 at 02:33 >> >> > So the idea is that this structure is defined in one module, >> >> > ietf-something-structure, right? >> >> > >> >> > And then different oam protocol modules augment this structure? >> >> > >> >> > How does this help you find the modules that augment this >>structure? >> >> Yes, this is the intention. By then generating the tree of the >>overall >> >> structure, then I can see what different containers are created >> >> there. It's not perfect (and hey, this suggestion is a *draft* for a >> >> reason - but yet again, there are not alternatives) - but the fact >> >> that the modules augment a common path adds some information that >>they >> >> are grouped to providing the same functionality, not >> >> disparate. ietf-routing does the same thing, it gives me the fact >>that >> >> at /routing/routing-instance/routing-protocols there are a bunch of >> >> control-plane protocols that are related to routing. >> > >> >Ok. So your proposal doesn't help with the problem of locating >> >relevant YANG modules, but once their located, it is easier to find >> >the ones related to a specific function, b/c they would augment a >> >common path. Is this what you mean? >> >> 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. > >Now I am a user of YANG models. I am searching for the YANG module >that defines OAM for BFD. How does your model above help me find it? If one can envision a function to list the schema rather than the actual config data, you could retrieve the schema for the oam-protocols container. It would seem reasonable to support such a function. Thanks, Acee > > >/martin _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
