This use-case document is a good start. Support, -scott.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Lucy yong Sent: Friday, February 01, 2013 10:55 AM To: Bannai, Vinay; Benson Schliesser; [email protected] Subject: Re: [nvo3] Poll for WG adoption of draft-mity-nvo3-use-case-04 Hello Bannai, Thank you very much for the comment. It is not late at all to contribute on it. Please see in-line. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Bannai, Vinay > Sent: Thursday, January 31, 2013 4:22 PM > To: Benson Schliesser; [email protected] > Subject: Re: [nvo3] Poll for WG adoption of > draft-mity-nvo3-use-case-04 > > Hello, > > This might be a little late but I had a few comments on the use cases. > The use cases do a good job of covering most of the use cases. However > the use cases seem more directed towards the SPDC use cases. [Lucy] not intend to. If you view likely, we are glad to fix it. There are few > use > cases that we are dealing with that requires segmentation of the web- > tiers and the mid-tiers that conform to certain security rules. In > this context, the definition of a tenant gets a little hazy. To give > an example. > The web-tier talks to the mid-tier but depending on the transactions > might have to go through a firewall/policy device that enforces > security rules and zones. This may not be the typical use case, but I > would like to capture this in this document. [Lucy] This is great point. We need to capture this for sure. The teams used in the document may not convey this case clearly. If you think that section 5.3 is more for SPDC, we can modify the description to make it general. A tenant network may contain multiple virtual overlays to provide zoning, the web-tiers, the mid-tiers, and back-tiers. The implementation must allow operator to place the firewall/policy between tiers to enforce inter virtual network communication rules. FYI, we have a lot of intra and inter subnet communication discussions on the mailing list last year. In my mind, that is related to this case. In short, we will make the text clear in the next version. Thanks to bring it out. > > The other use case is when you have a legacy tenant (using > physical[Lucy] > hardware) but new capacity adds are happening in a virtual environment. > The tenant machines are now spread across both physical and virtual > worlds. The other use case case is that of a database or a data store > that happens to reside in the physical world with the VM's in the > virtual world that access them. [Lucy] This is related to gateway. We add some statement about gateway usage (including these cases). It may not be enough. We will check it again. I interpret that you support this document and wish it covering broader scenarios, right? Thanks, Lucy > > -- > Vinay Bannai > 408-967-7784 > Cloud Engineering > PayPal > > > > > > > > On 1/30/13 6:28 PM, "Benson Schliesser" <[email protected]> wrote: > > >This email begins a two week poll to help the chairs judge if there > >is consensus to adopt draft-mity-nvo3-use-case-04 as an NVO3 working > group > >draft. > > > >Please respond to this email on the list with 'support' or 'do not > >support'. > > > >Please also send any comments on the draft to the NVO3 list. > > > >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 poll closes on 14 February 2013. > > > >Cheers, > >-Benson & Matthew > > > >_______________________________________________ > >nvo3 mailing list > >[email protected] > >https://www.ietf.org/mailman/listinfo/nvo3 > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
