The chairs have discussed the comments on list, but it looks like there is insufficient consensus to adopt this version as an NVO3 working group draft at this time.
There were a number of comments relating to the scope of the draft and whether it should address general operational requirements, or OAM specifically. Certainly, the original intent when this was raised at the BoF (and reflected in the charter) seemed to be OAM requirements i.e. to ensure adequate OAM tools to manage NVO3 networks in a data center. We'd suggest that the authors of the draft revise the draft, in particular resolving the comments related to scope. Best regards, Matthew and Benson On 23/08/2013 16:19, "Bocci, Matthew (Matthew)" <[email protected]<mailto:[email protected]>> wrote: This email begins a two week poll to help the chairs determine if there is consensus to adopt draft-ashwood-nvo3-operational-requirement-03.txt as an NVO3 working group draft. The draft can be found here: http://tools.ietf.org/id/draft-ashwood-nvo3-operational-requirement-03.txt Please read the draft and indicate to the list if you support adoption, or if you do not support adoption (giving reasons). Please note that this is only a call for adoption. There needs to be consensus that this draft is a good basis for the work, but it does not need to be perfect at this stage. The poll for adoption will close in two weeks time, on Friday 6th September. Best regards, Matthew and Benson
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
