Following the recent Call for Adoption discussion, the chairs believe there is consensus to adopt draft-rekhter-nvo3-vm-mobility-issues-03.txt as a NVO3 working group document.
However, the chairs are concerned that there are other drafts that contain related text. We would like to see discussion on the list about whether this text should be included or abandoned. We do not intend to adopt multiple WG drafts on the same topic. Please can the authors of draft-rekhter upload a new version of the document with the name changed to draft-ietf-nvo3-vm-mobility-issues-00.txt. Please can participants review this draft, and comment on the list if you believe there is additional draft material that should be incorporated, providing an explicit pointer to that material. We would like to see discussion on this list so that we can see whether or not there is consensus to include it. We then expect the editors of draft-ietf-nvo3-vm-mobility-issues-00.txt to reflect that consensus in a new version of the draft, as needed. Best regards, Matthew and Benson On 29/11/2012 17:52, "Bocci, Matthew (Matthew)" <[email protected]<mailto:[email protected]>> wrote: There have been a number of requests for the WG to adopt draft-rekhter-nvo3-vm-mobility-issues-03.txt as a working group draft. There has also been some discussion on the list and in Atlanta as to whether VM mobility requirements and problem statement issues should be addressed in a stand alone draft or as a part of the existing problem statement. There are also a number of other drafts addressing this issue, so if draft-rekhter is adopted as a stand alone working group document, then that will provide the base working group document into which any additional text would be added. In order to help the chairs determine how to progress on this issue, please can you indicate to the list: * Do you support adoption of this draft as-is (yes/no)? * If no, would you support adoption of this draft with changes, and if so, what (e.g. more Layer 3 content)? * If no, should all of the VM mobility problem statement be added to the NVO3 problem statement draft? Coincidentally, we are also polling for knowledge of any IPR that applies to this draft, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor, please respond to this email whether or not you are aware of any relevant IPR. The draft will not be adopted until a response has been received from each author and contributor. If you are on the NVO3 WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. This call for consensus will close on Thursday 13th December 2012. Best regards Matthew and Benson
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
