A question about the draft-wang-bess-sbfd-discriminator

Greg Mirsky <gregimirsky@gmail.com> Mon, 14 March 2022 16:44 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9787B3A0C0E; Mon, 14 Mar 2022 09:44:29 -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 nFyyfKL6nEav; Mon, 14 Mar 2022 09:44:25 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 D63DC3A0C05; Mon, 14 Mar 2022 09:44:21 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id f7so1400525qtk.1; Mon, 14 Mar 2022 09:44:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=V2LS0Si+CSeniuxNMowdr52EHe1M5Op6Cd8bGXE50Sk=; b=dfzd2wEIasGyfyOIyS2TjVmnC+hy+XqCJ2B6HRj85Al4NikVV3GD52eq0PlZwAeIh+ ajhf+LRv2HrW9VEnEoCTvWUSUmn72g8Fy1l5pWmKgpH53FIZxg5uKSGOZ+/+pnp05Coi TlKcjwc5latu+lHtccyd/ViTibI11BxAiEeNWSdF8wSvfwCt3jZ/slOWJZLj+Cj39zy4 P1da+XhshUgqNCfMwI9Np3NwZ+fAP3OLXdoI6hrzP0J3HlwCh1CXPHt3SEnukYodPxGs 1mVgJENI7jkLub+HLpg7Vl5krJkQJCfTpvgQpLtYfM/SkvS0yZG5o8PX7+iDw97GFPIC bHcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=V2LS0Si+CSeniuxNMowdr52EHe1M5Op6Cd8bGXE50Sk=; b=RsFD/e5vPr5ThlzQxOznW3Ug6byMBtZxgDg4N4LIHD7dKh85Rlf428XCB+MBAnmuxd o82uDPtBopbRh1zr7GdCt+bzc2RqtUuxigeaqwJJQaU7+Tzr1tfdF3XmiBK8usw9Cj9n mJgZpbKQ1T3K1ARrmwUZRsTNuGsxfpfbClLVelrOoQ1mCB16Q4u030oAzdDZATAvaOWu oyxsIIeoFnkfn5zNp15+j5/4IY6rkilOjQGSMAbXGA4x057TuW3GsPTGQUGzvEa/z4St QTXz/VZJg0ad7qxLIqKqXeWZ7dWw8x6hjlRun/3rpu745TxNDT1Tphng0WCPESuld9CM fwnw==
X-Gm-Message-State: AOAM531Y8Ti1ObiIa1rLHQJWcgh/9Mw6bIf46Fh14gWYd4d1Nc2KzXEJ caMGGXlS8lwnKMICt8ZAfc11UtQup90r2MpkqT0=
X-Google-Smtp-Source: ABdhPJxvRVzZ7B/4XwRowoJBrG2Nl7ADBUr4WUiYWaR6jp8A2cOeRnyhBFcJkWxLP7AiUATwp7WTDoptrtT/5HYPTWE=
X-Received: by 2002:ac8:5a84:0:b0:2e1:4f1d:36fb with SMTP id c4-20020ac85a84000000b002e14f1d36fbmr19359648qtc.54.1647276260242; Mon, 14 Mar 2022 09:44:20 -0700 (PDT)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 14 Mar 2022 09:44:09 -0700
Message-ID: <CA+RyBmUEULD__UWa6yeoanEn6jWLXjOREcZnJ7o+HU7UXgyqGQ@mail.gmail.com>
Subject: A question about the draft-wang-bess-sbfd-discriminator
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>
Content-Type: multipart/alternative; boundary="00000000000056bcaa05da306425"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Weo6kjz6uohx4fGNTygoonNoD-c>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2022 16:44:30 -0000

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