[bess] Zaheduzzaman Sarker's No Objection on draft-ietf-bess-evpn-fast-df-recovery-10: (with COMMENT)

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Wed, 21 August 2024 11:16 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from [10.244.2.52] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF54C14F74E; Wed, 21 Aug 2024 04:16:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.22.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172423898196.2233625.14123611054643179072@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Wed, 21 Aug 2024 04:16:21 -0700
Message-ID-Hash: S53ITC2Z7225JUJNQTCRRHUW5J55JSXG
X-Message-ID-Hash: S53ITC2Z7225JUJNQTCRRHUW5J55JSXG
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bess.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-bess-evpn-fast-df-recovery@ietf.org, bess-chairs@ietf.org, bess@ietf.org, matthew.bocci@nokia.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Subject: [bess] Zaheduzzaman Sarker's No Objection on draft-ietf-bess-evpn-fast-df-recovery-10: (with COMMENT)
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/3SrcPUrR6FGcxNSEUaKhoC6DCP4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Owner: <mailto:bess-owner@ietf.org>
List-Post: <mailto:bess@ietf.org>
List-Subscribe: <mailto:bess-join@ietf.org>
List-Unsubscribe: <mailto:bess-leave@ietf.org>

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-bess-evpn-fast-df-recovery-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-fast-df-recovery/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for working on this specification.

I have no comments from transport protocol point of view. However, I am missing
how the skew (in section 3) will be calculated. Is this well defined? Is there
a scenario where more than one PEs take over if PE2 (in the example) fails? if
yes, how would then the skewing work?