Re: Tracking resolution of DISCUSSes

Jari Arkko <jari.arkko@piuha.net> Mon, 15 January 2007 16:40 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6Usc-00082C-8g; Mon, 15 Jan 2007 11:40:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6Usa-000825-6J for ietf@ietf.org; Mon, 15 Jan 2007 11:40:16 -0500
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6UsX-00082b-84 for ietf@ietf.org; Mon, 15 Jan 2007 11:40:16 -0500
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EAA32198767; Mon, 15 Jan 2007 18:40:09 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 91B2D198765; Mon, 15 Jan 2007 18:40:09 +0200 (EET)
Message-ID: <45ABAE69.7070806@piuha.net>
Date: Mon, 15 Jan 2007 18:40:09 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: Brian E Carpenter <brc@zurich.ibm.com>
References: <03dc01c73116$33fabb60$6a01a8c0@china.huawei.com><073d01c731aa$f04e4090$0a23fea9@your029b8cecfe><87ejq7f8ek.fsf@latte.josefsson.org><2F04242A9E159580681BB631@[192.168.1.108]> <45A21835.1080000@zurich.ibm.com><08e201c73314$a4669fe0$0a23fea9@your029b8cecfe><756322479FBFFBAA515267FC@sirius.fac.cs.cmu.edu> <B507AC4A-81AF-4331-A6DC-CF37B5F120BB@cisco.com> <005401c73706$957765f0$0a23fea9@your029b8cecfe> <45A9E3C9.9070909@zurich.ibm.com> <01b001c738b1$43e77e80$0a23fea9@your029b8cecfe> <45AB9671.3080808@zurich.ibm.com>
In-Reply-To: <45AB9671.3080808@zurich.ibm.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Adrian Farrel <adrian@olddog.co.uk>, Jeffrey Hutzelman <jhutz@cmu.edu>, ietf@ietf.org, Fred Baker <fred@cisco.com>
Subject: Re: Tracking resolution of DISCUSSes
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

> Why would we do this for technical typos and other things that
> are essentially trivial? I'd expect an AD to enter WG discussion
> when raising fundamental issues, but not for straightforward
> points.
>
> This is what should, IMHO, be the PROTO shepherd's job to decide
> about, as well as consolidating issues when more than one AD
> (or other reviewer) finds the same thing.
What Brian is saying here is that there is a fair amount
of noise in some of these cases. A fairly typical situation
is that an AD raises a concern by placing a Discuss
but then in the telechat we talk about whether under
the circumstances that is really an issue. Quite often
we end up clearing the Discuss. In any case, it could
be premature to start a thread in the WG mailing list
on "this protocol must do X" before we are sure that
we actually want to demand that.

A good shepherd manages this and takes the
discussion to the WG when its ready. But in case
they forget and/or to assist them, I wouldn't mind
automatic posting of the IESG review results a
a day or two after the telechat to the WG list.

Jari


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf