Hi Linda, Please see inline.
- Larry From: Linda Dunbar <[email protected]<mailto:[email protected]>> Date: Monday, September 9, 2013 1:30 PM To: Larry Kreeger <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Questions to draft-ietf-nvo3-nve-nva-cp-req-00 Larry, et al, Section 3 of the draft states that the scenario of NVE residing on a physical network switch is not in the scope being discussed in this draft (last sentence of the second paragraph). LK> Right, it says it is covered in draft-kreeger-nvo3-hypervisor-nve-cp-req which is recently expired, but I am in the process of updating (so it will be back). But the bullet 3 in the same section states: [cid:[email protected]] Are those “End Devices” different from the “Tenant System”? Are there any indication to differentiate “End Devices” from “Tenant Systems”? LK> Yes, these End Devices are not Tenant Systems. As you quoted above "a hypervisor or a Network Service Appliance" is not a Tenant System. Here is the definition from draft-ietf-nvo3-framework: LK>"End Device: A physical device that connects directly to the DC Underlay Network. This is in contrast to a tenant system, which connects to a corresponding tenant VN. An End Device is administered by the DC operator rather than a tenant, and is part of the DC infrastructure. An End Device may implement NVO3 technology in support of NVO3 functions. Examples of an End Device include hosts (e.g., server or server blade), storage systems (e.g., file servers, iSCSI storage systems), and network devices (e.g., firewall, load-balancer, IPSec gateway). " Another question, why have two places to define the NVE-NVA requirement, one for NVE being embedded on Hypervisor, one for NVE being on separate physical switches? LK> The requirements for the NVE to NVA control plane are exactly the same regardless of whether the NVE is embedded within and End Device (e.g. Hypervisor), or in a physical switch. The second paragraph of section 3 is trying to say that the Hypervisor to NVE protocol is covered in draft-kreeger-nvo3-hypervisor-nve-cp-req, not that that embedded NVEs is out of scope for the NVE to NVA control plane. Please let me know how I can reword it to make it more clear. I see the requirement for both scenarios quite similar. Can you elaborate the major differences? LK> It think they are identical. Linda
<<attachment: image003.png>>
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
