[Bier] Re: Call for review for draft-ietf-bier-bfd

Greg Mirsky <gregimirsky@gmail.com> Wed, 17 July 2024 16:10 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7552EC180B6C; Wed, 17 Jul 2024 09:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 RoQjlvK-7Hqi; Wed, 17 Jul 2024 09:10:36 -0700 (PDT)
Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (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 D92CAC15199B; Wed, 17 Jul 2024 09:10:36 -0700 (PDT)
Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-66493332ebfso12145857b3.3; Wed, 17 Jul 2024 09:10:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721232636; x=1721837436; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0Rx3hbMc1BHzbpBPz48rOXSEGNQsA/o4wqDGnluQg6k=; b=c+4L8PGwMhF1Szu4G4EvSCZQfQefXGazuXw44X5tc7aiggh0OyOXbOx6QfhgnbjVFj paQDv5pICIvLRMft/rtfcC/fgrvsUcbBNtnxtJqgCjB+Xn7b8BwDxTiFrjgGSbQ3XNeW vJ91Dpa80kQu1P92BuAirRFEJ0VSduxuD2HTgrRirMVZVsg6/gYIkRKyfmuRn3NUl6ar k10tcnF48shC9cbmIxgke5olUNxJ2goqkbBKjx58e5ZSSUoz0EQ8S25nI1gbAsi1wfba dTmnZ5T8CIFvINBISURwPI7UhN/gT5924o5NQHcShpyEpueioAMvr8pE8vuPkrdM3wHW e01g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721232636; x=1721837436; 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=0Rx3hbMc1BHzbpBPz48rOXSEGNQsA/o4wqDGnluQg6k=; b=mkBXUabOixivqFuPK2kevWgUed7FFB3ZZHJ08YZNh1Z0A0GYSHePy3zgUVlxYSLEzq yjZhQKpBb/x8XYXmFJu/ytkCkaLdzpaS2Q4ri3xPwGCzBTcfujhvBSznPIrP8oIfQTs3 XHsIjX5eA8eSYbgVkWptroGoLOaNoh+oFAlzsPOZQnAFyZdCTE+bbyO9B8yx+yehIktJ LHvyskGC24/hgr5kVwt4YSOwZk8fX2xNFsMUORCFD3T4zFUxeOXWfo9eCqf/aPk2q1Q6 vPa8TSWyAw6IvPzfSKnbjccKgFAnJla561C2thv/d0/BxwpEoQPfwXDrNHLSMOHLuvCx evIg==
X-Forwarded-Encrypted: i=1; AJvYcCU3okrIfTnKzSIbwj5k6caisrE6SLUZvPRdpB24KqqoXq9of+N2vYwtby4ot8XizlzU14JiOXTFs2SugXtSaRzQ6mi97Ni6xxyfJtp2/E0z
X-Gm-Message-State: AOJu0Yy7NXDUXvhzI+tZxBI5iNq//HKSuOz2DiDA4sYXeYXCkn9r32fM 4/rFicAk7HQEZhOs/rGUqZwzJ9qDuvE6h7mvauyCqhhbW4XfHsk0JOK1bSNS8/ZV2Q+wji6+c7M nOaJ22qeYSNBswfOJGMfT3gSQMjU=
X-Google-Smtp-Source: AGHT+IES5o86EdZ2vFDQtTMOvQAhFot6PFEuUch/+RB7BPBnfMztNTpvMZYsB3awW5azF/GX1k++lqPWz1kHsnXTJaw=
X-Received: by 2002:a05:6902:2b84:b0:e03:b61f:22e6 with SMTP id 3f1490d57ef6-e05ed69b163mr2555502276.9.1721232635826; Wed, 17 Jul 2024 09:10:35 -0700 (PDT)
MIME-Version: 1.0
References: <20240708083233587mlc9r0U_6U-pzIaWxBP29@zte.com.cn> <80785901.872920.1721183324688@mail.yahoo.com>
In-Reply-To: <80785901.872920.1721183324688@mail.yahoo.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 17 Jul 2024 09:10:25 -0700
Message-ID: <CA+RyBmUG=3wT2aht2ZmLEpTzKW3E+PtjK5K=Qx-ounAOAZnpJg@mail.gmail.com>
To: Reshad Rahman <reshad@yahoo.com>
Content-Type: multipart/alternative; boundary="000000000000d59b4a061d73b395"
Message-ID-Hash: NFUERZECDICFOX4XTBEKNWCJKDZ63NLI
X-Message-ID-Hash: NFUERZECDICFOX4XTBEKNWCJKDZ63NLI
X-MailFrom: gregimirsky@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bier.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "zhang.zheng@zte.com.cn" <zhang.zheng@zte.com.cn>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "bier@ietf.org" <bier@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Bier] Re: Call for review for draft-ietf-bier-bfd
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/Thw-WU7ycFOlnMX0NQ5xxz5Djt0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Owner: <mailto:bier-owner@ietf.org>
List-Post: <mailto:bier@ietf.org>
List-Subscribe: <mailto:bier-join@ietf.org>
List-Unsubscribe: <mailto:bier-leave@ietf.org>

