Re: To "lose the argument in the WG"

John C Klensin <john-ietf@jck.com> Sun, 19 February 2017 03:56 UTC

Return-Path: <john-ietf@jck.com>
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 F2510128B44 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 D_W-knLX70B4 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:56:52 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A698129407 for <ietf@ietf.org>; Sat, 18 Feb 2017 19:56:52 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cfIc7-0009TJ-Ox; Sat, 18 Feb 2017 22:56:43 -0500
Date: Sat, 18 Feb 2017 22:56:38 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
Subject: Re: To "lose the argument in the WG"
Message-ID: <55E03EE38894AF3FBC97DE8F@JcK-HP5.jck.com>
In-Reply-To: <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BE5L2MIfqgiFfotFIW1Ul8YxHKo>
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 19 Feb 2017 03:56:54 -0000


--On Saturday, February 18, 2017 3:59 PM -0800 S Moonesamy
<sm+ietf@elandsys.com> wrote:

>...
>> The only solution to that sort of time conflict is for the
>> IETF to become much less ambitious about how much work can be
>> done in parallel, possibly by constraining the number of WGs.
>> The latter has been proposed a few times, but has gone
>> nowhere, I think in part because even its advocates want
>> whatever work they want to do next to be treated
>> exceptionally.
> 
> Isn't the issue about the volume of WG discussions which an
> Area Director has to manage instead of the number of WGs?

There are a number of dimensions of the problem.  One could
debate their ranking by importance, but I'm not sure the
exercise would be productive.  I would encourage you to find the
earlier I-Ds (there were at least two different models) and
discussions before starting over again.

>> I also note that a Last Call complaint (or appeal, or
>> suggestion of intent to appeal) on the grounds that a
>> document on which an IETF Last Call has been initiated
>> exceeds the scope of the relevant WG Charter has ever gone
>> anywhere.  It isn't clear to me how cases like that should be
>> handled because the work has typically been completed and
>> there is no obvious basis for sending the document back to
>> the WG for technical corrections. The community should
>> probably fire ADs who let that sort of thing happen, but
>> (without guessing at what discussions occur within the
>> Nomcom) there is little evidence of community willingness to
>> do that either.
> 
> It is up to the Working Group Chair and Responsible Area
> Director to assess whether the WG output falls within the WG
> Charter.

Yes, as long as you remember that they are supposed to be
representing the will of the community and accountable to it.
Neither WG Chairs nor ADs have any other source of authority.
The difficulty with your statement above is that it can be read
to imply that there are no constraints one, or appeals from, the
decisions.  That is not true or, more specifically, if one wants
a healthy IETF that produces credible work, it better not be.

best,
   john