Re: [Gendispatch] draft charter text: terminology-related WG

Eric Rescorla <ekr@rtfm.com> Sun, 14 February 2021 00:23 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA2C3A11AF for <gendispatch@ietfa.amsl.com>; Sat, 13 Feb 2021 16:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 vK4d-4cbvfA8 for <gendispatch@ietfa.amsl.com>; Sat, 13 Feb 2021 16:23:41 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D681E3A11AB for <gendispatch@ietf.org>; Sat, 13 Feb 2021 16:23:40 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id x1so3533573ljj.11 for <gendispatch@ietf.org>; Sat, 13 Feb 2021 16:23:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+Et7oYpZOOs1X03irvcLE1hH3YQHHatHz+rvLEmBGVI=; b=NHPldz/jE4wHqTzSA+iqN7NTPBK6AqpWHSRR6RZ7aT8N8VIr4ACtzuSs48gaUZwakT T94EjHhfN8n+GM4oqAeXYOWZ+X5HxJEoo5S0QXCLiNbybMdEg7X9wRf67JPTTHvbZMAh zNIZPj1PzoqSjiJmA0/uYhQK3jaY04acNobu25zkd5utqpUFiv+K4C+anNbJUbFcz1MA ilCFbgZcuETrLeJVnnjTFxA3z36SlT8fkmjr7RKV928iMoarU7+uAKcd+uFRa1YpiLnI kVETjpMZFVgOIc0lsPXdSCa+PrpMnEXTO9x/eFe0El9uq/5oiBtEVnj9/slm+wzck3IR PWFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+Et7oYpZOOs1X03irvcLE1hH3YQHHatHz+rvLEmBGVI=; b=mipiX8SkXizR4gKnHlXnoJ53pdlnygb1ycLbOv51sMQn33eUozXRFbgFQ2XeXPje7S 3TxDZ1Q17Yt6xRWoqcViEiwUOZwumcFhkHolufnexze5dczQFQce7FKMg4Uw66cW8x4T iMVZvc1eJ9PkFcYFAIu6nwr5DH0nYirp2CBfkBgIJYKwg8+uV3HJ0i+VsE+7U+kkaStL TpeuP0Vt0C+3x9i2lL4/UzNsPgirTgnHcsi73Pz3LuIyP1wubZ1cg2DjUvCclo7GVT8i v6wPLGl7JaN99+kz1442gGaOkWDNe9yKCt33+qcdm2+rlC2RTjGpY+LRb6DVdkXiH5qT seOg==
X-Gm-Message-State: AOAM530w5Slaox/fGIARYKCLeAoaiZmOQ4lfpZouwUagd8QjLSt9Cu5z RjGq5lunswTpYIvznbY41swaGqPqpRdBH9yvZw7N8w==
X-Google-Smtp-Source: ABdhPJwSVqg6JLKN2siKEkH4LES19ZPtg/h6Y5fKsoqmlQs3iw4JcM6vTBIiNIkj9Z3cEtQHyrVJcChXcvfIzTnCdgg=
X-Received: by 2002:a2e:7f04:: with SMTP id a4mr5170357ljd.3.1613262217330; Sat, 13 Feb 2021 16:23:37 -0800 (PST)
MIME-Version: 1.0
References: <20210212205351.27E4B6DDB49D@ary.qy> <3b4ea13c-0743-c882-7fc0-1fe7288f6d07@gont.com.ar> <a2e6c65e-076a-8875-c374-56c825105a6c@cs.tcd.ie> <CAGVFjM+sgyRDhuVYvkPC1XbH4yL-Q_Qpbs_naZpS3D3ApPO92A@mail.gmail.com> <772fa23e-4170-82d2-8ee2-caececd83904@si6networks.com> <E53D1060-5F25-4495-8C97-6A0F0EFD2117@mnot.net> <47ff90d4-b960-f159-c064-1f963c717c31@network-heretics.com> <7E75BBC0-3266-4980-9676-1384B7D0D565@mnot.net>
In-Reply-To: <7E75BBC0-3266-4980-9676-1384B7D0D565@mnot.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 13 Feb 2021 16:23:01 -0800
Message-ID: <CABcZeBMstAaoMFjNaS6FyKphLbyH0z+Xvb5kyXX_nr9jaucoGw@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Keith Moore <moore@network-heretics.com>, "vittorio.bertola@open-xchange.com" <vittorio.bertola@open-xchange.com>, Mallory Knodel <mknodel@cdt.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>, John Levine <johnl@taugh.com>, Fernando Gont <fernando@gont.com.ar>, Fernando Gont <fgont@si6networks.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="00000000000064d5b905bb40e1b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/qLzz_MMvds-LhuEZMRQqGY-Sycc>
Subject: Re: [Gendispatch] draft charter text: terminology-related WG
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Feb 2021 00:23:43 -0000

On Sat, Feb 13, 2021 at 4:12 PM Mark Nottingham <mnot@mnot.net> wrote:

>
>
> > On 14 Feb 2021, at 10:56 am, Keith Moore <moore@network-heretics.com>
> wrote:
> >
> > On 2/13/21 5:52 PM, Mark Nottingham wrote:
> >
> >> This issue is settled in much of tech, so we have strong cowpaths to
> pave. As a result, the amount of energy that it will take to create
> language guidelines is almost completely determined by how much energy
> people put into trying to stop it.
> >>
> >> If people have legitimate reasons as to why we shouldn't do this,
> that's one thing; 'our energy is better spent elsewhere' is not one of them.
> >
> > To me this proposal looks like a DoS attack against actually increasing
> inclusion in IETF.   Why actually do the hard work when we can fill in a
> check box and pretend we have virtue?
> >
> > If we want to publish a document that talks about exclusionary language,
> let's just Last Call what we have once or twice (but no more than that) and
> be done with it.   I don't think a WG is going to improve the document as
> much as community-wide Last Calls, and IMO a WG on this topic has a lot
> more potential to do harm than good.
>
> I think that would work if we didn't have a small group of people who
> vocally and continually insert ever-shifting arguments against this. Under
> those conditions, it's normal practice for a WG to be formed; AD-sponsored
> is always tenuous, and not really built for contentious issues.
>

I concur with Mark. In addition, I note that many of the issues people
are raising now werealso raised in the gendispatch discussion
(
https://mailarchive.ietf.org/arch/msg/gendispatch/6Od2aX-uiYGdYCKZqfvrOHHtY58/
),so
we're going over old ground.

   After extensive discussion, there were objections by the end of the
   first meeting to making the output of this work AD-sponsored, with
   a preference for a quick-spin-up WG. In the second meeting, there
   was more ambivalence as to whether AD-sponsored or quick-spin WG
   would be better. Putting this together, we think the rough
   consensus within the meetings was to have a quick-spin WG.

   ...

   There was rough support in both meetings for recommending a broader
   discussion and resulting document on inclusivity beyond the
   terminology, but there were many concerns for how to structure such
   work in a WG and have it be successful. Several suggestions were
   made to have the IAB sponsor such work as part of their program on
   "Diversity, Inclusion, and Growth". The thought was that perhaps a
   discussion there could generate a path forward for IETF work.

I think it's clear that a significant number of people [0] think it's
useful to do some sort of WG to work on terminology, certainly enough
to meet the threshold of interest for starting a WG. If people think
that that's a bad idea, then that's certainly a reasonable objection
to raise. OTOH, if people just think that there is something more
important to do, then it seems to me that that shouldn't prevent
WG formation.

-Ekr


[0] Full disclosure, I also believe we should do something here
and that a WG is a reasonable approach.