Re: [nvo3] draft-drake-nvo3-evpn-control-plane

["NAPIERALA, MARIA H" <[e-mail]>]

Let me refer you the following e-mail (attached) in case you missed it.

Maria


> -----Original Message-----
> From: John E Drake [mailto:[e-mail]]
> Sent: Friday, September 28, 2012 3:38 PM
> To: NAPIERALA, MARIA H; Henderickx, Wim (Wim); Luyuan Fang (lufang);
> Bitar, Nabil N; Fedyk, Donald (Don); [e-mail]
> Subject: RE: [nvo3] draft-drake-nvo3-evpn-control-plane
> 
> Comment inline.
> 
> Yours irrespectively,
> 
> John
> 
> 
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]] On Behalf
> Of
> > NAPIERALA, MARIA H
> > Sent: Friday, September 28, 2012 9:54 AM
> > To: Henderickx, Wim (Wim); Luyuan Fang (lufang); Bitar, Nabil N;
> Fedyk,
> > Donald (Don); [e-mail]
> > Subject: Re: [nvo3] draft-drake-nvo3-evpn-control-plane
> >
> > Since layer 3 can address both intra-subnet and inter-subnet IP
> > communication by a uniform forwarding (i.e., there is no difference
> in
> > forwarding between those two), the question is why to introduce a
> > complication of mixing L2 and L3 forwarding in the *same* solution.
> 
> JD:  Maria, did you invent some new technology that you're not telling
> anyone about?
> 

--- Begin Message ---

Don,

> Hi Maria
> 
> Perhaps I'm missing something but I thought EVPN was built using many of the 
> same building blocks as RFC4364 so that it could be used in combination 
> with EVPN.  In other words IP VPN + EVPN.  

Moreover, section 6.1 of draft-raggarwa-data-center-mobility-03.txt
describes how EVPN can cover inter-VLAN traffic (by forming
EVPN extranets).

Yakov.

> 
> Does that not address your point?
> 
> Thanks,
> Don
> 
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of NAPIE
RALA, MARIA H
> Sent: Monday, September 24, 2012 10:09 AM
> To: [e-mail]
> Subject: Re: [nvo3] draft-drake-nvo3-evpn-control-plane
> 
> I think we should try to clarify what problems or what type of data centers s
pecific solutions are addressing.
> Specifically, EVPN can only address traffic bridged in the same VLAN. In data
 centers where most traffic is inter-VLAN, i.e., packets are routed, the EVPN d
oesn't achieve much as an overall solution.
> I tried to make this point on the webex during the nvo3 interim session when 
draft-drake-nvo3-evpn-control-plane was discussed but I am not sure if my messa
ge went through.
> 
> Maria
> 
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]] On Behalf Of
> > Thomas Nadeau
> > Sent: Monday, September 17, 2012 11:55 AM
> > To: [e-mail]
> > Subject: [nvo3] draft-drake-nvo3-evpn-control-plane
> > 
> > 
> > 	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
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/nvo3
> _______________________________________________
> nvo3 mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/nvo3
> _______________________________________________
> nvo3 mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/nvo3

--- End Message ---