[Bier] Opsdir last call review of draft-ietf-bier-php-12

Jen Linkova via Datatracker <noreply@ietf.org> Mon, 30 September 2024 19:54 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jen Linkova via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172772605076.609363.1679581405021106464@dt-datatracker-7bbd96684-zjf54>
Date: Mon, 30 Sep 2024 12:54:10 -0700
Message-ID-Hash: 2T35RYRAMFX626SYHO44RI2UYQHZMIMA
CC: bier@ietf.org, draft-ietf-bier-php.all@ietf.org, last-call@ietf.org
Reply-To: Jen Linkova <furry13@gmail.com>
Subject: [Bier] Opsdir last call review of draft-ietf-bier-php-12
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/rJKK9GNnFzd17F5N9IxYQLglYK0>

Reviewer: Jen Linkova
Review result: Ready

The document is nicely written and easy to understand even by someone who is
not familiar with BIER.

I have one minor question/comment though.
If I understand correctly (from looking at rfc8279), when the BIER header is
removed,  by default the TTL/Hoplimit in the payload is not updated. Does it
mean that if the BIER header is removed one hop earlier (with PHP), the last
hop might become visible to traceroute-like tools? Not sure if it should be
mentioned in the operational consideration section?

Thanks!

[Bier] Opsdir last call review of draft-ietf-bier… Jen Linkova via Datatracker