Hi Larry, I do remember this discussion and I think this level of details should fall within the architecture document and not the framework document.
Thanks, Marc ________________________________ From: Larry Kreeger (kreeger) [mailto:[email protected]] Sent: Friday, September 20, 2013 4:11 AM To: LASSERRE, MARC (MARC); Pat Thaler; Benson Schliesser; [email protected] Subject: Re: [nvo3] WGLC for draft-ietf-nvo3-framework-03 Hi Marc, There was a fairly long email thread (actually a few) on the list regarding Tenant System Interfaces and how they relate to the VAPs, especially when the NVE is external to a hypervisor (search for threads with TSI in the subject). I was hoping the Framework could define TSI and illuminate the relationship of TSI to VAP (e.g. cardinality). I think this is the proper place for this. - Larry From: <LASSERRE>, "MARC (MARC)" <[email protected]<mailto:[email protected]>> Date: Thursday, September 19, 2013 3:04 AM To: Pat Thaler <[email protected]<mailto:[email protected]>>, Benson Schliesser <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [nvo3] WGLC for draft-ietf-nvo3-framework-03 Thanks Pat for your feedback. The framework is meant to provide a high-level view of the main nvo3 components. The architecture draft, draft-narten-nvo3-arch, is meant to provide add'l details. In this latter draft, there is text about the relationship between hypervisors, TS's abd NVE's. We have the following options: - Leave the framework draft as is and let the architecture draft provide further details - Cut and paste some text from the architecture draft - You could provide specific text that you'd like to see included in the framework draft (after WG review) I'm fine either way even if I favor the first option ;-) Let's hear from the WG and chairs. Marc ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Pat Thaler Sent: Friday, September 13, 2013 9:17 PM To: Benson Schliesser; [email protected]<mailto:[email protected]> Subject: Re: [nvo3] WGLC for draft-ietf-nvo3-framework-03 The framework is in pretty good shape but not quite ready. I am concerned that the framework is fuzzy on the relationship of hypervisors to tenant systems and NVEs. This became apparent during recent discussions on the security draft. I looked at the framework and the control plane drafts to see what they said before posting. The figures in the framework don't show the hypervisor - TS just connects to the NVE when in cases where the TS is a VM the hypervisor would be between them. The figures in the hypervisor NVE draft show the hypervisor as containing the VMs but they don't show the TS. "Hypervisor" only appears in the terminology section in the definition of NVE (which says the NVE could be part of a hypervisor virtual switch), in its own definition, and in the definitions of server and virtual switch. Clearly the role of the hypervisor in the framework should be described beyond that. At least, its role in communicating about TSes to the NVE and controlling the network behavior of TSes that it hosts (e.g. filtering). Regards, Pat From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Benson Schliesser Sent: Thursday, September 12, 2013 8:08 PM To: [email protected]<mailto:[email protected]> Subject: [nvo3] WGLC for draft-ietf-nvo3-framework-03 This email begins a one week working group last call for draft-ietf-nvo3-framework-03. Please review the draft and post any comments to the NVO3 list. This working group last call will end on Friday 20-September-2013. Cheers, -Benson & Matthew
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
