I think that the outstanding issue is what to do with long tree diagrams. Yes, we have discussed it and have a statement about one page being a good idea but very few of the I-Ds I see can manage that.
RIP has four pages, NAT has six. OSPF and BFD have divided the diagram up but many if not most of the subdivisions still exceed one page (I would regard two as more or less ok but many exceed that). My own take is that a too long tree diagram reflects a too flat module structure, just as many years ago, code would be a long unbroken sequence and now is divided up into manageable modules, so a YANG module should be structured as smaller pieces, bite-size chunks, and a tree diagram of one page is a good indicator of a manageable chunk size. Tom Petch ----- Original Message ----- From: "joel jaeggli" <joe...@bogus.com> Sent: Monday, January 01, 2018 10:01 PM Greetings, We hope the new year is a time to make great progess on outstanding documents before preparation for the London IETF begins in earnest. This starts a two-week working group last call on: YANG Tree Diagrams draft-ietf-netmod-yang-tree-diagrams https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-tree-diagrams/ Please send email to the list indicating your support or concerns. We are particularly interested in statements of the form: * I have reviewed this draft and found no issues. * I have reviewed this draft and found the following issues: ... Thank you, NETMOD WG Chairs ------------------------------------------------------------------------ -------- > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod > _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
