IETF Logo Mail Archive

Re: [l2vpn] WG adoption call for the draft "Usage and applicability of BGP MPLS based Ethernet VPN", draft-rp-l2vpn-evpn-usage-02

"Rabadan, Jorge (Jorge)" <jorge.rabadan@alcatel-lucent.com> Wed, 15 October 2014 02:14 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 4A78A1A014E for <l2vpn@ietfa.amsl.com>; Tue, 14 Oct 2014 19:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level:
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] 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 bvRs_ZDtRfaa for <l2vpn@ietfa.amsl.com>; Tue, 14 Oct 2014 19:14:39 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D9D71A0140 for <l2vpn@ietf.org>; Tue, 14 Oct 2014 19:14:39 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 42E54E8DC9788; Wed, 15 Oct 2014 02:14:36 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s9F2EaQu026514 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Oct 2014 04:14:36 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.75]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Wed, 15 Oct 2014 04:14:36 +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: [l2vpn] WG adoption call for the draft "Usage and applicability of BGP MPLS based Ethernet VPN", draft-rp-l2vpn-evpn-usage-02
Thread-Topic: [l2vpn] WG adoption call for the draft "Usage and applicability of BGP MPLS based Ethernet VPN", draft-rp-l2vpn-evpn-usage-02
Thread-Index: AQHP5/JWQO1Mk0A7R0uvK5lV9Lao9pwv1LoA
Date: Wed, 15 Oct 2014 02:14:35 +0000
Message-ID: <D063257A.553A9%jorge.rabadan@alcatel-lucent.com>
References: <DFEE5C63-7ED6-4DEE-AA2D-2082E711C085@gmail.com> <EE3DB9B68D417942A9B1863918E159FA124555F356@FLDP1LUMXC7V63.us.one.verizon.com> <EE3DB9B68D417942A9B1863918E159FA124555F359@FLDP1LUMXC7V63.us.one.verizon.com> <EE3DB9B68D417942A9B1863918E159FA124555F35B@FLDP1LUMXC7V63.us.one.verizon.com> <543D8F6C.6070001@os3.nl>
In-Reply-To: <543D8F6C.6070001@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: <71682E009A80F640B76C13834DCE5A53@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/n03o_nQNNB4agDt_eYs0EgEBFJ4
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, 15 Oct 2014 02:14:42 -0000

Hi Stefan,

We have just uploaded rev 03 where you can see the terminology changed.
http://tools.ietf.org/html/draft-rp-l2vpn-evpn-usage-03


Please let us know if you support this document now for WG adoption.
Thank you.
Jorge

-----Original Message-----
From: Stefan Plug <Stefan.Plug@os3.nl>
Date: Tuesday, October 14, 2014 at 2:02 PM
To: "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Re: [l2vpn] WG adoption call for the draft "Usage and
applicability of BGP MPLS based Ethernet VPN", draft-rp-l2vpn-evpn-usage-02

>I believe this draft still uses the terms 'packet' and 'frame' quite
>indiscriminately.
>
>Again as an example
>'The MPLS-encapsulated packet' on page 13 point e) which indicates that
>only the packet i.e. L3 is encapsulated (which would remove the L2
>information needed).
>
>In reality the entire frame is encapsulated as is indeed stated on page
>26:
>"PE1 will push the MPLS Label(s) onto the original Ethernet frame and
>send the packet to the MPLS network"
>
>On 09-07-14 16:43, Rabadan, Jorge (Jorge) wrote:
>> Hi Stefan,
>>
>> We will make sure draft-rp-l2vpn-evpn-usage has the right wording (frame
>> vs packet) in the next revision.
>> Thank you for the feedback.
>>
>> Jorge
>
>I would like to see the terminology changed to avoid confusion and
>therefore must object for now.
>
>Regards,
>
>Stefan
>
>
>On 06-10-14 15:20, Bitar, Nabil N wrote:
>> L2VPN WG,
>> 
>> This is the start of a 2-week call for adopting the draft “Usage and
>>applicability of BGP MPLS based Ethernet VPN”,
>>draft-rp-l2vpn-evpn-usage-02, as an L2VPN WG document.  The draft can be
>>found at: http://tools.ietf.org/id/draft-rp-l2vpn-evpn-usage-02.txt.
>> 
>> This draft was well supported in the WG meeting in Toronto, but as
>>always we are taking it to the list to decide on WG adoption. Please,
>>reply to this email indicating your support or objection to adopting
>>this draft as a WG document. Substantive comments in addition to
>>indicating your support or objection are appreciated.
>> 
>> This call will close on Monday, October 20, 2014.
>> 
>> Thanks,
>> Nabil & Giles
>> 
>

v2.23.0 | Report a Bug | By Email