Tsvart last call review of draft-ietf-6man-ipv6-alt-mark-06

Yoshifumi Nishida via Datatracker <noreply@ietf.org> Wed, 16 June 2021 08:48 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E29E3A09E4; Wed, 16 Jun 2021 01:48:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoshifumi Nishida via Datatracker <noreply@ietf.org>
To: tsv-art@ietf.org
Cc: draft-ietf-6man-ipv6-alt-mark.all@ietf.org, ipv6@ietf.org, last-call@ietf.org
Subject: Tsvart last call review of draft-ietf-6man-ipv6-alt-mark-06
X-Test-IDTracker: no
X-IETF-IDTracker: 7.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162383331612.20524.16296649297265738669@ietfa.amsl.com>
Reply-To: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Wed, 16 Jun 2021 01:48:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/N5rtUnhfW82dFkM1biIglhNdy3s>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jun 2021 08:48:37 -0000

Reviewer: Yoshifumi Nishida
Review result: On the Right Track

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

Summary: I think this document is on the right track, but it needs to address
                   the following points to be published as a PS document.

1: I think the doc should provide a high-level view of the usage of this
   method. For example, it is not clear to me how measurement nodes interact
   each other, exchange and compare information, etc. If it is provided in 
   other documents, it should be referred.

2: Section 5.1: "By counting the number of packets in each batch and
   comparing the values measured by different network nodes along the path,
   it is possible to measure the packet loss occurred in any single batch
   between any two nodes."

    -> It is not clear to me how two nodes exchanges the measured counts.
       This point should be clarified even if if it's out-of-scope of the

3: Section 5.1: "In a few words this implies that the length of the batches
   MUST be chosen large enough so that the method is not affected by those

    -> It would be better to have recommended length values here.
       At least, it would be better to provide some guidances to decide
       the value.

4: Section 5.1:
   Can we change the length of batch in the middle of data transfer?
   Also, is there any concerns to use different length for each flow?
   I think it would be better to specify on these points.

5: Section 5.2:
   I am wondering if this approach requires time sync between nodes or not.
   This point should be clarified.

6: Section 5.2:
   "Whenever the L bit changes and a new batch starts, a network node
   can store the timestamp of the first packet of the new batch, that
   timestamp can be compared with the timestamp of the first packet of the
   same batch on a second node to compute packet delay."

     -> It is not clear to me how two nodes compare the stored timestamps.
        This point should be clarified.

7: Section 5.2:
   What's the benefits for using the approach described in 1.?
   The use cases for it should be described.