I totally agree with Barry Leiba's comment. I mentioned before that charter SHOULD be clear to all readers, as he mentioned not only routing expert participants.
It will be helpful to make references as he mentioned, as I think the documents in the charter already a good reference but no objection to add others. However, I think giving work-examples and referencing initial I2RS work in progress will be a good start for people to know what it is all about. If the RIB and FIB is not described abreviation in the charter it SHOULD do, but it can be defined more in the documents terminology. Thanks for comments, AB On 1/6/13, Adrian Farrel <[email protected]> wrote: > Hi, > > Barry has entered the following comments on the proposed charter. > > Your comments please. > > Adrian > > === > > Block (2012-12-27) > > The second paragraph says this: > > I2RS facilitates real-time or event driven interaction with the > routing system through a collection of control or management > interfaces. These allow information, policies, and operational > parameters to be injected into and retrieved (as read or by > notification) from the routing system while retaining data > consistency and coherency across the routers and routing > infrastructure, and among multiple interactions with the routing > system. > > Nowhere that I can see does it give me any idea what the target of these > interfaces is: what is it that you want having interaction with the routing > system? What is it that will inject information, policies, and operational > parameters, that can't do so now? > > > Comment (2012-12-27) > > Especially because charters, including this one, don't have the sorts of > citations and references that we have in RFCs, it would be helpful to > expand > "RIB" and "FIB" (and, for completeness, "BGP") on first use. I know that > routing people know those terms cold... but some of us don't (Wikipedia > taught > be that they're "Routing Information Base" and "Forwarding Information > Base", > so I'm now better informed). > > _______________________________________________ > i2rs mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i2rs > _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
