Re: [l2vpn] WG adoption call for the draft Integrated Routing and Bridging in EVPN, draft-sajassi-l2vpn-evpn-inter-subnet-forwarding-05
Thomas Morin <thomas.morin@orange.com> Fri, 17 October 2014 16:14 UTC
Return-Path: <tmmorin.orange@gmail.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 B84CF1A1BC4 for <l2vpn@ietfa.amsl.com>; Fri, 17 Oct 2014 09:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 b0r-oflWfwG3 for <l2vpn@ietfa.amsl.com>; Fri, 17 Oct 2014 09:14:30 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E74A71A1BB3 for <l2vpn@ietf.org>; Fri, 17 Oct 2014 09:14:10 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id d1so2510717wiv.8 for <l2vpn@ietf.org>; Fri, 17 Oct 2014 09:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=p5c7ZWOQU85IJDFLSWnDqniKND+ofeK/WBxZgDEkI7o=; b=G/ob0Czo/O7sRRovNSG8ii/1sV4U5ke2ldOOWx5TnCVbIshe5BdaSh7x7SUkAwC+3c Vm1ISVrFb8R2B84TiOSeq4/eW+ZEXb3um0YdZltVFn90mQIGW+RYjjRZibV9KeUXzvoZ nA2uh7uQHGQriXy6QGffM4W9NmAI3U1VbDS2Y9NC10Q42sJYb3FYsPfYZBXtX4WtIjDE /qrTHxrhk0/bEQUo/EOF2ZtBBpBVDtmkPYXV+Zychc5bX01e6RHsvK5Bu89n5YDcuWdH kG18uMFEObNO5LDP2CAfW6ze8OnPKXGrPIS0udJ4WMrQMUVvyF9W4z2upHLyuY2lvwEy /7Pg==
X-Received: by 10.194.90.15 with SMTP id bs15mr11255414wjb.47.1413562449555; Fri, 17 Oct 2014 09:14:09 -0700 (PDT)
Received: from [127.0.0.1] (ARennes-652-1-63-137.w2-11.abo.wanadoo.fr. [2.11.62.137]) by mx.google.com with ESMTPSA id vm6sm2194119wjc.16.2014.10.17.09.14.08 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Oct 2014 09:14:08 -0700 (PDT)
Sender: Thomas Morin <tmmorin.orange@gmail.com>
Message-ID: <5441404E.8000906@orange.com>
Date: Fri, 17 Oct 2014 18:14:06 +0200
From: Thomas Morin <thomas.morin@orange.com>
Organization: Orange
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "l2vpn@ietf.org" <l2vpn@ietf.org>, draft-sajassi-l2vpn-evpn-inter-subnet-forwarding@tools.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
References: <DFEE5C63-7ED6-4DEE-AA2D-2082E711C085@gmail.com> <EE3DB9B68D417942A9B1863918E159FA124555F356@FLDP1LUMXC7V63.us.one.verizon.com>
In-Reply-To: <EE3DB9B68D417942A9B1863918E159FA124555F356@FLDP1LUMXC7V63.us.one.verizon.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/N6OyBqXdPBHw83wX94uvfCugOsE
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: Fri, 17 Oct 2014 16:14:34 -0000
Hi working group, (My apologies for not having found time to review this and send feedback earlier.) Although the topic of inter-subnet forwarding is indeed important, I have a few concerns about the document as it currently is, and I do not support adoption in its current form. My main concerns are the following: - the document describes multiple solutions, but the benefit/necessity of introducing each is to me not clearly spelled out, in particular the benefits compared to an approach that would just locally combine an EVI and a VRF ; I'm not saying there is no benefit, but they just aren't spelled out explicitly, nor the limitations of what we could do without these specs - how these solutions can be combined or not is not explained, and an immediate worry is the question of interop of solution implementing one approach with solutions implementing another - a important point would be to make it explicit that in all solutions, interop with routers not implementing these specs and implementing plain RFC4364 should be a MUST (by having NVE implementation also import and use IPVPN routes if any is advertised, and advertise IP VPN routes for the networks for which IP VPN interconnection is wanted) - last but not least: section 5.2 depends on draft-rabadan-l2vpn-evpn-prefix-advertisement that is not yet a working group document: wouldn't we putting the cart before the horse by adopting draft-sajassi-l2vpn-evpn-inter-subnet-forwarding now ? Other questions: - section 4.3 seems to me as possibly incorrect: the proposed procedure consist in having the ingress NVE rewrite the destination MAC address of the payload before, but I can't understand how this makes sense: why is this needed since the packet is forwarded based on an IP VPN route (and can thus only be an IP packet) ? and why would the payload destination MAC be useful to the local WAN gateway anyway (it will do an IP lookup, and no MAC lookup) ? - section 4.4 raises the same question - section 5.1 is a lot about the use of overlays and describes how to use a VXLAN encapsulation, while section 4 does not (and even assumes in many places that LSPs are used for transit between PEs) ; this is editorial, but it looks like a fair amount of work is needed to make the document overall consistent Best, -Thomas 2014-10-06, Bitar, Nabil N: > 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 >
- WG adoption call for EVPN Overlay draft Giles Heron
- Re: WG adoption call for EVPN Overlay draft Henderickx, Wim (Wim)
- RE: WG adoption call for EVPN Overlay draft John E Drake
- RE: WG adoption call for EVPN Overlay draft Brites, Jorge
- Re: WG adoption call for EVPN Overlay draft Jeff Tantsura
- RE: WG adoption call for EVPN Overlay draft Lucy yong
- Re: WG adoption call for EVPN Overlay draft Ali Sajassi (sajassi)
- RE: WG adoption call for EVPN Overlay draft Linda Dunbar
- RE: WG adoption call for EVPN Overlay draft UTTARO, JAMES
- Re: WG adoption call for EVPN Overlay draft Samer Salam (ssalam)
- Re: WG adoption call for EVPN Overlay draft Andrew G. Malis
- WG adoption call for EVPN Overlay draft Shahram Davari
- RE: WG adoption call for EVPN Overlay draft Gregory Mirsky
- Re: WG adoption call for EVPN Overlay draft Patrice Brissette (pbrisset)
- Re: WG adoption call for EVPN Overlay draft Tapraj Singh
- Re: WG adoption call for EVPN Overlay draft Rabadan, Jorge (Jorge)
- Re: WG adoption call for EVPN Overlay draft Sam Aldrin
- Re: WG adoption call for EVPN Overlay draft Thomas Morin
- [l2vpn] WG adoption call for the draft Integrated… Bitar, Nabil N
- [l2vpn] WG adoption call for the draft VPWS suppo… Bitar, Nabil N
- [l2vpn] WG adoption call for the draft VXLAN DCI … Bitar, Nabil N
- [l2vpn] WG adoption call for the draft "Usage and… Bitar, Nabil N
- 答复: WG adoption call for EVPN Overlay draft Haoweiguo
- Re: [l2vpn] WG adoption call for the draft "Usage… Rabadan, Jorge (Jorge)
- Re: [l2vpn] WG adoption call for the draft Integr… Henderickx, Wim (Wim)
- Re: [l2vpn] WG adoption call for the draft VPWS s… Henderickx, Wim (Wim)
- Re: [l2vpn] WG adoption call for the draft "Usage… Henderickx, Wim (Wim)
- Re: [l2vpn] WG adoption call for the draft VPWS s… Rabadan, Jorge (Jorge)
- Re: [l2vpn] WG adoption call for the draft Integr… Rabadan, Jorge (Jorge)
- RE: [l2vpn] WG adoption call for the draft VPWS s… UTTARO, JAMES
- RE: [l2vpn] WG adoption call for the draft Integr… UTTARO, JAMES
- RE: [l2vpn] WG adoption call for the draft "Usage… UTTARO, JAMES
- RE: [l2vpn] WG adoption call for the draft "Usage… Lucy yong
- RE: [l2vpn] WG adoption call for the draft VPWS s… Lucy yong
- RE: [l2vpn] WG adoption call for the draft Integr… Lucy yong
- Re: [l2vpn] WG adoption call for the draft VXLAN … Tapraj Singh
- RE: WG adoption call for EVPN Overlay draft Dhananjaya Rao (dhrao)
- Re: WG adoption call for EVPN Overlay draft Nabeel Cocker
- Re: [l2vpn] WG adoption call for the draft VPWS s… Ali Sajassi (sajassi)
- Re: [l2vpn] WG adoption call for the draft "Usage… Nabeel Cocker
- Re: [l2vpn] WG adoption call for the draft Integr… Ali Sajassi (sajassi)
- Re: [l2vpn] WG adoption call for the draft "Usage… Ali Sajassi (sajassi)
- Re: [l2vpn] WG adoption call for the draft VXLAN … Ali Sajassi (sajassi)
- Re: [l2vpn] WG adoption call for the draft "Usage… Keyur Patel (keyupate)
- Re: WG adoption call for EVPN Overlay draft Keyur Patel (keyupate)
- RE: [l2vpn] WG adoption call for the draft VXLAN … John E Drake
- RE: [l2vpn] WG adoption call for the draft VPWS s… John E Drake
- RE: [l2vpn] WG adoption call for the draft "Usage… John E Drake
- Re: [l2vpn] WG adoption call for the draft "Usage… Senad Palislamovic
- Re: [l2vpn] WG adoption call for the draft "Usage… Stefan Plug
- Re: [l2vpn] WG adoption call for the draft "Usage… Rabadan, Jorge (Jorge)
- Re: [l2vpn] WG adoption call for the draft "Usage… Stefan Plug
- Re: [l2vpn] WG adoption call for the draft Integr… Thomas Morin
- Re: [l2vpn] WG adoption call for the draft Integr… Ali Sajassi (sajassi)
- RE: [l2vpn] WG adoption call for the draft Integr… Dennis Cai (dcai)
- RE: [l2vpn] WG adoption call for the draft Integr… Linda Dunbar
- Re: [l2vpn] WG adoption call for the draft Integr… Samer Salam (ssalam)
- RE: [l2vpn] WG adoption call for the draft Integr… John E Drake
- Re: [l2vpn] WG adoption call for the draft Integr… Samir Thoria (sthoria)
- Re: WG adoption call for EVPN Overlay draft Giles Heron
- Re: WG adoption call for EVPN Overlay draft Ali Sajassi (sajassi)
- Re: WG adoption call for EVPN Overlay draft Giles Heron
- Re: WG adoption call for EVPN Overlay draft Thomas Morin
- RE: [l2vpn] WG adoption call for the draft "Usage… Bitar, Nabil N
- RE: [l2vpn] WG adoption call for the draft Integr… Bitar, Nabil N
- RE: [l2vpn] WG adoption call for the draft VXLAN … Bitar, Nabil N
- RE: [l2vpn] WG adoption call for the draft VPWS s… Bitar, Nabil N
- Re: [l2vpn] WG adoption call for the draft VPWS s… Thomas Morin
- RE: [l2vpn] WG adoption call for the draft VPWS s… John E Drake
- Re: [l2vpn] WG adoption call for the draft VPWS s… Dirk Steinberg
- Re: [l2vpn] WG adoption call for the draft VPWS s… Patrice Brissette (pbrisset)
- Re: [l2vpn] WG adoption call for the draft VPWS s… Ali Sajassi (sajassi)
- RE: [l2vpn] WG adoption call for the draft VPWS s… Dennis Cai (dcai)