[Bier] Zaheduzzaman Sarker's No Objection on draft-ietf-bier-te-arch-10: (with COMMENT)

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Thu, 26 August 2021 12:15 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C48C03A0AB2; Thu, 26 Aug 2021 05:15:48 -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>
Cc: draft-ietf-bier-te-arch@ietf.org, bier-chairs@ietf.org, bier@ietf.org, Xuesong Geng <gengxuesong@huawei.com>, aretana.ietf@gmail.com, gengxuesong@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Message-ID: <162998014877.28890.6879473192533589908@ietfa.amsl.com>
Date: Thu, 26 Aug 2021 05:15:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/546I-OoR9e-OckBGtd1oRsZS5gA>
Subject: [Bier] Zaheduzzaman Sarker's No Objection on draft-ietf-bier-te-arch-10: (with COMMENT)
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2021 12:15:49 -0000

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-bier-te-arch-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/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bier-te-arch/



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

Thanks for the efforts on this document. Due to lack of time on my side
(apologies) I quickly read through the document and didn't find any transport
related issue sticking out. I agree with TSVART reviewer (Thanks Tommy Pauly)
that this seems useful to reduce duplicate packets to avoid unnecessary effects
in the higher layers.

I have two clarification questions:

* Section 5.3.6.2: if there is 6 SIs in the example then why does the it loops
through only 5 of them? see the text below -

    On all area edge BFR, bea in
   BIFT:SI=k|k=2...6 is populated with forward_routed(BFRka) and beb in
   BIFT:SI=k with forward_routed(BFRkb).

   For BIER-TE forwarding of a packet to a subset of BFERs across all
   areas, a BFIR would create at most 6 copies, with SI=1...SI=6,

* This might be completely my misunderstanding, however, I understood that
BIER-TE supports multiple domains and subdomains, where multiple domains may
not be under same implementer. In that case, would their not be issues for
BIER-TE controllers to show robust behavior if there is no default ECMP
algorithm? Also the implementer is expected to document their ECMP of choice, I
didn't understand in what format and to who the documentation applies. Also
there is no discussions on what happens if there is no such documentation.