<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.knodel-terminology" target="https://datatracker.ietf.org/doc/html/draft-knodel-terminology-00">
   <front>
      <title>Terminology, Power and Oppressive Language</title>
      <author initials="M." surname="Knodel" fullname="Mallory Knodel">
         <organization>ARTICLE 19</organization>
      </author>
      <author initials="N." surname="ten Oever" fullname="Niels ten Oever">
         <organization>University of Amsterdam</organization>
      </author>
      <date month="October" day="22" year="2018" />
      <abstract>
	 <t>   This document argues for and describes alternatives that shift
   specific language conventions used by RFC Authors and RFC Editors to
   avoid oppressive terminology in the technical documentation of the
   RFC series.  Specifically, this document details two sets of terms
   that are normalised on the technical level but oppressive on a
   societal level.  First, arguments are presented for why any
   oppressive terms should be avoided by the IETF/IRTF.  Second, problem
   statements for both sets of terms are presented and alternatives are
   proposed.  There is a third section on additional considerations and
   general action points to address the RFC series, past and future.
   Lastly, a summary of recommendations is presented.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-knodel-terminology-00" />
   
</reference>
