Re: To "lose the argument in the WG"
Dave Crocker <dhc@dcrocker.net> Tue, 14 February 2017 05:07 UTC
Return-Path: <dhc@dcrocker.net>
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 234441295EF for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level:
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
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 R0yMkCCKq1Hh for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:07:27 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 812371295DE for <ietf@ietf.org>; Mon, 13 Feb 2017 21:07:27 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1E59935005701 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 13 Feb 2017 21:09:09 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1487048949; bh=ngOBBFEBYHeRXcgN77u3kqxpPWJsBOvbA/nhXQxTlvE=; h=Subject:To:References:From:Reply-To:Date:In-Reply-To:From; b=K1GemZITwLawlc1BZ3XHmGPfVf2LwsoE0MCctbcwcOkahDqo55iSyE8ON9UNWPWXT GGr2R+VTIJELuwS4gcDzgnwzI+P6DYZo+tauc4kAGqytUr7mKJwYWFSeBSDfxkKa9+ xZRBwMNH4j7Ep3bJ58tUXGTe+thjijUZU6JPihQk=
Subject: Re: To "lose the argument in the WG"
To: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>
Date: Mon, 13 Feb 2017 21:07:17 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bT_Y-P7gO6q0H_s3jQ3CPs541uQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Tue, 14 Feb 2017 05:07:28 -0000
On 2/13/2017 8:50 PM, Pete Resnick wrote: > The WG participant who felt that the functionality should be in-scope > and is perfectly within bounds to make the case that the functionality > is somehow necessary during Last Call. The chair and/or AD should > summarize why they judged the functionality to be out of scope. Others > in the community might want to take up the argument and explain why it > should be added. This sounds like reasonable theory, but is actually rather destructive practice. It takes the position that Last Call is acceptable to use as a form of appeals process, where folk who have been working on the topic for an extended time have to defend their choices to a collection of other folk who are new to the topic and are, therefore, making snap judgements. While, yes, there will be times that the new folk see something new or better, that's not the usual occurrence. The usual occurrence is that folk who are experienced with the topic and are tired from the extended effort have to rehash their work and defend it to folk who have not done their homework. Either working groups are where the work really does get done or they aren't. The burden of having to worry about and deal with a larger, less-involved community being frankly encouraged to second-guess the folk who have actual skin in the game, is an example of what makes the formality of IETF process onerous. Last Call should not require a working group to be subject to random demands to defend itself. It should be for independent reviews that see something the working group missed. Missed is different from "we had a choice and we made it". If a fresh reviewer really does do their homework and really does present a good case for making a different decision, that's fine. But it also is quite different than supporting the re-hashing exercise that occurrs when an existing wg participant expresses dissatisfaction with a decision made during normal wg processes. d/ ps. Pete's other point was about a claim that an issue didn't really get settled and needs further review. That's quite a different case. Maybe it's worthy for LC discussion. Maybe it isn't. Dunno. pps. There's at least one case where I chose to attempt to use LC as a kind of appeals process, since I deemed the wg process to have been significantly flawed, including the cognizant AD. Like all good rules, there need to be some exceptions thoughtfully permitted, though of course my effort in this example of an exception bore no fruit... -- Dave Crocker Brandenburg InternetWorking bbiw.net
- To "lose the argument in the WG" Pete Resnick
- Re: To "lose the argument in the WG" Dave Crocker
- Re: To "lose the argument in the WG" Ted Lemon
- Re: To "lose the argument in the WG" Pete Resnick
- Re: To "lose the argument in the WG" Mark Andrews
- Re: To "lose the argument in the WG" Yoav Nir
- Re: To "lose the argument in the WG" John C Klensin
- Re: To "lose the argument in the WG" Stewart Bryant
- Re: To "lose the argument in the WG" Ted Lemon
- Re: To "lose the argument in the WG" Dave Crocker
- Re: To "lose the argument in the WG" Joel M. Halpern
- Re: To "lose the argument in the WG" Dave Crocker
- Re: To "lose the argument in the WG" John Levine
- Re: To "lose the argument in the WG" Pete Resnick
- Re: To "lose the argument in the WG" Pete Resnick
- Re: To "lose the argument in the WG" Brian E Carpenter
- Re: To "lose the argument in the WG" Ted Lemon
- Re: To "lose the argument in the WG" John C Klensin
- Re: To "lose the argument in the WG" Pete Resnick
- Re: To "lose the argument in the WG" Ted Lemon
- Re: To "lose the argument in the WG" Randall Gellens
- Re: To "lose the argument in the WG" Joel M. Halpern
- Re: To "lose the argument in the WG" George Michaelson
- Re: To "lose the argument in the WG" John Leslie
- Re: To "lose the argument in the WG" Yoav Nir
- Re: To "lose the argument in the WG" S Moonesamy
- Re: To "lose the argument in the WG" John C Klensin
- Re: To "lose the argument in the WG" S Moonesamy
- Re: To "lose the argument in the WG" Ted Lemon
- Re: To "lose the argument in the WG" Ted Lemon
- Re: To "lose the argument in the WG" John C Klensin
- Why do we have working group charters (was: To "l… S Moonesamy
- Re: Why do we have working group charters (was: T… Ted Lemon
- Re: Why do we have working group charters (was: T… John C Klensin
- Re: To "lose the argument in the WG" Joe Touch