Maria, LuYuan, and Dennis Your draft (http://www.ietf.org/id/draft-fang-vpn4dc-problem-statement-01.txt ) demonstrates the approaches on how to extend L3VPN to end systems in data center. "draft-narten-nvo3-problem-statement" describes the issues facing data centers with massive number of VMs interconnected by virtualized switches.
Majority of text in your draft is on how L3VPN can be extended to Data Center. It would be good solution draft, because some tenants do want to extend their VPNs (L2 or L3) into data centers. If you want to merge your draft to general NVo3 problem statement, a lot of sections in your draft need to be removed. For example, Section 7 on how MAC addresses should not be used, etc. MAC addresses don't have to be used in the solution described in your draft. But not all data centers will use L3VPN. Many data centers don't have any end systems which are part of any L3VPN; Many data centers only allow IPSec tunnels terminated at their gateways; Some multi-tenant data centers have to use L2 among VMs due to their tenant's requirement. Since NVo3 current charter is only on studying problems and identify requirement, it might be worthwhile to revise your draft focusing only on the problems facing data centers when some tenants need to extend their L3VPN to VMs within data centers. Linda Dunbar > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Yakov Rekhter > Sent: Thursday, June 21, 2012 2:44 AM > To: Benson Schliesser > Cc: Matthew (Matthew) Bocci; Luyuan Fang (lufang); [email protected]; > Dennis Cai (dcai); Pedro Marques; draft-narten-nvo3-overlay-problem- > [email protected]; [email protected] > Subject: Re: [nvo3] call for adoption: draft-narten-nvo3-overlay- > problem-statement-02 > > Benson, > > > Dear NVO3 Participants - > > > > This message begins a two week Call for Adoption of > > http://tools.ietf.org/html/draft-narten-nvo3-overlay-problem- > statement-02 > > by the NVO3 working group, ending on 30-June-2012. > > > > Please respond to the NVO3 mailing list with any statements of > approval > > or disapproval, along with any additional comments that might explain > > your position. Also, if any NVO3 participant is aware of IPR > associated > > with this draft, please inform the mailing list and/or the NVO3 > chairs. > > Before considering adoption of draft-narten-nvo3-overlay-problem- > statement, > we should consider how this draft is related to > draft-fang-vpn4dc-problem-statement (see below) ? Do these two drafts > cover the same topic ? Are they complementary with each other ? > Should both of these drafts be merged into a single draft, before > being adopted by the NVO3 working group ? > > Yakov. > > ----------------------------------------------------------------------- > Date: Wed, 20 Jun 2012 10:50:53 CDT > To: <[email protected]> > cc: Pedro Marques <[email protected]>, [email protected], > "Dennis Cai \(dcai\)" <[email protected]> > From: "Luyuan Fang (lufang)" <[email protected]> > Subject: [nvo3] FW: New Version Notification fordraft-fang-vpn4dc- > problem-sta > ***tement-01.txt > > Dear colleagues, > > We have uploaded a new updated version of draft-fang-vpn4dc-problem- > statement > -01.txt (on 6/12), by Maria Napierala, Dennis Cai, and myself. > Appreciate your review and comments. > > Thanks, > Luyuan > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Tuesday, June 12, 2012 10:48 PM > To: Luyuan Fang (lufang) > Cc: [email protected]; Dennis Cai (dcai) > Subject: New Version Notification fordraft-fang-vpn4dc-problem- > statement-01.t > xt > > > A new version of I-D, draft-fang-vpn4dc-problem-statement-01.txt > has been successfully submitted by Luyuan Fang and posted to the > IETF repository. > > Filename: draft-fang-vpn4dc-problem-statement > Revision: 01 > Title: IP-VPN Data Center Problem Statement and > Requirements > Creation date: 2012-06-12 > WG ID: Individual Submission > Number of pages: 18 > URL: http://www.ietf.org/internet-drafts/draft-fang-vpn4dc- > proble > m-statement-01.txt > Status: http://datatracker.ietf.org/doc/draft-fang-vpn4dc- > problem-st > atement > Htmlized: http://tools.ietf.org/html/submission.filename }}-01 > Diff: http://tools.ietf.org/rfcdiff?url2=draft-fang-vpn4dc- > problem > -statement-01 > > Abstract: > Network Service Providers commonly use BGP/MPLS VPNs [RFC 4364] as > the control plane for virtual networks. This technology has proven > to scale to a large number of VPNs and attachment points, and it is > well suited for Data Center connectivity, especially when > supporting all IP applications. > > The Data Center environment presents new challenges and imposes > additional requirements to IP VPN technologies, including multi- > tenancy support, high scalability, VM mobility, security, and > orchestration. This document describes the problems and defines the > new requirements. > > > > > > > The IETF Secretariat > _______________________________________________ > 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
