IETF Logo Mail Archive

Re: [bess] Section 8.5 of draft-ietf-bess-rfc7432bis

Gyan Mishra <hayabusagsm@gmail.com> Fri, 03 March 2023 22:50 UTC

Return-Path: <hayabusagsm@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 993F9C151AFB for <bess@ietfa.amsl.com>; Fri, 3 Mar 2023 14:50:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.092
X-Spam-Level:
X-Spam-Status: No, score=-2.092 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_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 DGvkfM-4Ag4L for <bess@ietfa.amsl.com>; Fri, 3 Mar 2023 14:50:10 -0800 (PST)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 12440C14CEE4 for <bess@ietf.org>; Fri, 3 Mar 2023 14:50:10 -0800 (PST)
Received: by mail-qv1-xf2b.google.com with SMTP id nf5so2809852qvb.5 for <bess@ietf.org>; Fri, 03 Mar 2023 14:50:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=jjsgg8oCCwb3HBp41tqGVXprJDdTiMLy2RkZriB+rLo=; b=j+Rg1BBeKO5a2Qta6+UUJQOu0moZbW3xV71ZEH+QuoXkXwQ3+lykNpu0AKT8LrZT5y ZvvdJr/89Qj1XrSzVmMnMiqYplICUV46CSnlRMpLE2HzbB94hz9sDVRmPbm0o6hNRBWo 1HQuCQCtHcP8Dr42E06EJRlh5ObBEJmh1Fc1jZPU0nh4mNGu50Of/Kefl9GjnvQ01Flm DdxxBYqMwfI2nlyXF0TjeDsVRpUyq+s4EFvucyWw4YHWL+nuc4G72vkMyxTK0Jdq4zpj Ov/ZCKIhyGFFvrpVIAQe9izmgTp67tbeepKR5414HlJms9DQ1jorEeo/20BSJNfcXIOF Lrlg==
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=jjsgg8oCCwb3HBp41tqGVXprJDdTiMLy2RkZriB+rLo=; b=fOb1H2eIul1iflDoLB9/IXw4kaCy8nvMbh6Jk2+sAOK/e+kj5gc/xgLvAlvAAR/knO 1jamqUV5KROtaA84U2YV86qpHSJis128YfGbs2fVOawSG9Z13OwotMwAhSHWAIJmAXfe s7mr47fR+xjMK8BVAWo8GdfKF5WV1WmhTZl1/yYatEoHHsABfQL3SKgFj18dDD9jLZZu 5OeTFKDU4DAEePXcKQmrriFAyLoM7vOgY1JtJuba/HM+Wi2ZK60Chme6mOoKrlE2fo7y GUPKZ47+dpIUGsbTd7mLYLdOXcXY1ompb//gyxZu185SeQrxs5nMovQnLmwlP6rqUWDQ WJGQ==
X-Gm-Message-State: AO0yUKU+l32sMXXXZMUlioi01+cUUH3jN/qZ+JDNVLQyrmwh+DaGQ5Qi /WvfGNb0DDfVULa3+tc+tuphNFmxu5c2BukVIh8=
X-Google-Smtp-Source: AK7set+qj2vxDl1b3CSwgkizMsRtW0Ic1aW5FgnYf6JB+MwdQNNHC5pkoL2C7xHenyrqJXkQYfQN3Pymw2acUJmX1xg=
X-Received: by 2002:a05:6214:913:b0:56e:ff38:46a2 with SMTP id dj19-20020a056214091300b0056eff3846a2mr892261qvb.10.1677883808746; Fri, 03 Mar 2023 14:50:08 -0800 (PST)
MIME-Version: 1.0
References: <AM9PR08MB6004F38A0D02DBBAAA137A73D5DE9@AM9PR08MB6004.eurprd08.prod.outlook.com> <BY3PR08MB706038003E2AF751B97FAB8CF7DE9@BY3PR08MB7060.namprd08.prod.outlook.com>
In-Reply-To: <BY3PR08MB706038003E2AF751B97FAB8CF7DE9@BY3PR08MB7060.namprd08.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 03 Mar 2023 17:49:57 -0500
Message-ID: <CABNhwV3Ms2zEJ41=Ajh34kB5E+t43+79_rE9MyuvEyF_vAdbjg@mail.gmail.com>
To: "Jorge Rabadan (Nokia)" <jorge.rabadan@nokia.com>
Cc: Menachem Dodge <mdodge@drivenets.com>, "bess@ietf.org" <bess@ietf.org>
Content-Type: multipart/related; boundary="0000000000006632cd05f606c4ac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/7FSJLuKdmFrSb0E-IbZSoObVjoA>
Subject: Re: [bess] Section 8.5 of draft-ietf-bess-rfc7432bis
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: Fri, 03 Mar 2023 22:50:14 -0000

