draft-ietf-l2vpn-evpn-07 L2 encapsulation?

[Stefan Plug <[e-mail]>]

Hi all,

In regards to draft-ietf-l2vpn-evpn-07:

One thing is not clear to me from the draft, does the L2 frame get
encapsulated by an MPLS tag as with Pseudo Wires, or does the L3 packet
get encapsulated as with normal MPLS?

I have got an answer that indeed the L2 frame in encapsulated, however I
can find no reference to an RFC or details itself in this document where
this is mentioned, to me therefore normal MPLS (RFC3031) applies and
only the L3 packet is encapsulated.

As this draft to my understanding proposes a replacement to VPLS I think
it is necessary to mention or at least reference an RFC on how the
entire L2 frame is to be encapsulated to avoid confusion.

I would suggest a small part mentioning or referencing probably Pseudo
Wires.

Regards,

Stefan Plug, Lutz Engels
MSc Students
System and Network Engineering (www.os3.nl)
University of Amsterdam

On 02-07-14 08:17, Henderickx, Wim (Wim) wrote:
> The packet is encapsulated like a PW using the ETH frame in the MPLS PW.
> 
> On 02/07/14 02:08, "Stefan Plug" <[e-mail]> wrote:
> 
> Dear evpn gurus
> 
> I'm a Networking student at the University of Amsterdam researching
> EVPN as a possible solution to the ARP flooding problem in IXPs.
> 
> One thing is not clear to me from the draft, does the L2 frame get
> encapsulated by an MPLS tag as with Pseudo Wires, or does the L3
> packet get encapsulated as with normal MPLS?
> 
> I cannot seem find any information on this in the draft?
> 
> In the case that normal MPLS rules apply and only the L3 packet is
> encapsulated, what then happens to the source mac address at the end
> of the tunnel?
> 
> I hope you can help me understand your protocol, it seems very
> interesting!
> 
> Regards,
> 
> Stefan Plug
> Student
> System and Network Engineering (www.os3.nl)
> University of Amsterdam
>