[Gendispatch] Meetings summary
Pete Resnick <resnick@episteme.net> Tue, 13 October 2020 20:17 UTC
Return-Path: <resnick@episteme.net>
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 310833A1102 for <gendispatch@ietfa.amsl.com>; Tue, 13 Oct 2020 13:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 3qIkOVOc8a7Z for <gendispatch@ietfa.amsl.com>; Tue, 13 Oct 2020 13:17:43 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E94F3A045E for <gendispatch@ietf.org>; Tue, 13 Oct 2020 13:17:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 49ACBC13DD96 for <gendispatch@ietf.org>; Tue, 13 Oct 2020 15:17:30 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cswpQ0Ev-0bS for <gendispatch@ietf.org>; Tue, 13 Oct 2020 15:17:28 -0500 (CDT)
Received: from [172.16.1.10] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id D4196C13DD88 for <gendispatch@ietf.org>; Tue, 13 Oct 2020 15:17:28 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: gendispatch@ietf.org
Date: Tue, 13 Oct 2020 15:17:28 -0500
X-Mailer: MailMate (1.13.2r5726)
Message-ID: <B1075198-D4F5-498B-B16B-3081A9B07DDD@episteme.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/6Od2aX-uiYGdYCKZqfvrOHHtY58>
Subject: [Gendispatch] Meetings summary
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: Tue, 13 Oct 2020 20:17:45 -0000
Here is a summary of what your chairs have concluded is the result of the two virtual interim meetings we held on the issue of terminology in IETF technical work generally, and draft-knodel-terminology, draft-gondwana-effective-terminology, and draft-moore-exclusionary-language specifically. We'll allow a couple of weeks for discussion of these conclusions on the list before we report back to Alissa the group's final recommendation on how we think this ought to be dispatched. -- First, we find that there was rough support in both meetings for creating a document containing recommendations on terminology to use in technical work, and that such a document should be Informational status. However, there were concerns about describing motivations in such a document for fear of "ratholing"[1], and so any significant discussion of motivations ought to be avoided. 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. We found a clear outcome in both meetings that draft-knodel has too much controversial discussion to be the basis of a document for the above mentioned quick-spin WG on terminology. There was rough support for recommending the use of draft-gondwana as a starting point. -- We are looking for a two important things in the discussion here on the list. First, if you have read the minutes of the meetings and believe that something was not discussed or that a point was missed by the people at the meeting that would change the conclusions in the above, please speak up. Second, if you think we misinterpreted the outcome of the discussion from the meetings and therefore should have come to a different conclusion, please let us know. Of course, you are also welcome to ask questions about how we came to our summary. However, we don't need to hear "+1" or "I agree with the above" (we'll assume you do if you say nothing) and importantly we do not want to re-litigate discussions that happened during the meeting unless you have new information to contribute. Simply restating arguments isn't going to change the outcome. So please do re-read the minutes of the meetings before posting. Thanks for everyone's participation, Pete and Francesca [1] In case you haven't seen the IETF use of that term before: Interminable and often useless or off-topic discussion, as if to fall into a messy pit made by a rat.
- [Gendispatch] Meetings summary Pete Resnick
- Re: [Gendispatch] Meetings summary Salz, Rich
- Re: [Gendispatch] Meetings summary Mallory Knodel
- Re: [Gendispatch] Meetings summary Dan Harkins
- Re: [Gendispatch] Meetings summary Jay Daley
- Re: [Gendispatch] Meetings summary Brian E Carpenter
- Re: [Gendispatch] Meetings summary Pete Resnick
- Re: [Gendispatch] Meetings summary Francesca Palombini
- Re: [Gendispatch] Meetings summary Mary Barnes
- Re: [Gendispatch] Meetings summary Jay Daley
- Re: [Gendispatch] Meetings summary Dan Harkins
- Re: [Gendispatch] Meetings summary Francesca Palombini
- Re: [Gendispatch] Meetings summary Keith Moore
- Re: [Gendispatch] Meetings summary Keith Moore
- Re: [Gendispatch] Meetings summary Pete Resnick
- Re: [Gendispatch] Meetings summary Bron Gondwana
- Re: [Gendispatch] Meetings summary Eliot Lear
- [Gendispatch] The actual issues (was Re: Meetings… Vittorio Bertola
- Re: [Gendispatch] Meetings summary Andrew Campling
- Re: [Gendispatch] Meetings summary Christian Huitema
- Re: [Gendispatch] Meetings summary Brian E Carpenter
- Re: [Gendispatch] Meetings summary Mallory Knodel
- Re: [Gendispatch] Meetings summary Dan Harkins
- Re: [Gendispatch] what are we doing here, Meeting… John Levine
- Re: [Gendispatch] Meetings summary Bron Gondwana
- Re: [Gendispatch] Meetings summary Salz, Rich
- Re: [Gendispatch] what are we doing here, Meeting… Mallory Knodel
- Re: [Gendispatch] Meetings summary Dan Harkins
- Re: [Gendispatch] Meetings summary Francesca Palombini
- Re: [Gendispatch] Meetings summary Francesca Palombini