[Gen-art] Genart last call review of draft-ietf-ippm-ioam-data-11

Dan Romascanu via Datatracker <noreply@ietf.org> Sat, 05 December 2020 10:05 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 947C83A10DC; Sat, 5 Dec 2020 02:05:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: ippm@ietf.org, last-call@ietf.org, draft-ietf-ippm-ioam-data.all@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160716273455.18414.13800286326641344283@ietfa.amsl.com>
Reply-To: Dan Romascanu <dromasca@gmail.com>
Date: Sat, 05 Dec 2020 02:05:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/vzngkYWy-W-f0PHqAPNRlyNSwnw>
Subject: [Gen-art] Genart last call review of draft-ietf-ippm-ioam-data-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Dec 2020 10:05:35 -0000

Reviewer: Dan Romascanu
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-ippm-ioam-data-11
Reviewer: Dan Romascanu
Review Date: 2020-12-05
IETF LC End Date: 2020-12-08
IESG Telechat date: Not scheduled for a telechat


This is a very useful and rather complex document that discusses the data
fields and associated data types for IOAM that can be encapsulated into a
variety of protocols. It's well written, detailed and accurate. It is READY
from a Gen-ART perspective, with a few editorial comments that I suggest being
addressed before approval or as part of the final editorial process.

Major issues:

Minor issues:

Nits/editorial comments:

1. How are specific IOAM encapsulations being defined? Will specifications that
define IOAM encapsulations into various protocols be within the scope of the
IPPM WG? of the IETF? Do they require to be RFCs? Some clarification text would
be useful.

2. In Section I found the following:

> The authors
   acknowledge that in some operational cases there is a need for the
   units to be consistent across a packet path through the network,
   hence RECOMMEND the implementations to use standard units such as

'The authors ... RECOMMEND' seems a little bit odd. The active verb form is not
within the list of keywords as per [RFC2119], also mentioned in Section 3 of
this document. To be on the safe side I would recommend reformulating the
sentence so that the RECOMMENDED form is used. Alternatively, just do not use
capitalization here.

3. In Section 8.7 I found:

> The expert will post the request on the IPPM mailing list, and
   possibly on other relevant mailing lists, to allow for community

I assume that this means the IPPM WG mailing list. The abbreviation of IPPM may
be very familiar for the current audiences, but the situation may change in the
future. The scope even of this document may outlive the WG. I suggest to expand
IPPM in Section 3 and possibly reformulate the sentence so that posting the
request on the IPPM list does not sound as the eternal procedure.