[ippm] Intdir telechat review of draft-ietf-ippm-rfc8321bis-02

Timothy Winters via Datatracker <noreply@ietf.org> Fri, 15 July 2022 13:52 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 01ED0C188728; Fri, 15 Jul 2022 06:52:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Timothy Winters via Datatracker <noreply@ietf.org>
To: int-dir@ietf.org
Cc: draft-ietf-ippm-rfc8321bis.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: <165789317100.34126.9786306829689121898@ietfa.amsl.com>
Reply-To: Timothy Winters <tim@qacafe.com>
Date: Fri, 15 Jul 2022 06:52:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/IManjUHhkWVeMbnr_lmrChD7NWc>
Subject: [ippm] Intdir telechat review of draft-ietf-ippm-rfc8321bis-02
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: Fri, 15 Jul 2022 13:52:51 -0000

Reviewer: Timothy Winters
Review result: Not Ready

draft-ietf-ippm-rfc8321bis-02

I am an assigned INT directorate reviewer for draft-ietf-ippm-rfc8321bis-02.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received. For more
details on the INT Directorate, see
https://datatracker.ietf.org/group/intdir/about/
<https://datatracker.ietf.org/group/intdir/about/>.

Based on my review, if I was on the IESG I would ballot this document as
DISCUSS.

DISCUSS:
Section 3.1
This section states two possible methods using either a fixed number of packets
or fixed timer.  Only fixed timer is defined in draft.  I would think that
supporting the fixed timer method would be a MUST for implementations of this
document.

Section 3.2
Suggest a lower case must for clock network synch.    I would suggest using a
capital MUST, if the clocks aren't in synch this method will not work properly.
  Additionally, I was surprised there are no suggesting on what to use to keep
the clocks in synch (NTP, PTP) or precision suggested in time keeping
mechanism.  These methods are referenced in Section 7 but I think it would make
sense to give people the options in this section.

Section 7.1
While is says recommended to be a controlled domain, it should document what
happens if it leaves the controlled and how to protect the borders of the
domain.

NIT:
OLD:
As discussed in the previous section, a simple way to create the
   blocks is to "color" the traffic (two colors are sufficient), so that
   packets belonging to different consecutive blocks will have different
   colors."

New:
As discussed in the previous section, a simple way to create the
   blocks is to "color" the traffic (two colors are sufficient), so that
   packets belonging to alternate consecutive blocks will have different
   colors.