Re: IESG Statement On Oppressive or Exclusionary Language

Michael StJohns <mstjohns@comcast.net> Thu, 23 July 2020 18:52 UTC

Return-Path: <mstjohns@comcast.net>
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 78E263A0CBC for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2020 11:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 Tlk-1JwzGzi9 for <ietf@ietfa.amsl.com>; Thu, 23 Jul 2020 11:52:54 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64B1B3A0CBB for <ietf@ietf.org>; Thu, 23 Jul 2020 11:52:54 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id ygIPjEVTueol4ygKqjZcwJ; Thu, 23 Jul 2020 18:52:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1595530372; bh=fZ/kY9ZOs50pmYmgjExD4hNBr4IQMxYM8IaCe/Ka8+8=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=pv5/xMyj7raEMgruvANBYBQowCwgmAI98gSt/Q/ds6xnot2KFwI3bo8ptpE11Gkgd rAPd2IusyP8nyOcDIsBNjO0T3uVMUp78OAHM0QA41lnnO+gEK2Cqcm2c+7M1tomvxV 5F03Rmnn6Pj3kwnHpvbHf3TLF5472NNarsq0LhyGnVBMnLBNeREaWbaunZDLKOHdf/ qkBRWgIfMnDolQqRumnOO2ZfMXiimXyBDH/9vANsrXZuDRTRkCTJeaMMveASgwwFqV J1rc/s2Wz8p3GC0BjMHJIqtGIrkrlyDSYI+6oD0ExTYs1iBTs+Odo+3zwSvDvHViCJ WIQMfdqRPmweg==
Received: from [192.168.1.115] ([71.163.188.115]) by resomta-ch2-09v.sys.comcast.net with ESMTPSA id ygKcjN4X6dKV2ygKhj53Qk; Thu, 23 Jul 2020 18:52:49 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduiedrhedugddufeegucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefoihgthhgrvghlucfuthflohhhnhhsuceomhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtqeenucggtffrrghtthgvrhhnpeefieevjeehueduvdfhveelgfelffegheejiefhhfevtdekkeelfeehhfejledtgeenucfkphepjedurdduieefrddukeekrdduudehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurdduudehngdpihhnvghtpeejuddrudeifedrudekkedrudduhedpmhgrihhlfhhrohhmpehmshhtjhhohhhnshestghomhgtrghsthdrnhgvthdprhgtphhtthhopehivghtfhesihgvthhfrdhorhhgpdhrtghpthhtohepjhhmhhesjhhovghlhhgrlhhpvghrnhdrtghomh
X-Xfinity-VMeta: sc=0.00;st=legit
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: IETF <ietf@ietf.org>
References: <159552214576.23902.6025318815034036362@ietfa.amsl.com> <7990c17d-4ba7-f295-de04-9ab3fe17ded3@comcast.net> <CA+9kkMBofZ-1XHn+4t5tfxyyhomt+=UUtnxi2JU7XWnR1gESqQ@mail.gmail.com> <43540be1-6b82-04b9-c1f2-81c09b54de50@comcast.net> <CA+9kkMD+WHARqDNWA4z0zUgn7LeA63fkpSUDPCcF=G+O6-bG7w@mail.gmail.com> <a2cb91eb-0ad1-0238-e4e3-e3a1621ae3cb@comcast.net> <69fc9773-8970-5db9-48b6-b04bdb934412@joelhalpern.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <cbd6a687-792c-9bd1-9dee-2143c0c41725@comcast.net>
Date: Thu, 23 Jul 2020 14:52:38 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <69fc9773-8970-5db9-48b6-b04bdb934412@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Iq3Bzdy9pZ3XFYp5tX_4SzSaMYM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 23 Jul 2020 18:52:56 -0000

On 7/23/2020 2:37 PM, Joel M. Halpern wrote:
> It seems to me that the first place to do this is in I-Ds, even if we 
> do not have strict enforcement mechanisms.  And if it is to be done in 
> I-Ds, it is up to the individual streams to do so.  Having the IETF 
> discuss doing this for IETF i_Ds seems a really effective and sensible 
> starting point.
>
> Yours,
> Joel

Do you expect the IAB and IRSG and the ISE to also do an evolution like 
this?   For example: Should the use of "master key"be banned in CFRG 
documents?  Isn't that a lot of redundant work?

When you say "IETF discuss", I'm assuming you have a WG in mind to do 
this work?  Or are we going to stand up yet another WG?  Or is the IESG 
going to decide on its own perhaps with some community input?

Why would you not let the RSE or the Temp (John) manage the process of 
updating the acceptable phrasings in the RFC series? Isn't that directly 
in their job description?

Later, Mike