Re: [Pals] [EXTERNAL] [Technical Errata Reported] RFC7432 (7758)
"Andrew G. Malis" <agmalis@gmail.com> Thu, 11 January 2024 13:05 UTC
Return-Path: <agmalis@gmail.com>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F21CC14F600; Thu, 11 Jan 2024 05:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cvt7yQL1DTB5; Thu, 11 Jan 2024 05:05:44 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68815C14F5E6; Thu, 11 Jan 2024 05:04:19 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-6da4a923b1bso2808996b3a.2; Thu, 11 Jan 2024 05:04:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704978258; x=1705583058; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=q2d2pW40tjXnjjsl8kAyPnNNY5Ct75fRzrOYYVF9CQE=; b=au5Lq0szzqk2fmL1AnMjsV1UyDSA5gzCOAGlaLcHsT/5IDU7ySbe7DkOEAwbvU283/ MLOjo/kFTZK4WgKSD002lMtqXK63PrrvEQLnSoAnSCuabqK8nbDZVyoRmUrsqHhHcIv9 f2hEajWRS6UfLz1Em4ql9mBD5JpL4rK/E45WH1MnS+LjrtS6r+ZXtZOGMustpHL2VfX6 lXdWEM8/kQQKdX05C8sXlijw4EdwhcnyD94nyqM4c7snFM0xD/egrLc06zXq/IqNIrV9 EwmQMo5RVDumIWM21ITeCext+d4fcnbexsZj6/okg/L1m9OH4UQBYq7iPk1YfhA7frpu 3ESQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704978258; x=1705583058; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=q2d2pW40tjXnjjsl8kAyPnNNY5Ct75fRzrOYYVF9CQE=; b=f7Ni4z0PuiKSGIGqgyM5oOd30sMfNJzHCGiA3G7gY1xR6jJX85jmgWtjobtzUV/2Bg 1WYwtjZhzG9Rk+1VnOmVCh952LHkjLG8pvLL9UWhKgdKMp6hCOEK/NZ7FbFDD1pqy8NK DmIDSPKHiixnO/igDRpQzKsC5jA7a1Nym+ks2MOI+XSNzX+hoG8nrqXUQuK2Ub/LGa8a a0KxKZ5Z+DfO9mJ1+92En7i/to+g1pra4RK+KbJTMQqBi6DAQsOpdfQlR0yAtCNariNH DU8YhsuYaTkLLbmNzMEq1gK5XdO2k/PwW4OYwBZwNBkQaV7dJBZ1rOjbGFuGoDIRagZk HGpg==
X-Gm-Message-State: AOJu0YwoqSPgtEEUTgdze44Y1hOv32Nlm+DCVeGAQIcsJsxLWkpjLc0s NAQfrf8+PBxfksNE8wFtCx4w6hSq+WqcPE7Xqrc=
X-Google-Smtp-Source: AGHT+IGvVBEpGyA03ACaNyJDZ0bFeZZcqejU2ElQTBtOYP7YQlLJYDZ/VH0iHIXEInBE/zQ52Ig+qQBbaHKuX64sEXQ=
X-Received: by 2002:a05:6a20:da8a:b0:199:dd65:5d2e with SMTP id iy10-20020a056a20da8a00b00199dd655d2emr848413pzb.25.1704978258243; Thu, 11 Jan 2024 05:04:18 -0800 (PST)
MIME-Version: 1.0
References: <20240111080246.EE2F51182206@rfcpa.amsl.com> <PH0PR03MB630004B6932D957C84F7690AF6682@PH0PR03MB6300.namprd03.prod.outlook.com> <CAFpVB7XvHnQG1xHvvoad+7t=+Hp78Jgxf2XaZ0WfrKxeWAeOhA@mail.gmail.com> <PH0PR03MB6300733F18B720A17A6B93B9F6682@PH0PR03MB6300.namprd03.prod.outlook.com>
In-Reply-To: <PH0PR03MB6300733F18B720A17A6B93B9F6682@PH0PR03MB6300.namprd03.prod.outlook.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 11 Jan 2024 08:04:01 -0500
Message-ID: <CAA=duU0=Z0epL3FOzivjs_y7yjLE5zVqDShy_VNa1Z==LSCOKg@mail.gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>
Cc: Pavel Mykhailyk <pavel.mykhailyk@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "bess@ietf.org" <bess@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006eb3d5060eab2fda"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/RVh-T71OHediACZwkFYM9AoN5Ds>
Subject: Re: [Pals] [EXTERNAL] [Technical Errata Reported] RFC7432 (7758)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2024 13:05:49 -0000
Sasha, Andrew will take care of it. Cheers, Andy On Thu, Jan 11, 2024 at 5:37 AM Alexander Vainshtein < Alexander.Vainshtein@rbbn.com> wrote: > Pavel, > > Lots of thanks for your email. > > Looks as we are aligned😊. I am not sure if the reporter of an Erratum > can revoke it (never tried this). > > > > > > Regards, > > Sasha > > > > *From:* Pavel Mykhailyk <pavel.mykhailyk@gmail.com> > *Sent:* Thursday, January 11, 2024 12:33 PM > *To:* Alexander Vainshtein <Alexander.Vainshtein@rbbn.com> > *Cc:* RFC Errata System <rfc-editor@rfc-editor.org>; rtg-ads@ietf.org; > bess@ietf.org; pals@ietf.org > *Subject:* Re: [EXTERNAL] [Pals] [Technical Errata Reported] RFC7432 > (7758) > > > > Hi > > Sorry, looks like i just misunderstood some terms, so ES route means EVPN > Type 4 (not 1) - you are absolutely right, it is used for DF and limited > to PEs that are connected to MH Po. > > > > Thanks for clarification > > With Regards > > > > чт, 11 янв. 2024 г. в 11:56, Alexander Vainshtein < > Alexander.Vainshtein@rbbn.com>: > > Hi all, > > > > IMHO and FWIW the corrected text proposed in this Erratum is *technically > incorrect*, and. Therefore, the Erratum must be *rejected*. > > > > Ethernet Segment (EVPN Type 4) routes are used solely for discovery of all > PEs that participate in the process of election of the Designated Forwarder > (DF)for the specific MH ES, and their parameters that affect the election > process (e.g., DF Election algorithm and its parameters). This includes > all the PEs that are attached to the MH ES in question, and none other. > > > > The PEs that are not attached to the MH ES in question do not participate > in the DF election and, *by design*, *are not aware of the DF election > results*. > > In the case of All-Active multi-homing, there is no need for such PEs to > be aware of these results. > > The case of Single-Active multi-homing is addressed by the following > statement from Section 8.4 of RFC 7432 (the relevant text is highlighted): > > > > The backup path is a closely related function, but it is used in > > Single-Active redundancy mode. In this case, a PE also advertises > > that it has reachability to a given EVI/ES using the same combination > > of Ethernet A-D per EVI route and Ethernet A-D per ES route as > > discussed above, but with the "Single-Active" bit in the flags of the > > ESI Label extended community set to 1. A remote PE that receives a > > MAC/IP Advertisement route with a non-reserved ESI SHOULD consider > > the advertised MAC address to be reachable via any PE that has > > advertised this combination of Ethernet A-D routes, and it SHOULD > > install a backup path for that MAC address. > > > > AFAIK, EVPN implementation that follow the design defined in 7432 have > been widely deployed for years. > > > > My 2c, > > Sasha > > > > *From:* Pals <pals-bounces@ietf.org> *On Behalf Of *RFC Errata System > *Sent:* Thursday, January 11, 2024 10:03 AM > *To:* sajassi@cisco.com; raggarwa_1@yahoo.com; nabil.n.bitar@verizon.com; > aisaac71@bloomberg.net; uttaro@att.com; jdrake@juniper.net; > wim.henderickx@alcatel-lucent.com; aretana.ietf@gmail.com; jgs@juniper.net; > andrew-ietf@liquid.tech; giheron@cisco.com; nabil.n.bitar@verizon.com > *Cc:* pavel.mykhailyk@gmail.com; pals@ietf.org; rfc-editor@rfc-editor.org > *Subject:* [EXTERNAL] [Pals] [Technical Errata Reported] RFC7432 (7758) > > > > The following errata report has been submitted for RFC7432, > "BGP MPLS-Based Ethernet VPN". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7758 > > -------------------------------------- > Type: Technical > Reported by: Pavel Mykhailyk <pavel.mykhailyk@gmail.com> > > Section: 8.1.1 > > Original Text > ------------- > The Ethernet Segment route filtering MUST be done such that the > Ethernet Segment route is imported only by the PEs that are > multihomed to the same Ethernet segment > > Corrected Text > -------------- > The Ethernet Segment route filtering MUST be done such that the > Ethernet Segment route is imported only by the PEs that are > connected to same EVI > > Notes > ----- > In all text in context of evpn-multihoming term ES used for logical set of > links - distributed PortChannel when CE use several links to different PEs > as single aggregate link. But in section 8.1.1 term ES can't be used in > same way, becouse ES routes must be distributed for all PE that hold same > VLAN. For example PE1 and PE2 connected to CE1 with EVPN-MH PortChannel > (ESI-1) and use VLAN 10, CE2 connected to PE3 and use VLAN 10 but not use > any aggregation - not included to any ES. PE3 build mac table for CE1 mac > and must use ESI-1 as next-hop, so it must apply ES route and not filter > it, regardles of local connection to ES in terms of EVPN-MH PortChannel. So > each PE connected to EVI import this route > > Instructions: > ------------- > This erratum is currently posted as "Reported". (If it is spam, it > will be removed shortly by the RFC Production Center.) Please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > will log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC7432 (draft-ietf-l2vpn-evpn-11) > -------------------------------------- > Title : BGP MPLS-Based Ethernet VPN > Publication Date : February 2015 > Author(s) : A. Sajassi, Ed., R. Aggarwal, N. Bitar, A. Isaac, J. Uttaro, > J. Drake, W. Henderickx > Category : PROPOSED STANDARD > Source : Layer 2 Virtual Private Networks > Area : Routing > Stream : IETF > Verifying Party : IESG > > _______________________________________________ > Pals mailing list > Pals@ietf.org > https://www.ietf.org/mailman/listinfo/pals > > > > *Disclaimer* > > This e-mail together with any attachments may contain information of > Ribbon Communications Inc. and its Affiliates that is confidential and/or > proprietary for the sole use of the intended recipient. Any review, > disclosure, reliance or distribution by others or forwarding without > express permission is strictly prohibited. If you are not the intended > recipient, please notify the sender immediately and then delete all copies, > including any attachments. > > _______________________________________________ > Pals mailing list > Pals@ietf.org > https://www.ietf.org/mailman/listinfo/pals >
- [Pals] [Technical Errata Reported] RFC7432 (7758) RFC Errata System
- Re: [Pals] [EXTERNAL] [Technical Errata Reported]… Alexander Vainshtein
- Re: [Pals] [EXTERNAL] [Technical Errata Reported]… Alexander Vainshtein
- Re: [Pals] [EXTERNAL] [Technical Errata Reported]… Andrew G. Malis
- Re: [Pals] [EXTERNAL] [Technical Errata Reported]… Alexander Vainshtein
- Re: [Pals] [EXTERNAL] [Technical Errata Reported]… Rebecca VanRheenen