Re: dealing with AD reviews in the week before the IESG call
Benjamin Kaduk <kaduk@mit.edu> Mon, 10 August 2020 22:33 UTC
Return-Path: <kaduk@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55623A0DC0; Mon, 10 Aug 2020 15:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 v6TPwUvx0DSG; Mon, 10 Aug 2020 15:33:51 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 2A1303A0DBD; Mon, 10 Aug 2020 15:33:50 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07AMXk0C020437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 10 Aug 2020 18:33:48 -0400
Date: Mon, 10 Aug 2020 15:33:45 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: dealing with AD reviews in the week before the IESG call
Message-ID: <20200810223345.GU92412@kduck.mit.edu>
References: <12164.1596936888@localhost> <CALaySJJUb5jNN1MJiABGGPkagTnJv88n6pnmTmJZjcHd39ayqw@mail.gmail.com> <CAHw9_iJWy76XWwtxW6-LxBbFooW3Akp52u=kPVQ5AXuGeaX82Q@mail.gmail.com> <MN2PR11MB4366E0C527C06D7E93A41AF3B5440@MN2PR11MB4366.namprd11.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <MN2PR11MB4366E0C527C06D7E93A41AF3B5440@MN2PR11MB4366.namprd11.prod.outlook.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RiblaAhhCb3YwkV05kQcgCaScWc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2020 22:33:53 -0000
On Mon, Aug 10, 2020 at 02:39:51PM +0000, Rob Wilton (rwilton) wrote: > > > > -----Original Message----- > > From: iesg <iesg-bounces@ietf.org> On Behalf Of Warren Kumari > > Sent: 09 August 2020 17:33 > > To: Barry Leiba <barryleiba@computer.org> > > Cc: IESG <iesg@ietf.org>; Michael Richardson <mcr+ietf@sandelman.ca>; IETF > > discussion list <ietf@ietf.org>; Benjamin Kaduk <kaduk@mit.edu> > > Subject: Re: dealing with AD reviews in the week before the IESG call > > > > On Sun, Aug 9, 2020 at 11:29 AM Barry Leiba <barryleiba@computer.org> > > wrote: > > > > > > Speaking only for myself: I would always prefer to be reviewing the > > > latest version available at the time I'm reviewing, and I don't care > > > whether it's not the same version that another AD reviewed, nor that I > > > might start reviewing one version and see another posted before I'm > > > done. > > > > > > In other words, I'd rather have updates posted when the judgment of > > > the authors, working groups, and sponsoring ADs says they should be. > > > > > > > Me too! Update early, update often. If I comment on an older version, > > and the issues have already been addressed, thats perfectly fine / > > preferred... > [RW] > > Agreed. As long as the authors accept that some reviews/comments may be against older versions, then responsive authors fixing the text as the reviews come in generally seems like a good thing. If an AD is reviewing a document closer to the telechat deadline, then generally any improvements that have already been made to the text normally makes the document easier/quicker to review. I'm of a similar opinion as Warren, Barry, and Rob -- I'm happy to see fixes get posted in a new I-D so that I can review the "latest and greatest" that's available. I do make a note of which version I'm reviewing, at least in my local notes, so that I have an easier time tracking things down if a new version is posted before I'm done. That said, you can always ask the AD responsible for the document in question whether you should upload a new version; they should have a pretty good idea for the general sense of the IESG at that time. -Ben
- dealing with AD reviews in the week before the IE… Michael Richardson
- Re: dealing with AD reviews in the week before th… Barry Leiba
- Re: dealing with AD reviews in the week before th… Warren Kumari
- RE: dealing with AD reviews in the week before th… Rob Wilton (rwilton)
- Re: dealing with AD reviews in the week before th… Benjamin Kaduk
- Re: dealing with AD reviews in the week before th… Murray S. Kucherawy