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]] On Behalf Of Benson Schliesser Sent: Thursday, September 12, 2013 8:08 PM To: [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
