The chairs have discussed the comments on this draft and believe there is sufficient consensus to adopt it as an NVO3 working group draft.
Having a single security requirements draft provides a useful focus for the working group. However, as a number of participants have also pointed out, individual requirements and solutions drafts need to have their own security considerations sections. These can either refer to the relevant sections of the security draft, or they can introduce their own text, as long as it is constant with the security draft. There have also been a few comments regarding the technical content of the draft. With this in mind, please can the authors of draft-hartman upload a new version of the draft with the connect unchanged but the name of the draft changed to draft-ietf-nvo3-security-requirements-00. Please can they then work with the people who posted comments to resolve them and post a new revision (v01) of the WG draft as soon as possible. Regards, Matthew and Benson On 23/08/2013 16:22, "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-hartman-nvo3-security-requirements-01.txt as an NVO3 working group draft. The draft can be found here: http://tools.ietf.org/id/draft-hartman-nvo3-security-requirements-01.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
