Andy Bierman <[email protected]> writes: > On Thu, Jan 24, 2013 at 8:36 AM, Ladislav Lhotka <[email protected]> wrote: > >> >> On Jan 24, 2013, at 5:26 PM, Juergen Schoenwaelder < >> [email protected]> wrote: >> >> > On Thu, Jan 24, 2013 at 11:13:44AM -0500, Alia Atlas wrote: >> >> Juergen, >> >> >> >> What would you recommend for an information model for i2rs? >> >> >> > >> > Frankly, I do not know. I am still unsure what the scope/complexity of >> > i2rs really is. To find out, I guess people just have to pick >> > something and get started. YANG tree diagrams are fine to get a quick >> > overview of YANG data models, they likely won't be the right tool if >> > many of data model items with more complex interrelationships are >> > involved - then you need additional diagrams. >> >> I like the approach of RFC 6728 which combines UML with YANG. >> >> > How about both?. The first step is to understand the data structures > at a high level and how they relate to each other. The IPFIX approach > is best for that. The next step is understanding each data structure
I agree. The authors of 6728 use a semi-formal procedure for mapping UML diagrams to YANG structures: object properties are represented as YANG groupings, aggregated components as subordinate nodes and unidirectional associations as leafrefs. And then they fill in the details in YANG. Lada > in more detail and YANG tree diagrams are good for that. I agree with Tom > that the syntax is not completely intuitive. > > > >> Lada >> >> > Andy -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: E74E8C0C _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
