Re: [l2vpn] WG adoption call for the draft Integrated Routing and Bridging in EVPN, draft-sajassi-l2vpn-evpn-inter-subnet-forwarding-05
"Ali Sajassi (sajassi)" <sajassi@cisco.com> Mon, 20 October 2014 16:45 UTC
Return-Path: <sajassi@cisco.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 BDD001A8762 for <l2vpn@ietfa.amsl.com>; Mon, 20 Oct 2014 09:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.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 FQrCOSIaNxQs for <l2vpn@ietfa.amsl.com>; Mon, 20 Oct 2014 09:45:57 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552591A88AD for <l2vpn@ietf.org>; Mon, 20 Oct 2014 09:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4154; q=dns/txt; s=iport; t=1413822743; x=1415032343; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=jo+1XusHVomLVYqEXmJA2bZLOYW1/32KybcJloSVIAI=; b=ac2DazgObUMIP2JJKfgH04+dnplmShF3VSvI1XIICsnxZY3AmYI+yinI Wy4lGTsiR1fqW6vPIMfOj5Rz8j0I4YzT0+54bi4qIK9AzeRPzxwHr3Zgx SJSlW1omqN0YCHQGax1PG0jEYCSTg8sU/i574PZVf8wNe1AZ1x8n94Eny Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAJI4RVStJV2b/2dsb2JhbABcgmsjU1gEzCyHSwKBERYBfYQDAgQdbgEIOz0lAgQBEgkSiCQBDMV8AQEBByKPbxEBV4RLBYskhl2LWYEwg0aNK4QBggYYFoFDbIEPOYEDAQEB
X-IronPort-AV: E=Sophos;i="5.04,757,1406592000"; d="scan'208";a="88679615"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP; 20 Oct 2014 16:32:22 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9KGWLoX020108 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Oct 2014 16:32:22 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0195.001; Mon, 20 Oct 2014 11:32:21 -0500
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Thomas Morin <thomas.morin@orange.com>, "l2vpn@ietf.org" <l2vpn@ietf.org>, "draft-sajassi-l2vpn-evpn-inter-subnet-forwarding@tools.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
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: AQHP4WXwjS6QSXZDCUOTnJPs4fsLzJw028UAgARGvAA=
Date: Mon, 20 Oct 2014 16:32:21 +0000
Message-ID: <D06A7BA4.F908B%sajassi@cisco.com>
In-Reply-To: <5441404E.8000906@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.128.2.91]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3CC5CC60EE581249B0B4F7C7B46B3A95@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/FLdfGoBqFtIWaOHZXNIjAbEDESM
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, 20 Oct 2014 16:45:58 -0000
Thomas, Thanks for the review, please refer to my reply inline On 10/17/14, 9:14 AM, "Thomas Morin" <thomas.morin@orange.com> wrote: >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 The document describes two broad approaches for IRB: Asymmetric and Symmetric. Symmetric approach is the one that expects each node to have both EVI and VRF. Are you asking for a description of pros/cons of these two approaches? >- 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 The two approaches are interoperable. I¹ll add a section to describe the inter-operability between the two. >- 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) There is another draft for this: draft-sajassi-l2vpn-evpn-ipvpn-interop >- 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 ? The dependency is minimal and the section 5.2 is just an extension of section 5.1 where now there are some prefixes sitting behind TS¹s > >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) ? You¹re right. It is more of adding a new MAC header than re-writing the existing one. I¹ll correct it. >- section 4.4 raises the same question OK. I¹ll fix it. >- 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 I¹ll try to make them consistent. Thanks again for your review, Ali > >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-0 >>5.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)