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

Stefan Plug <Stefan.Plug@os3.nl> Tue, 14 October 2014 21:02 UTC

Return-Path: <Stefan.Plug@os3.nl>
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 B102E1A0009 for <l2vpn@ietfa.amsl.com>; Tue, 14 Oct 2014 14:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.591
X-Spam-Level:
X-Spam-Status: No, score=-0.591 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RP_MATCHES_RCVD=-0.786] autolearn=no
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 K2imwSLEgC6V for <l2vpn@ietfa.amsl.com>; Tue, 14 Oct 2014 14:02:39 -0700 (PDT)
Received: from mail.serv.os3.nl (mail.serv.os3.nl [145.100.96.25]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE4D31A90F8 for <l2vpn@ietf.org>; Tue, 14 Oct 2014 14:02:38 -0700 (PDT)
Received: from smtp.os3.nl (smtp.os3.nl [IPv6:2001:610:158:960::119]) by mail.serv.os3.nl (Postfix) with ESMTP id CE15317BA88 for <l2vpn@ietf.org>; Tue, 14 Oct 2014 23:02:35 +0200 (CEST)
Received: from [192.168.1.21] (h173109.upc-h.chello.nl [62.194.173.109]) by smtp.os3.nl (Postfix) with ESMTPSA id A641F17BA87 for <l2vpn@ietf.org>; Tue, 14 Oct 2014 23:02:35 +0200 (CEST)
Message-ID: <543D8F6C.6070001@os3.nl>
Date: Tue, 14 Oct 2014 23:02:36 +0200
From: Stefan Plug <Stefan.Plug@os3.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: 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
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>
In-Reply-To: <EE3DB9B68D417942A9B1863918E159FA124555F35B@FLDP1LUMXC7V63.us.one.verizon.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/ds3tD-yE1h8IqRg1C0Kh3fjEvu8
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: Tue, 14 Oct 2014 21:02:40 -0000

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
>