[Bier] John Scudder's No Objection on draft-ietf-bier-php-15: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Thu, 05 December 2024 02:00 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: bier@ietf.org
Delivered-To: bier@ietfa.amsl.com
Received: from [10.244.8.175] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id BC477C15154D; Wed, 4 Dec 2024 18:00:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.28.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <173336401643.1877878.16353714372546178531@dt-datatracker-5679c9c6d-qbvvv>
Date: Wed, 04 Dec 2024 18:00:16 -0800
Message-ID-Hash: TETRE2NKFORCNDVL3R2LVC25XP4NZRY5
X-Message-ID-Hash: TETRE2NKFORCNDVL3R2LVC25XP4NZRY5
X-MailFrom: noreply@ietf.org
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: draft-ietf-bier-php@ietf.org, bier-chairs@ietf.org, bier@ietf.org, xiao.min2@zte.com.cn
X-Mailman-Version: 3.3.9rc6
Reply-To: John Scudder <jgs@juniper.net>
Subject: [Bier] John Scudder's No Objection on draft-ietf-bier-php-15: (with COMMENT)
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/zR4kFVqtJm80A_81YM_w2y1vYhQ>
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>

John Scudder has entered the following ballot position for
draft-ietf-bier-php-15: 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-bier-php/



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

Thanks for the well-written document. I have just a couple of minor comments
about the Introduction.

### Section 1, BFR

It seems relatively obvious that "BFR" must mean "BIER Forwarding Router" but
please expand it on first use.

### Section 1, directly or indirectly?

   A potential solution to this issue is the use of Penultimate Hop
   Popping (PHP), whereby the upstream BFR pops the BIER header
   [RFC8296] and transmits the payload directly.  This transmission can
   occur either directly or indirectly through any type of tunnel to the
   PE.

The end of the first sentence ("transmits the payload directly") conflicts with
the beginning of the next ("can occur [...] indirectly"). I think I get what
you mean but it's still jarring. Maybe something like "... and transmits the
payload without BIER encapsulation"?