|
Hello Lada, I want a formal way to define mount data. I want tools to
understand it, so RFC text or an unspecified file is a not a good
solution. We could have described any data model in plain English. The
whole point of YANG is to have a formal definition. If containing
one container in another is described in a formal way why is
containing a full module in a container less important? My solution would only use standard YANG files with a well
specified content. I need the same level of precision from any
alternative. Balazs On 2016-07-28 16:14, Ladislav Lhotka
wrote:
Solution: My problem is that the specific data in the yang-library or in ietf-yang-schema-mount is only defined and available in run-time, so I don't understand how it could solve the design-time schema-mount requirement. IMHO whatever the solution, it needs to be in a file.YANG library data can appear in the RFC text, in a file, or elsewhere off line.We could do the same with "mount-points" data as defined in draft-ietf-netmod-schema-mount-02 but only with one level of mounts. -- Balazs Lengyel Ericsson Hungary Ltd. Senior Specialist Mobile: +36-70-330-7909 email: [email protected] |
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
