RE: optional ethernet A-D per EVI route
Jakob Heitz <jakob.heitz@ericsson.com> Mon, 12 May 2014 05:34 UTC
Return-Path: <jakob.heitz@ericsson.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 BCBC71A03FD
for <l2vpn@ietfa.amsl.com>; Sun, 11 May 2014 22:34:18 -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, HTML_MESSAGE=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 tDfy_fNIzPJ7 for <l2vpn@ietfa.amsl.com>;
Sun, 11 May 2014 22:34:09 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65])
by ietfa.amsl.com (Postfix) with ESMTP id 579681A03F6
for <l2vpn@ietf.org>; Sun, 11 May 2014 22:34:09 -0700 (PDT)
X-AuditID: c6180641-f799b6d000000b0f-fb-53700b9ba0e8
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87])
by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id
85.F3.02831.B9B00735; Mon, 12 May 2014 01:45:31 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by
EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0174.001; Mon,
12 May 2014 01:34:02 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>, "l2vpn@ietf.org"
<l2vpn@ietf.org>
Subject: RE: optional ethernet A-D per EVI route
Thread-Topic: optional ethernet A-D per EVI route
Thread-Index: Ac9tmo9QXH1GYTvGSny5wGqVCAmMz///7AeA///ad0A=
Date: Mon, 12 May 2014 05:34:01 +0000
Message-ID: <2F3EBB88EC3A454AAB08915FBF0B8C7E03053B47@eusaamb109.ericsson.se>
References: <2F3EBB88EC3A454AAB08915FBF0B8C7E03053A4C@eusaamb109.ericsson.se>
<CF95A55C.D37EF%sajassi@cisco.com>
In-Reply-To: <CF95A55C.D37EF%sajassi@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.12]
Content-Type: multipart/alternative;
boundary="_000_2F3EBB88EC3A454AAB08915FBF0B8C7E03053B47eusaamb109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyuXRPuO5s7oJgg4vr5SwefzvEbvHubDOL
A5PHlN8bWT2WLPnJFMAUxWWTkpqTWZZapG+XwJVx/PBeloLJLYwVW47uZ2tgXFnWxcjJISFg
IrHq4wtmCFtM4sK99WxdjFwcQgJHGSU+7f3IDOEsZ5R4OHs7O0gVm4COxLfrXWAdIgIhEqf7
WhhBbGYBM4nOm5PBaoQFDCRePp/CBlFjKLHj1DMmCNtKYn3XJLA4i4CqxMZjX8DqeQV8JaYs
XQpWIyRQJNF07DRYDaeAvsSf2R9ZQGxGoOu+n1rDBLFLXOLWk/lMEFcLSCzZcx7qA1GJl4//
sULYShJzXl9jhqjPl/iz4AUrxC5BiZMzn7BMYBSdhWTULCRls5CUQcR1JBbs/sQGYWtLLFv4
mhnGPnPgMROy+AJG9lWMHKXFqWW56UaGmxiBkXVMgs1xB+OCT5aHGAU4GJV4eBfsyg8WYk0s
K67MPcQozcGiJM6b/ik2WEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAPjhrrLHgXJl5gzdObU
37t1g+XDlbk+/k09h1kmLTzo+XVVembYcTu9wyfrt2vz5XtsaK9iuuT0sYR12hpPPzePiV4G
Cq7f5/ZU/qpW7f57bk/l3kC/mte/7utrpGzcYvCrerpImN3M5svuV5J7j8/c75YfX/GJO9/y
o/gdvV1LI1/MPW2+RHGREktxRqKhFnNRcSIAFBI+cI0CAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/OIgXzhcOD510SVGetL2wfGOia3k
Cc: Antoni Przygienda <antoni.przygienda@ericsson.com>
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, 12 May 2014 05:34:18 -0000
Thanks Ali. We didn't quite tie together the optionality of aliasing with the optionality of the route. You have clarified it. Cheers, Jakob. From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com] Sent: Sunday, May 11, 2014 10:17 PM To: Jakob Heitz; l2vpn@ietf.org Cc: Antoni Przygienda Subject: Re: optional ethernet A-D per EVI route Hi Jakob, We are talking about two different routes. Section 8.4.1 talks about Ethernet A-D per EVI; whereas, section 9.2.2 talks about Ethernet A-D per ES. The former one is optional but no the latter one. As the matter of fact section 8.2.1 states that the support of the latter one is mandatory (1st para). For rev 7, I added a clarification sentence to the end of the 3rd para of section 9.2.2 saying: "The dependency of MAC routes installation on Ethernet A-D per ES routes, is to ensure that MAC routes don't get accidentally installed during mass withdraw period." Cheers, Ali From: Jakob Heitz <jakob.heitz@ericsson.com<mailto:jakob.heitz@ericsson.com>> Date: Sunday, May 11, 2014 9:43 PM To: "l2vpn@ietf.org<mailto:l2vpn@ietf.org>" <l2vpn@ietf.org<mailto:l2vpn@ietf.org>> Cc: Antoni Przygienda <antoni.przygienda@ericsson.com<mailto:antoni.przygienda@ericsson.com>> Subject: optional ethernet A-D per EVI route Tony and I have an issue. The draft says 8.4.1<http://tools.ietf.org/html/draft-ietf-l2vpn-evpn-07#section-8.4.1> Constructing the Ethernet A-D per EVPN Instance (EVI) Route This section describes the procedures used to construct the Ethernet A-D per EVPN Instance (EVI) route, which is used for aliasing (as discussed above). Support of this route is OPTIONAL. And 9.2.2<http://tools.ietf.org/html/draft-ietf-l2vpn-evpn-07#section-9.2.2> Route Resolution ... If the Ethernet Segment Identifier field in a received MAC Advertisement route is set to a non-reserved ESI, then if the receiving PE decides to install forwarding state for the associated MAC address, it MUST be when both the MAC Advertisement route AND the associated set of Ethernet A-D per ES routes have been received. Should this sentence be changed to "Support of this route is OPTIONAL unless non-reserved ESIs are used" or just be changed to MANDATORY? Thanks, Jakob.
- optional ethernet A-D per EVI route Jakob Heitz
- Re: optional ethernet A-D per EVI route Ali Sajassi (sajassi)
- RE: optional ethernet A-D per EVI route Jakob Heitz
- RE: optional ethernet A-D per EVI route Antoni Przygienda
- Re: optional ethernet A-D per EVI route Jakob Heitz
- RE: optional ethernet A-D per EVI route John E Drake
- RE: optional ethernet A-D per EVI route Antoni Przygienda
- Re: optional ethernet A-D per EVI route John E Drake
- RE: optional ethernet A-D per EVI route Antoni Przygienda