Hi Reshad,
thank you for your thorough review and thoughtful comments. I'll work on
addressing your concerns and share proposed updates for the discussion.

Regards,
Greg

On Tue, Jul 16, 2024 at 7:29 PM Reshad Rahman <reshad=
40yahoo.com@dmarc.ietf.org> wrote:

> Hi,
>
> Here are my comments:
>
> - Section 1, 2nd paragraph, states that RFC8562 defines a method for BFD
> to detect unicast failures between the sender and receivers in multipoint
> or multicast networks. Should that just say "detect failures" (remove
> unicast) instead?
> - Section 4, last paragraph. It says "this discriminator", should that be
> "My Discriminator"?
> - Section 4.1, last paragraph. Typo "the My Discriminator field n the" ->
> "the My Discriminator field in the"
> - Section 5.6 of RFC8562 on Session Establishment mentions that "Sessions
> on the tail MAY be established dynamically, based on the receipt of a
> multipoint BFD Control packet from the head". In this document it seems
> to be implied that sessions on the BFERs (tail nodes) are established via
> the bootstrapping mechanism. Whether true or not, this should be explicitly
> stated one way or the other.
> - Section 6.1, any concerns that the BFIR could be overwhelmed by a spike
> of incoming BFD control packets? I see this is not mentioned in RFC8563.
>
> Finally, shouldn't LSR WG also take a look at this doc (even though Les
> has already provided comments)?
>
> Regards,
> Reshad.
>
> On Sunday, July 7, 2024 at 08:32:38 PM EDT, <zhang.zheng@zte.com.cn>
> wrote:
>
>
> Hi Reshad,
>
> No problem for the extension.
>
> Thank you very much!
>
> Best regards,
>
> Sandy
>
>
> <http://www.zte.com.cn/>
> Original
> *From: *ReshadRahman <reshad@yahoo.com>
> *To: *rtg-bfd@ietf.org <rtg-bfd@ietf.org>;bier@ietf.org <bier@ietf.org>;
> 张征00007940;
> *Date: *2024年07月08日 03:56
> *Subject: **Re: Call for review for draft-ietf-bier-bfd*
> Hi,
>
> Thanks Sandy for forwarding the document to the BFD WG.
>
> I was planning to review this document but work and a work-trip got in the
> way. Could we please get a 1-week extension?
>
> BFD WG, please review this document.
>
> Regards,
> Reshad.
>
>
> On Tuesday, June 25, 2024 at 03:26:28 AM EDT, <zhang.zheng@zte.com.cn>
> wrote:
>
>
> Hi,
>
> The draft-ietf-bier-bfd passed last call in BIER WG.
>
> We'd like to get more review in BFD WG:
> https://datatracker.ietf.org/doc/draft-ietf-bier-bfd/
>
> Comments and suggestion welcomed, please send your comments before 9th,
> July.
>
>
> And please volunteer if you want to be the shepherd of this draft.
>
> Thank you!
>
> Best regards,
>
> Sandy
>
>
>
>
> _______________________________________________
> BIER mailing list -- bier@ietf.org
> To unsubscribe send an email to bier-leave@ietf.org
>