IETF Logo Mail Archive

Re: [l2vpn] WG adoption call for the draft Integrated Routing and Bridging in EVPN, draft-sajassi-l2vpn-evpn-inter-subnet-forwarding-05

"Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com> Mon, 06 October 2014 14:46 UTC

Return-Path: <wim.henderickx@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 C9AC31A6FC1 for <l2vpn@ietfa.amsl.com>; Mon, 6 Oct 2014 07:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.172
X-Spam-Level:
X-Spam-Status: No, score=-1.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, URIBL_RHS_DOB=1.514] 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 tV8p-LnxAHCd for <l2vpn@ietfa.amsl.com>; Mon, 6 Oct 2014 07:46:41 -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 255221A6FBB for <l2vpn@ietf.org>; Mon, 6 Oct 2014 07:46:41 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id B8C3E279298A0; Mon, 6 Oct 2014 14:46:36 +0000 (GMT)
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 s96EkcjC019006 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Oct 2014 16:46:38 +0200
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.219]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Mon, 6 Oct 2014 16:46:38 +0200
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Re: [l2vpn] WG adoption call for the draft Integrated Routing and Bridging in EVPN, draft-sajassi-l2vpn-evpn-inter-subnet-forwarding-05
Thread-Topic: [l2vpn] WG adoption call for the draft Integrated Routing and Bridging in EVPN, draft-sajassi-l2vpn-evpn-inter-subnet-forwarding-05
Thread-Index: AQHP4WXwjS6QSXZDCUOTnJPs4fsLzJwjJc+A
Date: Mon, 06 Oct 2014 14:46:37 +0000
Message-ID: <D058778B.FB32D%wim.henderickx@alcatel-lucent.com>
References: <DFEE5C63-7ED6-4DEE-AA2D-2082E711C085@gmail.com> <EE3DB9B68D417942A9B1863918E159FA124555F356@FLDP1LUMXC7V63.us.one.verizon.com>
In-Reply-To: <EE3DB9B68D417942A9B1863918E159FA124555F356@FLDP1LUMXC7V63.us.one.verizon.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <13DE239813D2A942B83B9334CC2F1B50@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/2Pq2eZ06G5PL-vQ9fUbH9pbxJZ0
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: Mon, 06 Oct 2014 14:46:42 -0000

As co-author I support adopting this draft as WG since it describes a
fundamental part of how EVPN is applied and describes the different
options to achieve IOT.

On 06/10/14 15:15, "Bitar, Nabil N" <nabil.n.bitar@verizon.com> wrote:

>L2VPN WG,
>
>This is the start of a 2-week call for adopting the draft ³Integrated
>Routing and Bridging in EVPN²,
>draft-sajassi-l2vpn-evpn-inter-subnet-forwarding-05,
>as an L2VPN WG document. The draft can be found at:
>http://www.ietf.org/id/draft-sajassi-l2vpn-evpn-inter-subnet-forwarding-05
>.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