Re: [ippm] Genart last call review of draft-ietf-ippm-initial-registry-12

Joel Halpern Direct <jmh.direct@joelhalpern.com> Sun, 03 November 2019 21:00 UTC

Return-Path: <jmh.direct@joelhalpern.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716CC1200C1; Sun, 3 Nov 2019 13:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THMlRh5Vouvc; Sun, 3 Nov 2019 13:00:07 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32C0912002E; Sun, 3 Nov 2019 13:00:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 475pGb14rYz2mH6J; Sun, 3 Nov 2019 13:00:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1572814807; bh=k6ym5aEFi5YktGv9owd+c1c4JLqnQJcmAAfvG5vN2NE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=b1AI89dYXUJNCzgd7G/DU12iZAvjOejZoK76nBhlmLVDIshOq8NW/RS5qHDeMYFC0 l3lj9nT+od1gsMN+ng2g4swjFezBZdoj3JfXOraOpP/dFyBP4GuQ8Rn/sQUmY5xbk/ C5D6FsvzIYEI9VxobUtIMjeJclu+0GzCC5usEsdw=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 475pGZ2yq2z2mH6H; Sun, 3 Nov 2019 13:00:06 -0800 (PST)
To: "MORTON, ALFRED C (AL)" <acm@research.att.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-ippm-initial-registry.all@ietf.org" <draft-ietf-ippm-initial-registry.all@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
References: <157262730194.31927.5524715609259531175@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CFA0B6B28E@njmtexg5.research.att.com>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <e1ab718e-cc0b-2e05-b3f9-e696ed8df5fd@joelhalpern.com>
Date: Sun, 03 Nov 2019 16:00:05 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CFA0B6B28E@njmtexg5.research.att.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/v4cdERzPtcX1A2EXD9AhzYhba5I>
Subject: Re: [ippm] Genart last call review of draft-ietf-ippm-initial-registry-12
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Sun, 03 Nov 2019 21:00:10 -0000

Thanks Al.  I presumed all the ducks were in a row, but thought I should 
ask to be certain.

Yours,
Joel

On 11/3/2019 3:14 PM, MORTON, ALFRED C (AL) wrote:
> Hi Joel,
> Thanks for your review, please see replies below.
> Al
> 
>> -----Original Message-----
>> From: Joel Halpern via Datatracker [mailto:noreply@ietf.org]
>> Sent: Friday, November 1, 2019 12:55 PM
>> To: gen-art@ietf.org
>> Cc: last-call@ietf.org; draft-ietf-ippm-initial-registry.all@ietf.org;
>> ippm@ietf.org
>> Subject: Genart last call review of draft-ietf-ippm-initial-registry-12
>>
>> Reviewer: Joel Halpern
>> Review result: Ready
>>
>> 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
>>
>> <https://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__trac.ietf.org_trac_gen_wiki_GenArtfaq&d=DwICaQ&c=LFYZ-
>> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=GTgiUHp01_savOvQS49iOt8XRHfRw
>> hPgZj-TNotgKGk&s=M0ib3zYg2qffmRujLJv2h_WHQ16W9fOYat9hNtBqcFk&e=>.
>>
>> Document: draft-ietf-ippm-initial-registry-12
>> Reviewer: Joel Halpern
>> Review Date: 2019-11-01
>> IETF LC End Date: 2019-11-06
>> IESG Telechat date: Not scheduled for a telechat
>>
>> Summary: This document is ready for publication as a Proposed Standard
>>
>> Side note: I presume that as part of the process for
>> draft-ietf-ippm-metric-registry (the normative reference the defines the
>> structure used in this document) there has been discussion with IANA explicitly
>> about the fact that this registry has an extremely large number of
>> columns, some with extremely verbose content, and it will likely take some work for
>> IANA to determine how to present this in a human-readable fashion?  And the
>> lesser point that is probably covered by existing procedures, but I wanted to
>> check, that IANA is prepared to fill in the URLs scattered throughout the
>> document?
> [acm]
> Yes and Yes. We prepared a mock-up of the new Registry at various stages
> of development. Humbly, it was my idea to make the registry entries both
> readable and useful. The IANA reps suggested the mock-up early-on, and we have
> shared the different versions with the IPPM WG.  We/IANA plan to make the
> mock-up more widely available (but we failed to do that in time for Last Call).
>>
>> Second note:  I did not review the accuracy of the descriptions of the metrics,
>> but only looked for clarity.  This is material well known to the WG, and mostly
>> derived from other documents this or closely related working groups have
>> produced.
>>
>> Major issues: N/A
>>
>> Minor issues:
>>      For those entries that are defining two (or more) closely related metrics,
>>      should the document actually have two (or more) lines for URL, since the
>>      text says that IANA is to assign two URLs.  (And the list of differing
>>      fields should presumably include URL?)
> [acm]
> There are sections of the document that define more than one registry entry,
> so yes, there will be >1 URLs, etc. in the corresponding rows.
>>
>>      In the first part of section 5, there is a note about potentially splitting
>>      the registry entry into two registry entries.  I can not understand the
>>      note.  The registry is either defined with one entry or defined with two
>>      entries.  Is this still an open item?  (If so, my "ready" above clearly
>>      should be "Ready with issues.")  I think it is just an erroneous retention
>>      of text from earlier?
> [acm]
> Exactly, it is a note left-stranded by editing later in the section,
> thanks for catching it - deleted in the working version.
> 
>>
>> Nits/editorial comments:
>>      If there are no roles to define in 5.3.6, shouldn't it say "N/A"
> [acm]
> Actually, it should define the Roles (Src and Dst) as with other Metrics.
> Something went wrong with formatting here - the text below the
> section header disappeared... thanks for catching that!
> 
>>      Some comments and remarks say "None" which makes sense.  Some say
>>      "Additional (Informational) details for this entry" which seems to be
>>      text left over from the template that should say "None"?
> [acm]
> Right,  found and replaced in working copy.
> 
>>
>