Hi Jorge

As defined in RFC 8584 AC-DF and HRW are independent of each other.

RFC 8584 updates RFC 7432, however RFC 7432 bis does not update any aspect
of RFC 8584 including HRW as you stated.

I would think HRW would be the new default algorithm used for DF election
and would not be a knob as it fixes the major deficiencies with the modulus
algorithm.

Thanks

Gyan
On Fri, Feb 10, 2023 at 2:01 PM Jorge Rabadan (Nokia) <
jorge.rabadan@nokia.com> wrote:

> Hi Menachem,
>
>
>
> The way I see it, draft-ietf-bess-rfc7432bis will obsolete RFC7432, but it
> does not update or change RFC8584, so I don’t think
> draft-ietf-bess-rfc7432bis needs to repeat the aspects of RFC8584.
>
>
>
> In particular, the AC-DF, as the other capabilities defined in other
> documents, is a capability that can be turned on or off. While it is very
> useful in many cases, it actually needs to be disabled in some others,
> e.g., draft-ietf-bess-evpn-mh-pa-07
> <https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-mh-pa-07>
>
>
>
> So the answer to your second question could be that the AC-DF capability
> should be configurable in the implementation, and used on all cases where
> issues with individual Attachment Circuits may create blackholes. However,
> it has to be disabled in case of port-active multi-homing.
>
>
>
> My 2 cents..
>
>
>
> Thanks.
>
> Jorge
>
>
>
>
>
> *From: *BESS <bess-bounces@ietf.org> on behalf of Menachem Dodge <
> mdodge@drivenets.com>
> *Date: *Friday, February 10, 2023 at 8:10 AM
> *To: *bess@ietf.org <bess@ietf.org>
> *Subject: *[bess] Section 8.5 of draft-ietf-bess-rfc7432bis
>
> Some people who received this message don't often get email from
> mdodge@drivenets.com. Learn why this is important
> <https://aka.ms/LearnAboutSenderIdentification>
>
> Hello All,
>
>
>
> In section 8.5 of draft-ietf-bess-rfc7432bis there is a reference to the
> Finite State Machine in section 2.1 of RFC 8584.
>
>
>
> However, in section 4 of RFC 8584 the AC Influenced DF Election Capability
> is described and it states that this updates Step 3 of the procedure for
> service carving of RFC 7432.
>
>
>
> Shouldn’t this AC-DF update be mentioned in the procedures of section 8.5
> of draft-ietf-bess-rfc7432bis?
>
>
>
> Is AC Influenced DF Election the preferred DF election method ?
>
>
>
>
>
> According to RFC 8584 “ The procedure discussed in this section is
> applicable to the DF
>
>    election in EVPN services [RFC7432 <https://datatracker.ietf.org/doc/html/rfc7432>] and EVPN VPWS [RFC8214 <https://datatracker.ietf.org/doc/html/rfc8214>]. “
>
>
>
>
>
>
>
> Thank you kindly.
>
>
>
> Best Regards,
>
>
>
> *Menachem Dodge**​**​**​**​*
>
> System Architect
>
> [image: signature_3305758272]
>
> +972-526175734
>
> mdodge@drivenets.com
>
> follow us on Linkedin <https://www.linkedin.com/company/drivenets>
>
> www.drivenets.com
>
> [image: DriveNets Network Cloud]
> <https://get.drivenets.com/mwc-2023-schedule-a-meeting>
>
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*

v2.23.0 | Report a Bug | By Email