Thanks Joe, > > A routing system is all or part of a routing network. A part of a routing > > network may be a single router or a collection of routers. The routing system > > may be further divided to be an interface over which data traffic is forwarded, > > or a collection of such interfaces. > > > > 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 notification) from the routing system while retaining data > > consistency and coherency across the routers and routing infrastructure, and > > between multiple interactions with the routing system. > > I know this was bikeshedded quite a bit --
A bit? ;-) > and I have no objection to > the dual meaning -- but I do think that these two paragraphs mix > "interface" in a way that might be confusing. A "router" already has a > management "interface" (either virtual or physical) and that is > independent of the "interface" mentioned in paragraph two. > Unfortunately, I don't have a better suggestion other than putting the > word "programmatic" or "structured" in there to help disambiguate the > two uses. However, since this has been beaten to death, and this is > what the majority agrees to, then so be it. I think many object to programmatic on account of we are not building an API, but a protocol. While "interface" now appears multiple times in the paragraphs, each is specifically qualified. > More of a nit, but I think the parenthetical portion should read, "(as > read or by notification) Yes > > Aug 2013 : Request publication of Informational documents describing use > cases > > While it's written correctly here, you have two 'b's in "describing" in > the web charter. Two b's or not two b's? > From the web charter: > > "The I2RS working group works to develop a framework and architecture > that will enable specific use cases, and lead to an understanding of the > informational models and requirements for encodings and protocols. Small > and well-scoped use cases are critical to constrain the scope of the > work and achieve sufficient focus for the working group to deliver > successfully. Initial work within the working group will be limited to > within a single administrative domain." > > Another grammatical nit, but perhaps the last two sentences could read: > > "Small and well-scoped use cases are critical to constrain the scope of > the work an achieve sufficient focus for the working group to deliver > successful outcomes. Initial work within the working group will be > limited to a single administrative domain." I've made these changes. Cheers, Adrian _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
