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

"Rabadan, Jorge (Jorge)" <jorge.rabadan@alcatel-lucent.com> Wed, 02 July 2014 12:32 UTC

Return-Path: <jorge.rabadan@alcatel-lucent.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534411A008D for <l2vpn@ietfa.amsl.com>; Wed, 2 Jul 2014 05:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CObyk4J3ILs for <l2vpn@ietfa.amsl.com>; Wed, 2 Jul 2014 05:32:03 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A03101A0087 for <l2vpn@ietf.org>; Wed, 2 Jul 2014 05:32:00 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s62CVwOe006658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Jul 2014 07:31:59 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s62CVvO1032252 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 2 Jul 2014 14:31:57 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.230]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Wed, 2 Jul 2014 14:31:57 +0200
From: "Rabadan, Jorge (Jorge)" <jorge.rabadan@alcatel-lucent.com>
To: Stefan Plug <Stefan.Plug@os3.nl>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Re: draft-ietf-l2vpn-evpn-07 L2 encapsulation?
Thread-Topic: draft-ietf-l2vpn-evpn-07 L2 encapsulation?
Thread-Index: AQHPleyUCOSAI8EGhkSF3sIxhdWM2JuMIH0A
Date: Wed, 2 Jul 2014 12:31:57 +0000
Message-ID: <CFD944D8.46836%jorge.rabadan@alcatel-lucent.com>
References: <53B34D99.403@os3.nl> <CFD9704E.DBB54%wim.henderickx@alcatel-lucent.com> <53B3F320.1000301@os3.nl>
In-Reply-To: <53B3F320.1000301@os3.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.2.140509
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="utf-8"
Content-ID: <62E03D826368A343931330911ABDEEE2@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/TbtjarMQZ0yqnT6wEetIMxxTk1Q
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jul 2014 12:32:07 -0000

Stefan,

The evpn draft is full of references to “Ethernet frames transported over
IP/MPLS”, which in my opinion, along with the description in section 6 and
other sections should be enough to clarify the stack.

Having said that, in the WG, we agreed to publish a evpn use-case draft
that could help clarify the main control plane and data plane concepts in
evpn:
http://tools.ietf.org/html/draft-rp-l2vpn-evpn-usage-02


What I would suggest is to use that draft as a way to clarify all those
things so that the evpn researcher/implementer can use it as a reference.
If you agree, please go through it and suggest any additions. We would be
happy to discuss and address them if possible.

Thanks.
Jorge

-----Original Message-----
From: Stefan Plug <Stefan.Plug@os3.nl>
Date: Wednesday, July 2, 2014 at 4:55 AM
To: "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: draft-ietf-l2vpn-evpn-07 L2 encapsulation?

>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" <Stefan.Plug@os3.nl> 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
>> 
>