IESG Statement On Oppressive or Exclusionary Language

The IESG <iesg@ietf.org> Thu, 23 July 2020 16:35 UTC

Return-Path: <iesg@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CD8693A0BB3; Thu, 23 Jul 2020 09:35:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: IESG Statement On Oppressive or Exclusionary Language
X-Test-IDTracker: no
X-IETF-IDTracker: 7.10.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <159552214576.23902.6025318815034036362@ietfa.amsl.com>
Date: Thu, 23 Jul 2020 09:35:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/plvhcptm1IIJquJkE786ie3Zwxo>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2020 16:35:46 -0000

The IESG believes the use of oppressive or exclusionary language is 
harmful.  Such terminology is present in some IETF documents, including 
standards-track RFCs, and has been for many years. It is at odds with 
our objective of creating an inclusive and respectful environment in the 
IETF, and among readers of our documents.

The IESG realizes that the views of the community about this topic are 
not uniform. Determining an actionable policy regarding problematic 
language is an ongoing process. We wanted to highlight that initial 
discussions about this topic are taking place in the general area (a 
draft [1] is slated for discussion in GENDISPATCH [2] at IETF 108).  
Updating terminology in previously published RFCs is a complex endeavor, 
while making adjustments in the language used in our documents in the 
future should be more straightforward. 

The IESG looks forward to hearing more from the community, engaging in 
those discussions, and helping to develop a framework for handling this 
issue going forward.

[1] https://datatracker.ietf.org/doc/draft-knodel-terminology/
[2] https://www.ietf.org/proceedings/108/agenda/agenda-108-gendispatch-03