Yes, add MPLS-in-UDP encap. It is described in http://tools.ietf.org/html/draft-xu-mpls-in-udp-02
See below. Lucy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kireeti Kompella Sent: Tuesday, September 18, 2012 11:40 AM To: Thomas Nadeau Cc: [email protected] Subject: Re: [nvo3] draft-drake-nvo3-evpn-control-plane Cool, very happy to see this! A couple of comments: 1) spell out that a tunnel attr with encap GRE means MPLS-in-GRE. 2) sect 6 and first para of 6.1: make a note that BUM traffic may not need to be transported. In particular, unknown unicast is not needed, broadcast for ARP likewise. 3) why the funky four reserved bits for VNID? Leave it as 24 bit IDs ... 4) I like the idea of local VNIDs, but need to bounce that off the respective draft authors. 5) add an MPLS-in-UDP encap. Kireeti Sent from my iPad On Sep 17, 2012, at 8:55, Thomas Nadeau <[email protected]> wrote: > > A number of us just published this draft and wanted to bring it to the NVO3 > WG's attention. We will be presenting/discussing this draft at the interim > meeting this week as well, but please discuss here on the list as well. > > Thanks, > > Tom, John, et al > > > A new version of I-D, draft-drake-nvo3-evpn-control-plane-00.txt > has been successfully submitted by Thomas D. Nadeau and posted to the > IETF repository. > > Filename: draft-drake-nvo3-evpn-control-plane > Revision: 00 > Title: A Control Plane for Network Virtualized Overlays > Creation date: 2012-09-16 > WG ID: Individual Submission > Number of pages: 12 > URL: > http://www.ietf.org/internet-drafts/draft-drake-nvo3-evpn-control-plane-00.txt > Status: > http://datatracker.ietf.org/doc/draft-drake-nvo3-evpn-control-plane > Htmlized: > http://tools.ietf.org/html/draft-drake-nvo3-evpn-control-plane-00 > > > Abstract: > The purpose of this document is to describe how Ethernet Virtual > Private Network (E-VPN) can be used as the control plane for > Network Virtual Overlays. Currently this protocol is defined to > act as the control plane for Virtual Extensible Local Area > Network (VXLAN), Network Virtualization using Generic Routing > Encapsulation (NVGRE), MPLS or VLANs while maintaining their > existing data plane encapsulations. The intent is that this > protocol will be capable of extensions in the future to handle > additinal data plane encapsulations and functions as needed. > > > _______________________________________________ > 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
