[ippm] Opsdir last call review of draft-ietf-ippm-ioam-ipv6-options-08

Tianran Zhou via Datatracker <noreply@ietf.org> Wed, 13 July 2022 07:08 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63315C15949B; Wed, 13 Jul 2022 00:08:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tianran Zhou via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-ippm-ioam-ipv6-options.all@ietf.org, ippm@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165769613739.6412.16563378039511941850@ietfa.amsl.com>
Reply-To: Tianran Zhou <zhoutianran@huawei.com>
Date: Wed, 13 Jul 2022 00:08:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Scl0Tdjv5N9DEmtpQ0ofMNw7CLw>
Subject: [ippm] Opsdir last call review of draft-ietf-ippm-ioam-ipv6-options-08
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2022 07:08:57 -0000

Reviewer: Tianran Zhou
Review result: Has Issues

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

It is good to describe the deployment consideration in section 5. However, I
think there is an issue that the increamental tracing option will impact other
IPv6 extension header processing, e.g. SRH. This is similar to the
consideration about PMTU, which has many ways to detect. But it is different.
The increamental option is encapsulated in HbH which is the first EH. As the
option length expands, the intermedate node may not be able to process other
EHs. Typically, SRH is used for TE. This will break the network service.

Best,
Tianran