Re: [bess] A question about the draft-wang-bess-sbfd-discriminator
Greg Mirsky <gregimirsky@gmail.com> Sat, 19 March 2022 20:29 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 7B1F73A07B2; Sat, 19 Mar 2022 13:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, 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 GdxFhFLMQ7rr; Sat, 19 Mar 2022 13:29:38 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 D6F793A176E; Sat, 19 Mar 2022 13:29:37 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id g24so14128941lja.7; Sat, 19 Mar 2022 13:29:37 -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=0TE9A7QBD/3M1QcsaFWAXJPxDDCocJrvsGXwfPxAHsc=; b=ag0zkeL+AfTCwfgmPtBYrHSCaavGcJ3EU7gzGvDyu3OVJqWzMO7ArkoCvQqotcBOFQ 7WcezzFvIdHBYI1QFDtJ8ukDoGqIi0yle5hpt1Jofn7CAAGb5Z/P+Lt2J5KeUzJ79/Td 5FUfBnV0AXIIlscgqCsHa/UfDJvunBW3OTyeVSCMN+97Ddwi/QvKcz0HZKsQNa1HGxu6 w5IG5cZxq2csHjBfBzr0I6w5umXvEHsORa20DyNn9xPG5iqsCGpEyhMXqW1+eGtxtwKh cw2Oq7Iy+n40BV2wmHqEcGZQjD6Fu6vH79FjuVSgIFvPzEGyqb5ASdMRU90VO+PJiihz 9mxg==
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=0TE9A7QBD/3M1QcsaFWAXJPxDDCocJrvsGXwfPxAHsc=; b=sXBmcYtNqksZODtv7ZTPf3gslWLykoGauAAafOtpqS8EiIYIMS7YvQja8HzGbUvCGt xVBLE+kVTxc9xB3p2xtC8COtq8kstNC4aES1NKdfCYQ4mVcBGKUER9oB/m1P9RfED+LX FNppc/keerc61j1D5O73SS/CMzaz3t5qdrUuVL7grxIsqI8M1W3NG8E95pigz5EE7syp 4wzqC9/jEQzy1MuhwTRckXoaN8dJlSHUNAVD9I12iUFwX3eiZsfdMuNiFFcAk0fUQbd3 pdgAyRDUuPx9d1nKfQIN4jeeYLeXsCNeK/3cNdDGcrW3LthmEntAUD8EAZIFCcVz7H8T Bq2Q==
X-Gm-Message-State: AOAM533SogIl0A0antJhX2RjJHSGg2LHGcX3Fz0JM7mb5iq6GaZ1HtuJ zSu+j+QtHxF5nKKuuX4i9d1Gvguxbo4xiZAHU1IbZfxl/LI=
X-Google-Smtp-Source: ABdhPJzpFiW1f6JNY8/Lc1chauQEglqHWjIWkv0n8q4ssU7AhRpG6RWouTHbVenMpeHbXgTp16NZZd00EONcEDYgXo0=
X-Received: by 2002:a2e:b012:0:b0:249:8061:8486 with SMTP id y18-20020a2eb012000000b0024980618486mr612985ljk.463.1647721775090; Sat, 19 Mar 2022 13:29:35 -0700 (PDT)
MIME-Version: 1.0
References: <CA+RyBmUEULD__UWa6yeoanEn6jWLXjOREcZnJ7o+HU7UXgyqGQ@mail.gmail.com> <1c74ced331ac4ab3b9ebf9b74b1ec21d@huawei.com> <CA+RyBmW5EwE0EtViBjjE0J-7Zkw0q7bp6mpBP2GSWdLUd5Kxgw@mail.gmail.com> <b108f5a3ad474bcfb95629a9b955b320@huawei.com>
In-Reply-To: <b108f5a3ad474bcfb95629a9b955b320@huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sat, 19 Mar 2022 13:29:23 -0700
Message-ID: <CA+RyBmXhTJDvX+A_scYk5y5Z_D=4nWdQRs_O1wFgp6vyXzQHMA@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="00000000000017ce1205da981f51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/bZbWF8wCUVxvhzuwojIjXJ5mOgQ>
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: Sat, 19 Mar 2022 20:29:43 -0000
Hi Haibo, thank you for the clarification. I may suggest a text for Section 3: In some EVPN deployments, for example, when it spans over multiple domains, only one of a pair of interconnected PEs benefits from monitoring the status of the connection. In such a case, using S-BFD [RFC7880] is advantageous as it reduces the load on one of the PEs while providing the benefit of faster convergence. The following sections provide examples of EVPNs that would benefit from using S-BFD. What are your thoughts? Regards, Greg On Tue, Mar 15, 2022 at 7:18 PM Wanghaibo (Rainsword) < rainsword.wang@huawei.com> wrote: > Hi Greg, > > Thanks for you comments. > > Yes, the resources will save at PE1 and PE2 as figure 1. This is a typical > 3PE scenario. > > The service is like this: > > +-----+ +-----+ +-----+ > > | UCE1|----| APE1|--------|SPE1 |, > > +-----+ +-----+` /+-----+ `. > > `, .' `.+-----+ > > ...... \/ | SCE1| > > /\ `+-----+ > > ` `. ,' > > +-----+ +-----+,' .+-----+ ` > > | uCEn|----| APEn|--------|SPE2 |` > > +-----+ +-----+ +-----+ > > There may be many Access PEs,used to access User CE. And they all > multi-homed to a couple Servicc PE, SPE1 and SPE2. > > (shown as the PE1 and PE2 as figure 1) > > Access PE needs to detect Service PE’s reachability. Access PE > creates SBFD session as an initiator, SPE as the reflector. This will save > Service PEs’ resources. > > > > Regards, > > Haibo > > > > *From:* Greg Mirsky [mailto:gregimirsky@gmail.com] > *Sent:* Tuesday, March 15, 2022 11:12 PM > *To:* Wanghaibo (Rainsword) <rainsword.wang@huawei.com> > *Cc:* draft-wang-bess-sbfd-discriminator@ietf.org; BESS <bess@ietf.org>; > rtg-bfd WG <rtg-bfd@ietf.org> > *Subject:* Re: A question about the draft-wang-bess-sbfd-discriminator > > > > 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 > >
- [bess] A question about the draft-wang-bess-sbfd-… Greg Mirsky
- Re: [bess] A question about the draft-wang-bess-s… Greg Mirsky
- Re: [bess] A question about the draft-wang-bess-s… Wanghaibo (Rainsword)
- Re: [bess] A question about the draft-wang-bess-s… Wanghaibo (Rainsword)
- Re: [bess] A question about the draft-wang-bess-s… Greg Mirsky
- Re: [bess] A question about the draft-wang-bess-s… Wanghaibo (Rainsword)
- Re: [bess] A question about the draft-wang-bess-s… Greg Mirsky
- Re: [bess] A question about the draft-wang-bess-s… Wanghaibo (Rainsword)