[Gen-art] Genart last call review of draft-rsalz-2028bis-05

Vijay Gurbani via Datatracker <noreply@ietf.org> Fri, 18 February 2022 21:35 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 5A5F63A14C5; Fri, 18 Feb 2022 13:35:24 -0800 (PST)
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-rsalz-2028bis.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164522012430.26178.14440393326150748380@ietfa.amsl.com>
Reply-To: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Fri, 18 Feb 2022 13:35:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/aRwixzsxR3hfSbpstJvO2CpDoIk>
Subject: [Gen-art] Genart last call review of draft-rsalz-2028bis-05
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: Fri, 18 Feb 2022 21:35:25 -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-rsalz-2028bis-05
Reviewer: Vijay K. Gurbani
Review Date: 2022-02-18
IETF LC End Date: 2022-03-07
IESG Telechat date: 2022-03-10

Summary: Ready with one major issue and one nit.

Major issues: 1
- S3.7, first paragraph: I don't think it is accurate to characterize the 
 IETF as focusing on "shorter-term issues of engineering and standards
 making."  If the contrast is being made to the "longer-term research issues" 
 of IRTF, then the comparison is flawed.  Research can be short term and
 engineering decisions can have impact over the long term; it is not our
 place to characterize research as long term and engineering as short term.
 Who arbitrates what constitutes long term and short term?  Can a short-term 
 engineering idea in the IETF have as much impact as a long running IRTF 
 group?  I suspect the answer is yes.  For these reasons, I am not sure we 
 should consider ourselves to be an arbiter of these things.  

 I believe that first paragraph will read just as well if both the qualifiers
 "longer-term" and "shorter-term" were taken out, and I would make a case
 that we should do so.

Minor issues:

Nits/editorial comments:
- S3.5: Does "RFC Advisory Board (RSAB)" expand to "RFC Series Advisory Board"?
 The "Series" is missing; in the previous line RSWG expands to "RFC Series
 Working Group", so I expect a symmetry.