Hi, Melinda: Sorry for the delayed reply. I agree there should be security analysis work in each requirement document. However, I believe NVO3 networks could be very complex, and it is reasonable, at least at the moment, for us to analyze the system in a comprehensive way instead of splitting them into different parts and analyzing them respectively, since, for example, the attacks on a component may be a step of a more complex attack targeting another component and the security issues with the data plane may also be applied to attack the control plane. In addition, it is also useful for us to make a good threat model and reasonable assumptions of attacking capability before specifying the security requirements for data and control planes. It is very important for us to agree upon which security properties that we should guarantee and what kind of attacks we need to consider before moving forward.
So, I think it is proper to put the work mentioned above into an individual document. But if the group would like us to put the conclusion of our analysis into other documents or help the authors of other documents do the security related work, we would be very happy to do so. ^_^ Cheers Dacheng > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Melinda Shore > Sent: Saturday, August 24, 2013 1:22 AM > To: [email protected] > Subject: Re: [nvo3] Poll for WG adoption of > draft-hartman-nvo3-security-requirements-01 > > On 8/23/13 7:22 AM, Bocci, Matthew (Matthew) 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. > > What's the reason for not incorporating this material into > the other requirements drafts? I think that the text is a > good start but I am generally not that enthusiastic about > moving security issues into separate documents unless > there's a compelling reason. > > Melinda > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
