On 12/21/12 2:35 PM, Adrian Farrel wrote: > Hi, > > I have ploughed through the emails discussing the charter and come up with > some > minor tweaks. > > 1. "Interface" > There was a strong desire to separate the two meanings of "interface". > However, > the solutions suggested were all rather variable. In fact, the word is only > used > in the first paragraph of the charter, so it seems best to be long-winded for > the sake of clarity. This leads to: > > == > 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 -- 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. More of a nit, but I think the parenthetical portion should read, "(as read or by notification) > 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. > I have made these changes and updated the draft charter at > http://datatracker.ietf.org/doc/charter-ietf-i2rs/ > >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." Joe -- Joe Marcus Clarke, CCIE #5384, | | SCJP, SCSA, SCNA, SCSECA, VCP ||||| ||||| Distinguished Services Engineer ..:|||||||||::|||||||||:.. Phone: +1 (919) 392-2867 c i s c o S y s t e m s Email: [email protected] ---------------------------------------------------------------------------- _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
