[Terminology] Fwd: IESG Statement on Inclusive Language
Lars Eggert <lars@eggert.org> Tue, 11 May 2021 17:56 UTC
Return-Path: <lars@eggert.org>
X-Original-To: terminology@ietfa.amsl.com
Delivered-To: terminology@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BDE3A2088 for <terminology@ietfa.amsl.com>; Tue, 11 May 2021 10:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 DzN44bFGTrFe for <terminology@ietfa.amsl.com>; Tue, 11 May 2021 10:55:55 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 1B6233A2086 for <terminology@ietf.org>; Tue, 11 May 2021 10:55:55 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:1574:cd7a:7f:13e3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 983E360035E for <terminology@ietf.org>; Tue, 11 May 2021 20:55:44 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1620755744; bh=Jo4Sd6/c4w12d3r6Hzdr8bR2FURGheFFCFsERVglQ2g=; h=From:Subject:References:To:Date; b=PIMkQkTrEGFIKXK0P7VcM4Ue4SzQFXxrsU0QF95nhDOo/U9fEu4aPbzC/vy29d/MP aoDrbrfM62hjfAJ0tKKFASFysVUybHt1lsh8a19LSbBROSBSnUumrNryJEf5P/ma+v XBt85CqYuSfjTQyCFq+1vp2opam5HWuU+W2qHlrI=
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_134DE358-1B44-486F-90B6-43AF41A274F8"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Message-Id: <41D24B56-4373-448D-A321-F6DE3FFECBE2@eggert.org>
References: <162074136396.22917.13424778517979369806@ietfa.amsl.com>
To: terminology@ietf.org
Date: Tue, 11 May 2021 20:55:44 +0300
X-Mailer: Apple Mail (2.3654.80.0.2.43)
X-MailScanner-ID: 983E360035E.A2D28
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/terminology/NSa_W44xyPiZCTFkiNJ6EbC_lg0>
Subject: [Terminology] Fwd: IESG Statement on Inclusive Language
X-BeenThere: terminology@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Effective Terminology in IETF Documents <terminology.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/terminology>, <mailto:terminology-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/terminology/>
List-Post: <mailto:terminology@ietf.org>
List-Help: <mailto:terminology-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/terminology>, <mailto:terminology-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 May 2021 17:56:01 -0000
FYI > Begin forwarded message: > > From: IESG Secretary <iesg-secretary@ietf.org> > Subject: IESG Statement on Inclusive Language > Date: May 11, 2021 at 16:56:04 GMT+3 > To: "IETF Announcement List" <ietf-announce@ietf.org> > Cc: iesg@ietf.org > Reply-To: support@ietf.org > > IESG Statement on Inclusive Language > > Online: <https://www.ietf.org/about/groups/iesg/statements/on-inclusive-language> > > The mission of the IETF as specified in [BCP95] is to produce high > quality, relevant technical documents that influence the way people > design, use, and manage the Internet as a global resource. > Contributions to the IETF, including Internet-Drafts and RFCs, are > most understandable and effective when they use terminology that is > clear, precise, and widely accessible to readers from varying > backgrounds and cultures. > > The IESG hence encourages IETF participants to use the guidance in > [NISTIR8366] when making contributions to the IETF. Although developed > for use within the US National Institute of Standards and Technology > (NIST), the IETF community expressed strong support for the sentiment > that the guidance on inclusive language in [NISTIR8366] is suitable > for the IETF as well [1,2]. Using the same terminology as other > standards organizations and industry initiatives also contributes to > overall coherence in the industry. > > The IESG also encourages the owners of the various RFC streams and the > RFC Editor to consider whether they could issue similar guidance to > their authors and contributors. > > The IESG invites the community to continue using the > terminology@ietf.org mailing list for any future discussion of this > topic. > > [BCP95] Alvestrand, H., A Mission Statement for the IETF, BCP 95, > RFC 3935, DOI 10.17487/RFC3935, October 2004, > https://www.rfc-editor.org/info/rfc3935. > > [1] https://mailarchive.ietf.org/arch/msg/terminology/w_OoUaF6GVIzQIMoLUlrc8xq_rk > > [2] https://mailarchive.ietf.org/arch/msg/terminology/8mrwmUBT5GSDTT-GFZlM2kjknGo > > [NISTIR8366] Guidance for NIST Staff on Using Inclusive Language in > Documentary Standards, National Institute of Standards and > Technology (NIST) Interagency or Internal Report 8366 > (NISTIR 8366), April 2021, > https://doi.org/10.6028/NIST.IR.8366. > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce
- [Terminology] Fwd: IESG Statement on Inclusive La… Lars Eggert
- Re: [Terminology] Fwd: IESG Statement on Inclusiv… Bron Gondwana