[Gen-art] Genart last call review of draft-ietf-netvc-testing-08

Francesca Palombini via Datatracker <noreply@ietf.org> Mon, 03 June 2019 11:59 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 5D4B8120114; Mon, 3 Jun 2019 04:59:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-ietf-netvc-testing.all@ietf.org, video-codec@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <155956316822.24369.4530339060904691343@ietfa.amsl.com>
Date: Mon, 03 Jun 2019 04:59:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/5VYNPF6JKe4MssTms4t9kcG7RNg>
Subject: [Gen-art] Genart last call review of draft-ietf-netvc-testing-08
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: Mon, 03 Jun 2019 11:59:29 -0000

Reviewer: Francesca Palombini
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

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-netvc-testing-08
Reviewer: Francesca Palombini
Review Date: 2019-06-02
IETF LC End Date: 2019-06-04
IESG Telechat date: Not scheduled for a telechat

Summary: This draft is basically ready for publication, but has nits that
should be fixed before publication.

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:

* The document is missing the IANA section and Security Considerations section.
Although they do not apply (as the shepherd noted), these sections are
required. (See https://tools.ietf.org/html/rfc7322#section-4.8.5 and
https://tools.ietf.org/html/rfc7322#section-4.8.3)

* Outdated reference: A later version (-09) exists of
draft-ietf-netvc-requirements-08

All following comments are suggestions that would have helped a non-expert
reader (feel free to disregard):

* Section 2 - Subjective testing is mentioned in the first sentence with no
introduction. Although quite clear, a short definition or a reference to
literature would have been helpful.

* Section 2, second to last paragraph - The text is somewhat not well
formulated. "... even if the group agrees that a particular test is
important... then the test should be discarded. This ensures that only
important tests be done; in particular, the tests that are important to
participants" I understand that the paragraph was meant to underline the
necessity of selecting tests that participants can/will complete in a timely
fashion. But the formulation is not great: the group agrees on a particular
test is important, but if it is not completed it is not important?

* There are several acronym across the document that could have been expanded
on first use, or used a reference to the definition: PMF, PSNR, PSNR-HVS-M, CQP

* Section 3.7 - "This metric is focused on quality degradation due compression
and rescaling" missing "to"

* Section 5.2 - It would have been good to explicitly write out here what the
parenthesis after each test indicates (resolution, bit depth, etc)

* Section 5.2.2 - "High bit depth" could you quantify more precisely what high
is here?

* Section 5.2.4 and 5.2.5 - Does "old version" mean this should be seen as
deprecated?

(Please keep my address in the To: field if you want to make sure I see any
response to this thread)

Thanks,
Francesca