| Internet-Draft | Terminology | February 2022 |
| Knodel & ten Oever | Expires 13 August 2022 | [Page] |
This document argues for more inclusive language conventions sometimes used by RFC authors and the RFC Production Centre in Internet-Drafts that are work in progress, and in new RFCs that may be published in any of the RFC series, in order to foster greater knowledge transfer and improve diversity of participation in the IETF.¶
This document represents the opinion of the authors and does not have IETF consensus.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 13 August 2022.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
According to [RFC7322], "The ultimate goal of the RFC publication process is to produce documents that are readable, clear, consistent, and reasonably uniform," and one function of the RFC Editor is to "[c]orrect larger content/clarity issues; flag any unclear passages for author review." Documents that are published as RFCs are first worked on as Internet-Drafts.¶
Given the importance of communication between people developing RFCs, Internet-Drafts (I-Ds), and related documents, it is worth considering the effects of terminology that has been identified as exclusionary. This document argues that certain obviously exclusionary terms should be avoided and replaced with alternatives. We propose nothing more than care in the choice of language just as care is taken in defining standards and protocols themselves.¶
The point of the piece is to lift up the voices of those who choose not to engage because of harmful dynamics such as exclusionary language.¶
This document presents arguments for why exclusionary terms should be avoided in Internet-Drafts and RFCs and, as an exercise, describes the problems introduced by some specific terms and why their proposed alternatives improve technical documentation. The example terms discussed in this document are "master-slave" and "whitelist-blacklist". There is a section on additional considerations and general action points to address future RFCs and I-Ds. Lastly, a summary of recommendations is presented.¶
This analysis is presented as the authors' commentary on the IETF process and does not represent the opinion of the IETF.¶
According to the work of Heather Brodie Graves from 1993, "One goal of the application of rhetorical theory in the technical communication classroom is to assess the appropriateness of particular terms and to evaluate whether these terms will facilitate or hinder the readers' understanding of the technical material" [BrodieGravesGraves]. This implies that in order to effectively communicate the content of I-Ds and RFCs to all readers, it is important for Authors to consider the kinds of terms or language conventions that may inadvertently get in the way of effective communication. She continues, "Complex and subtle configurations of sexist, racist, or ethnocentric language use in technical documents can derail or interfere with readers' ability and desire to comprehend and follow important information."¶
Indeed, problems of language are problems of everyday speech. Racist and sexist language is rampant and similarly counter-productive in other sectors, notably social work [Burgest]. The terms "master-slave" (treated in detail below) are present in other realms of technology, notably, "Automotive clutch and brake systems, clocks, flip-flop circuits, computer drives, and radio transmitters" [Eglash].¶
However, it is not too late for these terms to be replaced with alternative metaphors that are more accurate, clearer, less distracting, and that do not offend their readers. Language matters and metaphors matter. Indeed, metaphors can be incredibly useful devices to make more human the complex technical concepts presented in RFCs. Metaphors should not be avoided, but rather taken seriously. Renowned linguist George Lakoff argued in 1980 that the ubiquitous use of metaphors in our everyday speech indicates a fundamental instinct to "structure our most basic understandings of experience" [Lakoff]. Metaphors structure relationships, and they frame possibilities and impossibilities [Wyatt].¶
The role of language is to describe the world and maintain social relationships. The way in which the world, people, and institutions are described provides a particular ordering to the world. This ordering function of language is what makes it a potential instrument for power and control. The understanding of power in relation to language, as used in this document, is the way in which language reflects, influences, and shapes social relations.¶
Like Graves, this document recognises the monumental challenge of addressing linguistics and power, and attempts to promote awareness that may lead to eventual wide-spread change and suggests first steps for actions that may remedy the inadvertent use of undesirable terms. To that end, the list below is a tersely written set of IETF-specific arguments as to why the RFC Editor should be encouraged to remedy issues with respect to exclusionary language and metaphors:¶
This document does not try to prescribe terminology shifts for any and all language that could be deemed exclusionary. Instead we illustrate an overall approach through the following two most eggregious examples of specific term pairs "master-slave" and "white-blacklist" and the rationale for the use of suggested alternatives. Suggested actions for handling additional considerations are presented in a subsequent section.¶
Master-slave is an offensive and exclusionary metaphor that will and should never become fully detached from history. Aside from being unprofessional and exclusionary it stifled the participation of students whom Eglash interviewed for his research. He asks: "If the master-slave metaphor affected these tough-minded engineers who had the gumption to make it through a technical career back in the days when they may have been the only black persons in their classes, what impact might it have on black students who are debating whether or not to enter science and technology careers at all?" [Eglash]¶
Aside from the arguably most important reason outlined above, these terms are becoming less used and therefore increasingly less compatible as more communities move away from their use (e.g. [NIST], [Python], [Drupal], [Github] and [Django] ). The usage of 'master' and 'slave' in hardware and software has been halted by the Los Angeles County Office of Affirmative Action, the Django community, the Python community and several other programming languages. This was done because the language is offensive and hurts people in the community [Django2]. Root operator Internet Systems Consortium recognised that the terms 'master' and 'slave' are very value-laden and responded to multiple requests from users by offering an inoffensive alternative [ISC].¶
In addition to being inappropriate, the master-slave metaphor is both technically and historically inaccurate. For instance, in DNS the 'slave' is able to refuse zone transfers on the ground that they are malformed. The metaphor is incorrect historically given the most recent centuries during which "the role of the master was to abdicate and the role of the slave was to revolt" [McClelland]. Yet "slavery" is not just a historic term: whereas freedom from slavery is a human-rights issue [UDHR], slavery continues to exist in the present day [Wikipedia]. Furthermore, this term set wasn't revived until recently, after WWII, and after many of the technologies that adopted it were already in use with different terminology [Eglash].¶
Ultimately master-slave is a poor choice since:¶
Eglash's research calls into question the accuracy of the master-slave metaphor. To find alternatives to master-slave, one can look to many existing implementations of technology. There are also many other relationships that can be used as metaphors. An alternative should be chosen based on the pairing that is most clear in context:¶
The metaphorical use of white-black to connote good-evil is exclusive. While master-slave might seem like a more egregious example of racism, white-black is arguably worse because it is more pervasive and therefore more insidious. While recent headlines have decried the technical community's use of master-slave, there is far less discussion about white-black despite its importance. There is even a name for this pervasive language pitfall: the association of white with good and black with evil is known as the "bad is black effect" [Grewal].¶
Indeed, there is an entire book on the subject, written by renowned authority on race, Frantz Fanon. In his book "Black Skin, White Masks," Fanon makes several persuasive arguments that standard language encodes subconscious in-group, out-group preferences [Fanon].¶
In the case of blacklist-whitelist in the technical documentation of I-Ds and RFCs, it is entirely a term of art and an arbitrary metaphorical construct with no technical merit. There are scientific uses of black that are related to light - black holes are black because light cannot escape them. Blacklist-whitelist is not a metaphor for lightness or darkness, it is a good-evil metaphor and therefore this trope has significant impact on how people are seen and treated. As we've seen with metaphors, its use is pervasive and, though not necessarily conscious, perceptions do get promulgated through culture and repetition.¶
As with master-slave, we save our technical argument for last, referencing and presenting first the reasons for the use of non-offensive, alternative terminology for the sake of our humanity. Indeed, our technical argument is succinct: Why use a metaphor when a direct description is both succinct and clear? There can be absolutely no ambiguity if one uses the terms, as suggested below, allow-block rather than white-black.¶
There are alternatives to this terminology set that vastly improve clarity because they are not even metaphors, they're descriptions. The alternatives proposed here say exactly what they mean.¶
As described in the preceding sections, the language used in technical documentation, like all written text, creates and reinforces expectations and stereotypes. We propose nothing more than additional care in the choice of language just as care is taken in defining standards and protocols themselves. The two examples provided above are not the only cases of exclusionary language to be avoided, and many more can be collected. We use this section to broaden the context of other offensive and exclusionary terminologies to encompass additional concerns, why spotting and eradicating problematic terminologies is a valid endeavour for authors and editors of technical documentation and how this might be systematised.¶
There are many other metaphors present in technical documentation that are "terms of art" but that have no technical basis whatsoever. If any of these metaphors is offensive there is no excuse for its continued use. A term like "man-in-the-middle" is not technically useful. It is not a standard term, not as clear as its alternative "on-path attacker", and should therefore be avoided. When presented with the opportunity to employ the use of metaphors or to unthinkingly repeat terms of art that connote gender or race, Authors should simply find a better way to explain themselves. A fun read on the politics of colloquial speech by George Orwell should dissuade any Author from using tired explanatory metaphors [Orwell].¶
The unnecessary use of gendered pronouns is a sexist practise that is common but easy to spot and replace. Without a neutral singular pronoun, "he" is assumed as the default singular pronoun when the gender of the person is unknown or ambiguous. However, that has changed, and it is now widely accepted that "they" can be used as a neutral singular pronoun. Since it is unlikely that all implementers and infrastructure operators are of any particular gender, "he" should never be used to refer to a person in I-Ds and RFCs. An Author who uses male examples sets male-ness as a standard.¶
Besides race and gender, our world is full of metaphors rooted in oppression, ableism, and colonialism. Militarised metaphors are also a pervasive problem in language, perhaps even more so in technical communities because of the historical and actual relationship between technology and war. Authors of RFCs need to be especially on their guard against all manner of metaphors that may carry unwanted overtones.¶
While it is not our intention to be exhaustive we hope to have made a persuasive case for authors and editors to pay attention to the finer details of metaphor, and the ways power is replicated in technical documentation unless detailed attention is paid. The example terms above "master-slave" and "blacklist-whitelist" are already less common. If the IETF community has learned anything from the debate over the use of these terms, and this document, it is that language matters to us deeply as members of society and as engineers. And because language, and society, change over time, we must approach future concerns with some degree of dispassion when the arguments presented in the first section can be clearly applied.¶
There is harm in protracted discussion about the validity of the experience of IETF participants with exclusionary terminology because it invalidates this people's experiences. Behavior that, some of which labeled IESG as racist and disrepectful and therefore removed [White1] [White2] surfaced in the community as a result of this larger debate among technologists pushed away participants and observers [Conger]. This illustrates the need to, as Graves is cited above as saying, continue to raise awareness within our community for eventual, lasting change on the continued front of struggle against the racists amongst us. Yet we recommend a living stylesheet, rather than repeated RFCs, be used as a mechanism for monitoring exclusionary language in IETF documents [inclusiveterminology].¶
It is there that we welcome additional examples of terminology that might be avoided through more awareness and thoughtfulness.¶
To summarise, we have listed some concrete action points that can be taken by Editors, reviewers and Authors, both present and future as they develop and publish Internet-Drafts and new RFCs.¶
The authors think that document authors should:¶
The authors think that the RFC editor should:¶
For more information on this topic we suggest reading:¶
Ford, Heather., Wajcman, Judy. 2017. "'Anyone can edit', not everyone does: Wikipedia and the gender gap" Social Studies of Science. ISSN 0306-3127¶
Grant, Barbara M. 2008. "Master-slave dialogues in humanities supervision" Arts and Humanities in Higher Education, Volume: 7 issue: 1, page(s): 9-27 https://doi.org/10.1177/1474022207084880¶
Miller, Carolyn, R. 1979. "A Humanistic Rationale for Technical Writing" College English, Vol. 40, No. 6, pp. 610-617¶
Security is dependent on a wide range of actors that are implementing technical documentation. Therefore it is crucial that language is clear, and understood by all that need to implement this documentation. Correct and inclusive language is therefore conducive for secure implementations of technical documentation.¶
Changing terminology that is common in use can be leveraged as security risk because it may lead people to misunderstand what is being talked about. It is therefore recommended that when language is changed because of the reasons described in this document, it should be documented as such.¶
This document has no actions for IANA.¶