Juergen, When I2RS recharters, I am certain that I'll hear your input. I am much less interested in rules-mongering and trying to pick holes (the lack of "generic" before an unqualified topology in the charter) than I am in gathering people who are doing real work on topology to get it DONE finally.
Those interested in SUPA were told very clearly before last IETF that the topology work was already being addressed in I2RS. You haven't chosen to participate in progressing the actual work. As for understanding how the IETF works, all the words in the world don't help if the recipient isn't willing to listen. Alia On Wed, Mar 4, 2015 at 6:22 PM, Juergen Schoenwaelder < [email protected]> wrote: > On Wed, Mar 04, 2015 at 04:52:14PM -0500, Alia Atlas wrote: > > Hi Benoit, > > > > Yes, as is clearly articulated in the draft,it is a generic topology into > > which all other topology-related work should > > plug. > > > > I2RS and Alex are very happy to hear comments and reviews of that draft. > > > > Alia, > > I like to see this clarified in the charter. The current charter says: > > o The ability to extract information about topology from the > network. Injection and creation of topology will not be > considered as an initial work item. > > If the work of I2RS has been expanded to do generic topology work, > then I think it is necessary to document that by updating the WG > charter. Frankly, it seems there is more stuff in the current charter > that does not seem to reflect the WGs and ADs understanding of what > I2RS works on. Anyway, pointing to an individual I-D in order to > define what that scope of the work of I2RS is making it really hard > for others to understand how the IETF works. > > /js > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
