Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

Greg Mirsky <gregimirsky@gmail.com> Tue, 15 March 2022 15:12 UTC

Return-Path: <gregimirsky@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 8DC233A1515; Tue, 15 Mar 2022 08:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PD_DSyD-hhwx; Tue, 15 Mar 2022 08:12:08 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 953173A150E; Tue, 15 Mar 2022 08:12:08 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id 1so15133476qke.1; Tue, 15 Mar 2022 08:12:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lSzftCuRpPr0JU/K0NekslXI/7Ov2Yo5pIRDGLYHbiU=; b=LWD/dXUxy02H9ZSrGUUc184jOJw0/8DXTXsDmqVrtxhVNfuM1Ej1wHhuf2QL8kDz1H kpCQefNjA+5a8lN3QwujZcFSyb6KNEYkbYeijT6WGPw36gmkr46AEIpwgaEZphPvf5zd AN98mblFoLlClYv3xVfaVqBsGXqtpRoi0klNYbXlZDSyo+0M08WU3sNmAGTXWdkHN0LV iU+KgKeszg77sgETLCfpm1k16cqz8DV5lV6LOmXJJ8PxvmgqewdD95IQnCqEfXQLSdJC pQDgDpS1VzmpXFyuUg85H74yRnPKibkpZDC/LeeGbQniQKI5ccWpR8fNe6hgQ43n/3k8 JF0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lSzftCuRpPr0JU/K0NekslXI/7Ov2Yo5pIRDGLYHbiU=; b=3V3gBW2bJuZ7/ioFUMlRWlwcn5w3N4I4u1p+n9HPB97eFd3GrUDJ3MSdjoiX5BdIPc Mm56szswD4k0+INX0flF24NHHNeuNvOUZRZ3UKY9hLUKgfZ+yJYWxu0PnioWMedMlB+k wgnMuwio4iSZuhX4YGLKa44VIozyPDhaE6N49kKFMUIsRpV1G9QRMwjqAkHfk+Q8spVz KBlC9lhwJupWH8ioAOmH6gF4uyus68HWs7lAyDmx8/bJf2HiQArc/15Q5ym7bBV7tcpN Vb8KuhZ4zmSAnlGZglt64ICKD7iPkR3yorj9IMURdZoVWqfTHmZjVFyyJyyjngzI07i7 TNMw==
X-Gm-Message-State: AOAM533KxCnpsAF80CFf6w5LdN++8oguDgCPLzzyyH5/OytJZk+SEAfP TBJgBV9mLbPFMSYoAYSUR0MyE0QsnTgb7PLndCJTFLtb
X-Google-Smtp-Source: ABdhPJxMznoasMZiXGbfnrsxf/t8CNu2pPUv9XGB5n75RHV1Z5S3d2dfLsq7XBu2/4ALJwIYrgDc8oRsqZl0fAUg1qY=
X-Received: by 2002:a05:620a:2591:b0:67a:f1ef:cda3 with SMTP id x17-20020a05620a259100b0067af1efcda3mr18787910qko.656.1647357127224; Tue, 15 Mar 2022 08:12:07 -0700 (PDT)
MIME-Version: 1.0
References: <CA+RyBmUEULD__UWa6yeoanEn6jWLXjOREcZnJ7o+HU7UXgyqGQ@mail.gmail.com> <1c74ced331ac4ab3b9ebf9b74b1ec21d@huawei.com>
In-Reply-To: <1c74ced331ac4ab3b9ebf9b74b1ec21d@huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 15 Mar 2022 08:11:56 -0700
Message-ID: <CA+RyBmW5EwE0EtViBjjE0J-7Zkw0q7bp6mpBP2GSWdLUd5Kxgw@mail.gmail.com>
To: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
Cc: "draft-wang-bess-sbfd-discriminator@ietf.org" <draft-wang-bess-sbfd-discriminator@ietf.org>, BESS <bess@ietf.org>, rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000062f32e05da4338be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/gGL6Tjwc9Qd5eHnWXptWUpDMee4>
Subject: Re: [bess] A question about the draft-wang-bess-sbfd-discriminator
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Mar 2022 15:12:14 -0000

Hi Haibo,
thank you for your expedient response. If I understand the scenario you're
addressing, it is where a single PE with moderate resources is connected to
a PE that acts as the edge device for the access network. To improve the
quality of user experience, customer's PE is connected to a secondary PE
that is used as a backup. You are concerned that maintaining two BFD
sessions on the customer's PE might overload the resource-limited PE. But
isn't that the PE that initiates S-BFD sessions toward two access
network edge PEs in your draft? I think that the savings are on the side of
these two PEs, not the subscriber's PE. Would you agree?

Regards,
Greg

On Tue, Mar 15, 2022 at 7:20 AM Wanghaibo (Rainsword) <
rainsword.wang@huawei.com> wrote:

> Hi Greg,
>
>        Thanks for your comments.
>
>        The scenario you pointed out is a 4PE scenario, but in our
> solution, a large number of scenarios are based on 3PE.
>
> In a 3PE scenario, deploying BFD wastes resources. A large number of
> single-homed PEs may be connected to the dual-homed PEs. The dual-homed PEs
> may not have enough resources to create BFD sessions.
>
>
>
> Regards,
>
> Haibo
>
>
>
> *From:* Greg Mirsky [mailto:gregimirsky@gmail.com]
> *Sent:* Tuesday, March 15, 2022 12:44 AM
> *To:* Wanghaibo (Rainsword) <rainsword.wang@huawei.com>;
> draft-wang-bess-sbfd-discriminator@ietf.org; BESS <bess@ietf.org>;
> rtg-bfd WG <rtg-bfd@ietf.org>
> *Subject:* A question about the draft-wang-bess-sbfd-discriminator
>
>
>
> Hi Haibo and the Authors,
>
> thank you for updating the draft. I've read the new version and have a
> question about the use case presented in the document. There are three PEs
> with two of them providing redundant access to a CE. It appears that a more
> general case would be if both CEs use redundant connections to the EVPN.
> Asume, PE4 is added and connected to CE2. In that case, it seems reasonable
> that each PE is monitoring remote PEs, i.e., PE1 monitors PE3 and PE4, PE2
> - PE3 and PE4, PE3 - PE1 and PE2, and PE4 - PE1 and PE2. So, now there are
> pairs of S-BFD sessions between PEs connected to CE1 and CE2 respectively.
> That seems like too many sessions and that number can be reduced if one
> uses BFD instead of S-BFD. Would you agree? To simplify operations, it
> might be helpful to use the technique described in
> draft-ietf-bfd-unsolicited
> <https://datatracker.ietf.org/doc/html/draft-ietf-bfd-unsolicited-09>. In
> the recent discussion of the draft on the BFD WG ML, the authors noted that
> they are working on extending the scope to include the multi-hop BFD.
>
> Greatly appreciate your thoughts about the number of S-BFD sessions.
>
>
>
> Regards,
>
> Greg
>