Lucy, > I also want to raise a question regarding the WG process.
> Last IETF (IETF83) had NVo3 BOF.(I heard that was well done) NVo3 WG > is just formed on May 1 2012. The framework draft 00 was just > published in March 2012. The 02 uploaded recently has fair amount of > changes from 01. There is no changes section, but the main changes are adding terminology (pulling it out of draft-kreeger-nvo3-overlay-cp-00.txt to be specific) and then making changes to align up the terminology. It was a goal to align the terminology in all three of the drafts: draft-kreeger-nvo3-overlay-cp-00.txt draft-narten-nvo3-overlay-problem-statement-02.txt draft-lasserre-nvo3-framework-02.txt I don't think one can really argue that there are major/substantive changes to the framework document. > Why do the WG want rapidly adopting the draft into WG draft. Are > there some DC operator want this badly? It seems the time line in > the charter is not the reason. Frankly, this set of works are > pretty new to IETF people. It should give people more time to think > and contribute. Urgency in getting started? Perhaps not. Desire to move slowly? Absolutely not. ;-) The IETF moves pretty slow on the whole, and as it is, it will take us until the end of the year/early next year to get to the point of rechartering (according to the WG milestones). The call for adopting the document as a WG document isn't saying the document is finished or won't change. What it would say is that the framework document is the one that WG will use as basis for moving forward, as opposed to, say, developing a completely different document, or waiting for additional submissions and then picking from them or figuring out how to merge them into one. IMO, the framework doc is a good base to start with and I support the WG adopting it. If there are specific issues with the document that anyone thinks needs addressing, please raise them. It is perfectly OK to raise issues with the document and at the same time support making the document a WG document. Thomas _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
