Dean, On Wed, Jul 16, 2014 at 04:27:34PM +0000, Dean Bogdanovic wrote: > Jeff Zhang and I've reviewed info model policy draft. > > One general comment (and I'm repeating somebody else). Didn't we decide to > use YANG for all modeling? I see you use RBNF, so it would be nice to have > YANG models in the draft.
We adopted Yang as our data modeling language. Ed and I will be having a discussion with our AD at the upcoming IETF to see about getting our charter formally updated to permit data models. We are also likely to want at least some high level info models for our yang modules. That practice seems to be present elsewhere as well. That said, info models are a perfectly reasonable way to start such a discussion, especially for something that would require a lot of pre-req material if we tried to code for Yang from day 1. If we did, there would be a lot of stubs saying "this ties us to the <foo> component, whose Yang module has yet to be written". Thanks also for submitting your comments. I would like to draw the WG's attention to a github repository I threw together for my own end of comments. In such large drafts, sometimes being able to submit comments in-line along with editorial fixes can be challenging. https://github.com/jhaas-pfrc/i2rs/tree/jhaas/edits01 While I'm not totally signing up to maintain this repository for general editing purposes yet, please feel free to clone it for your own comments. The master branch tracks the current published XML files published by the IETF. The branch above is where I've suggested my edits. The actual edits can be seen in this part of the history: https://github.com/jhaas-pfrc/i2rs/commit/3994b35b561b040c9381c5104ebf7a728ed326e2 I have edits for the BGP-IM in progress as well. -- Jeff (Haas) _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
