Re: [bess] [**EXTERNAL**] RE: CORRECTION WG Last Call, IPR and Implementation Poll for *draft-ietf-bess-evpn-geneve-03*

Anoop Ghanwani <anoop@alumni.duke.edu> Tue, 20 December 2022 04:12 UTC

Return-Path: <ghanwani@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B906C1524BD; Mon, 19 Dec 2022 20:12:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 7AP1htqBQNVg; Mon, 19 Dec 2022 20:12:03 -0800 (PST)
Received: from mail-yw1-f180.google.com (mail-yw1-f180.google.com [209.85.128.180]) (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 93E27C1524BC; Mon, 19 Dec 2022 20:12:03 -0800 (PST)
Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-3c090251d59so154398217b3.4; Mon, 19 Dec 2022 20:12:03 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=10VJ9zuQ2gcgmJsF3d8fyF72J7+u/OKUynrsut61Kbk=; b=clgJWg4ivy6nJEKH+AsKxhzOcePd8ARL7FTG3VH46k4dOlg3mOZJhwkPOrg3tW4n36 NLdLrI5Mdop8KeCuAlO5aor+nUb6MOJL1sWHicDxaORC1UA4gRpgMpg5VqSOCpwkw+W0 ElMy494UwSAjr4NMKgjOlJFnpgqBgYEOHKgo1PUBVa+s4YOdslzfotQWaDFnIWOAJQgl 5WH2ASUV6VgXyxMlXNIcD38hyYUiQri7/5kXLgHQkC5tB1CkzqTdmxt8wW6x4sM0hYu6 3CG9ZI2MFaTHY/fPegeU+vBldP+iQ0idyHT6rW6zFPOsTl7kzvVjKlMPiH14aFSbbR+J m5mA==
X-Gm-Message-State: ANoB5pkd0odwOWS8a1FA/xbTALwJ2VCRHtrJC1cLluO2P08n8eJRdhiJ hwB+OhfWgAThqjStGreF+g7P1OxN90cThaIW/eE=
X-Google-Smtp-Source: AA0mqf5xbW8muYCdQPfshSY3/cM8tLm3cihn13qNtpdwlcob3dJ4AjQF9MAV9WDrUn78hYdMEA9pWYSI3Ml0Qaxnaw0=
X-Received: by 2002:a81:7b08:0:b0:3ca:81e2:cf21 with SMTP id w8-20020a817b08000000b003ca81e2cf21mr3046028ywc.13.1671509522636; Mon, 19 Dec 2022 20:12:02 -0800 (PST)
MIME-Version: 1.0
References: <B2E1AA9C-4BBD-4356-B053-F5E2853A1B4C@ciena.com> <CA+-tSzyS9xhWAnOu8AR10CiHGio+EKp1xEC2agzyDXHTomfBMg@mail.gmail.com> <BYAPR04MB4581BAB0C92FEF8D8ADCE05EC4D79@BYAPR04MB4581.namprd04.prod.outlook.com> <CA+-tSzydhgB=Ntyk6XOSVrjeuyC+VR1CBb8p2sstFY3vUSv7QQ@mail.gmail.com> <CA+-tSzy7EPiL3aLmx9+LNnw0fog6NbgOqR7BnBZ6JAtJ+fObQg@mail.gmail.com> <BYAPR04MB45815818A699C3A41C25DD09C4E79@BYAPR04MB4581.namprd04.prod.outlook.com> <CA+-tSzyjAcDZ-Bz=3vNcGVkT=ccCLu5upuaabk+nkquV5yaf9A@mail.gmail.com> <CA+-tSzwVoj4=iK87CuYjmjTE=xaTysyvEF+-c9BcKu6yG46jMg@mail.gmail.com> <BY3PR08MB70608DD22B747F2109AD6946F7E59@BY3PR08MB7060.namprd08.prod.outlook.com>
In-Reply-To: <BY3PR08MB70608DD22B747F2109AD6946F7E59@BY3PR08MB7060.namprd08.prod.outlook.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
Date: Mon, 19 Dec 2022 20:11:50 -0800
Message-ID: <CA+-tSzwy0E_RYy-reRoEFMyBDUnEddpc=Ogdifhk+cVrT2R6wQ@mail.gmail.com>
To: "Jorge Rabadan (Nokia)" <jorge.rabadan@nokia.com>
Cc: "Boutros, Sami" <sboutros@ciena.com>, "Boutros, Sami" <sboutros=40ciena.com@dmarc.ietf.org>, "UTTARO, JAMES" <ju1738@att.com>, "Matthew Bocci (Nokia)" <matthew.bocci@nokia.com>, "bess@ietf.org" <bess@ietf.org>, "draft-ietf-bess-evpn-geneve@ietf.org" <draft-ietf-bess-evpn-geneve@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000055e54e05f03aa39f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/1zUwfPBZZbjxDFMneKjsbIaFArw>
Subject: Re: [bess] [**EXTERNAL**] RE: CORRECTION WG Last Call, IPR and Implementation Poll for *draft-ietf-bess-evpn-geneve-03*
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2022 04:12:08 -0000

Thanks Jorge.  I get it now.

On Sun, Dec 18, 2022 at 11:28 PM Jorge Rabadan (Nokia) <
jorge.rabadan@nokia.com> wrote:

> Hi Anoop,
>
>
>
> Note that it is not only the ESI-based filtering procedure (for
> multi-homing) that is performed using the information in the Ethernet
> option TLV, but also the E-Tree flags and the BUM indication. So even if
> you are using local-bias, and you are not using E-Tree, we still want the
> BUM indication to avoid transient packet duplication in certain scenarios.
>
>
>
> So IMO what we want is to RECOMMEND the use of the ethernet option TLV in
> all cases.
>
>
>
> Thanks.
>
> Jorge
>
>
>
> *From: *Anoop Ghanwani <anoop@alumni.duke.edu>
> *Date: *Sunday, December 18, 2022 at 3:49 AM
> *To: *Boutros, Sami <sboutros@ciena.com>
> *Cc: *Boutros, Sami <sboutros=40ciena.com@dmarc.ietf.org>, UTTARO, JAMES <
> ju1738@att.com>, Jorge Rabadan (Nokia) <jorge.rabadan@nokia.com>, Matthew
> Bocci (Nokia) <matthew.bocci@nokia.com>, bess@ietf.org <bess@ietf.org>,
> draft-ietf-bess-evpn-geneve@ietf.org <draft-ietf-bess-evpn-geneve@ietf.org
> >
> *Subject: *Re: [bess] [**EXTERNAL**] RE: CORRECTION WG Last Call, IPR and
> Implementation Poll for *draft-ietf-bess-evpn-geneve-03*
>
> Here's a proposed change:
>
>
>
> OLD
>
>
> While "local-bias" MUST be supported along with Geneve encapsulation, the
> use of the Ethernet option-TLV is RECOMMENDED to follow the same procedures
> used by EVPN MPLS.
>
>
>
> NEW
>
>
>
> While "local-bias" MUST be supported along with Geneve encapsulation, the
> use of the Ethernet option-TLV is required if not using local-bias and
> instead following procedures used by EVPN MPLS.
>
>
>
> This allows implementations that implement only local bias to skip
> sending/implementing the TLV.
>
>
>
> Or are you trying to RECOMMEND that implementations also implement the
> EVPN MPLS procedures in addition to local bias?  If so, I would word the
> text as:
>
>
>
> While "local-bias" MUST be supported along with Geneve encapsulation and
> that doesn't require the use of the Ethernet option-TLV, it is RECOMMENDED
> that Geneve implementations also implement the same procedures used by EVPN
> MPLS.
>
>
>
> On Sat, Dec 17, 2022 at 6:33 PM Anoop Ghanwani <anoop@alumni.duke.edu>
> wrote:
>
> Sami,
>
>
>
> Why is it recommended to carry the TLV if local bias is in use?  (I
> understand the need for it if we're not using local bias.)
>
>
>
> Anoop
>
>
>
> On Sat, Dec 17, 2022 at 2:06 PM Boutros, Sami <sboutros@ciena.com> wrote:
>
> I’m not sure what tightening you are recommending, I am out of ideas of
> how to tighten this, may be you can propose something.
>
>
>
> It is quite clear to me and to the authors, and I hope to everyone else,
> how the TLV can be used for SH as a mechanism similar to local bias, as
> well it can be used when ETREE support is needed.
>
>
>
> Thanks,
>
>
> Sami
>
> *From: *Anoop Ghanwani <anoop@alumni.duke.edu>
> *Date: *Saturday, December 17, 2022 at 1:25 PM
> *To: *Boutros, Sami <sboutros@ciena.com>
> *Cc: *Boutros, Sami <sboutros=40ciena.com@dmarc.ietf.org>, UTTARO, JAMES <
> ju1738@att.com>, Rabadan, Jorge (Nokia - US/Mountain View) <
> jorge.rabadan@nokia.com>, Bocci, Matthew (Nokia - GB) <
> matthew.bocci@nokia.com>, bess@ietf.org <bess@ietf.org>,
> draft-ietf-bess-evpn-geneve@ietf.org <draft-ietf-bess-evpn-geneve@ietf.org
> >
> *Subject: *Re: [bess] [**EXTERNAL**] RE: CORRECTION WG Last Call, IPR and
> Implementation Poll for *draft-ietf-bess-evpn-geneve-03*
>
> Sami,
>
> I don't believe there was closure on this issue.
>
> I think the text around the option TLV being RECOMMENDED should be
> tightened so that it's recommended only when needed.  The way the draft is
> currently written, it sounds like it is recommending that the TLV always be
> carried if multihoming is in use.  But this is not necessary or even
> valuable if Local Bias is in use.
>
> On Wed, Jul 13, 2022 at 12:12 AM Anoop Ghanwani <anoop@alumni.duke.edu>
> wrote:
>
> > Hi Sami,
> >
> > Thanks for updating the doc.
> >
> > Regarding this:
> > >>>
> >
> > I find this statement confusing
> >
> >
> >
> >    While "local-bias" MUST be supported along with GENEVE encapsulation,
> >
> >    the use of the Ethernet option-TLV is RECOMMENDED to follow the same
> >
> >    procedures used by EVPN MPLS.
> >
> >
> >
> >
> >
> > I'm not sure how it helps to carry an extra TLV when it is known
> >
> > that its absence or presence results in identical behavior.
> >
> >
> >
> > Sami: The new TLV is not there only for local bias! It is there for bum
> and leaf/root indications too. So, we can’t simply not carry it. As for the
> text above, we are saying setting the ESI label in the TLV will allow us to
> follow the same Split horizon behavior of MPLS-EVPN with no need for local
> bias. It is true local bias must be supported but this mechanism will work
> too if available given that it is optional.
> >
> > >>>
> >
> > I'm not sure I follow what you're saying.  The new TLV is actually not
> > needed for the Local Bias case because we already know how to make that
> > case work without it.  It is, however, needed for the non-Local Bias case
>
>