[Gen-art] Genart last call review of draft-kucherawy-bcp97bis-03

Vijay Gurbani via Datatracker <noreply@ietf.org> Thu, 22 September 2022 15:19 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 15064C1522C6; Thu, 22 Sep 2022 08:19:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Vijay Gurbani via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: draft-kucherawy-bcp97bis.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.16.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <166385997406.13223.8922418885748374623@ietfa.amsl.com>
Reply-To: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Thu, 22 Sep 2022 08:19:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/5ZJZXPwzpBcB3uuIPCiJMLQ6gKU>
Subject: [Gen-art] Genart last call review of draft-kucherawy-bcp97bis-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 22 Sep 2022 15:19:34 -0000

Reviewer: Vijay Gurbani
Review result: Ready with Issues

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-kucherawy-bcp97bis-??
Reviewer: Vijay K. Gurbani
Review Date: 2022-09-22
IETF LC End Date: 2022-10-17
IESG Telechat date: Not scheduled for a telechat

Summary: This document is "Ready with Issues" to be published as a BCP.

Major issues:

Minor issues:
- S1.1, first paragraph: "...subject matter in the RFC, ..."  Here, does the
"RFC" refer to the document being considered for RFC status?  Or does it refer
to the RFC in the normative reference?  I think it is the former, and if so,
perhaps better to say "... subject matter in the RFC under consideration ..."
(or "document under consideration". or even "RFC-to-be").  You hint to this
dilemma later --- in S3, where you define "source" and "target" documents. 
Another option would be to move S3 before S1 and use the "source" and "target"
terminology defined. - S1.1, top of page 4, first bullet ("If a protocol
relies..."): Perhaps better to say "If a RFC-to-be defines a protocol that
relies ..."? Or "If a target document defines a protocol that relies ...".

Nits/editorial comments:
- S4.1: s/At the option of the author/editor/At the discretion of the
author/editor/ - S4.2: s/added to the "Downref Registry"./added to the "Downref
Registry" (Section 7)./

Thanks,

- vijay