Matthew, Snipped, comment inline.
Thanks, John Sent from my iPhone Why not just rephrase the paragraph so that it does not appear to prescribe protocol development, but rather scopes the solutions to those that the IETF traditionally deals with and that meet the requirements/gap analysis?: "NVO3 will consider an approach to multi-tenancy that uses a Layer 3 encapsulation rather than relying on traditional L2 isolation mechanisms (e.g., VLANs) to support multi-tenancy, and consistent with a requirements gathering and gap analysis exercise. The approach will provide an emulated Ethernet service capable of satisfying typical data center deployments." [JD] I also have a problem with the last sentence as it sounds as though NV03 will be encroaching on the charter of the L2VPN WG, which reads, in part: "The L2VPN working group is responsible for defining and specifying a limited number of solutions for supporting provider-provisioned Layer-2 Virtual Private Networks (L2VPNs). It will also address requirements driven by cloud computing services and data centers as they apply to Layer-2 VPN services." And: "5. Ethernet VPN (E-VPN) - An enhanced Layer-2 service that emulates an Ethernet (V)LAN across a PSN. E-VPN supports load-sharing across multiple connections from a Layer-2 site to an L2VPN service. E-VPN is primarily targeted to support large-scale L2VPNs with resiliency requirements not satisfied by other L2VPN solutions."
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
