Re: To "lose the argument in the WG"

S Moonesamy <sm+ietf@elandsys.com> Sun, 19 February 2017 00:03 UTC

Return-Path: <sm@elandsys.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 22E4B1296A2 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:03:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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=opendkim.org header.b=uEsihd5T; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=iDmXogaz
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 vWj4s3MPDC2w for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:03:17 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E9AA2129401 for <ietf@ietf.org>; Sat, 18 Feb 2017 16:03:16 -0800 (PST)
Received: from sm-THINK.elandsys.com ([197.226.55.251]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v1J02ubG019412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Feb 2017 16:03:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1487462591; x=1487548991; bh=N1SbMYEHtTJAlsierYTA4Oqat2nuyTQoTU3O9SIFcn4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uEsihd5T04Hq0ZiFzihW5KAuXopdkoKrjMMTHp7priO7rkDPhzYxClTnM8I391VbY flVpjeBg2aMBIz/UpJFhHxXDtuCmFbJWRQL5/RHx8WgQyBsUEY6kdLOpsGbmdRcALh WES0XHdbiDJg3YTOsUyHh3MFHSlVYpqDcvQ6hRig=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1487462591; x=1487548991; i=@elandsys.com; bh=N1SbMYEHtTJAlsierYTA4Oqat2nuyTQoTU3O9SIFcn4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iDmXogazVi5BqSwraQ67g/1m4feHR7Monj6nKhr+L0mDuckM+EOW8Rb6kD7zKuBrG oSFt87ehsOI+pYn+LrpXxJvlxb0O8886V/MCcKfpkPsObpuTsH6owpZS71P4v0PoBZ +MGmQAkI3FAEF23os+JkYF+iDiBKvdKY8GZHPHQI=
Message-Id: <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 18 Feb 2017 15:59:06 -0800
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: To "lose the argument in the WG"
In-Reply-To: <AB7BB4019CE95D16CA7B0B8D@PSB>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x0BXeZFIzY94aMLda4aRtD62jzo>
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 00:03:18 -0000

Hi John,
At 07:26 AM 2/18/2017, John C Klensin wrote:
>It can be something else as well.  We could be more careful
>about our vocabulary (but probably won't be), but consider a
>scenario in which someone, even someone who is quite expert in a
>given topic, looks at a WG charter and likely leadership and
>participants and says to herself "This is unlikely to produce
>anything harmful or go off into the weeds or is sufficiently
>narrowly scoped to not pose a general problem.  I do not have
>unlimited time to spend on IETF work, and my knowledge and
>skills are needed elsewhere".  That is an "I don't have time"
>scenario, but it is a vote of confidence in those actively
>participating in the WG (and the WG Chair and AD involved) not
>abusive of them.  If it then turns out that the WG, in her
>opinion, does go off into the weeds, produces someone harmful to
>the Internet or other work, or even produces something outside
>the scope of the charter, I think the community needs her to
>speak up and that any attempt to dismiss the concerns on the
>grounds of "you should have participated more and earlier" are
>not only abusive but pose a danger to the IETF.

There are two message from Ted and Pete about "abusive" [1][2].  Pete 
made an interesting comment: "The process can't depend on a single 
participant's time."  In the above-mentioned scenario, and assuming 
that it is IETF work which I am supposed to do, I would take the Last 
Call comments into consideration.

>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?

>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.

Regards,
S. Moonesamy

1. https://www.ietf.org/mail-archive/web/ietf/current/msg101332.html
2. https://www.ietf.org/mail-archive/web/ietf/current/msg101335.html