Re: To "lose the argument in the WG"

John C Klensin <john-ietf@jck.com> Sat, 18 February 2017 15:26 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 8BCDE129532 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 07:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 tJ2E5MO-mooF for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 07:26:45 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69F9812952F for <ietf@ietf.org>; Sat, 18 Feb 2017 07:26:45 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cf6u7-0003bx-IQ; Sat, 18 Feb 2017 10:26:31 -0500
Date: Sat, 18 Feb 2017 10:26:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, John Leslie <john@jlc.net>, dcrocker@bbiw.net, ietf@ietf.org
Subject: Re: To "lose the argument in the WG"
Message-ID: <AB7BB4019CE95D16CA7B0B8D@PSB>
In-Reply-To: <6.2.5.6.2.20170218010720.0b845c18@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>
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
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JnmJE_xMfobxRNcpWRnf2N3EWfk>
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: Sat, 18 Feb 2017 15:26:47 -0000


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

>...
> At 09:05 AM 2/14/2017, Dave Crocker wrote:
>> To Ted's point, indulging folk who 'did not have time' to 
>> participate earlier is frankly abusive of all those who did.
> 
> It is a matter of how the comment is framed.  For example, a
> comment along the lines of "I don't know whether the WG
> considered this issue" is not a problem as it should be
> possible to point to the resolution (re. issue tracker,
> decision posted to the WG mailing list, etc.)

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.

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.

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.

      john