To preface, I agree with what you're getting at, and will add my own thoughts below. But first I would like to clarify that my earlier statement obliquely referred to specific cases of people having withdrawn from IETF participation because the technical problems they were trying to highlight were not only not being taken seriously in official venues, but were prompting ridicule and personal attacks from that vocal minority who could not conceive of any legitimate position in opposition to IETF mantras. I'm not going to get any more specific here because specific cases are not the point of this thread, and there's already been too much drift.
Now, getting back to your reply:
The IETF classically expresses its values through its consensus process in an emergent way: when a normative RFC is published in the IETF stream, it (let's assume for the sake of argument) represents the consensus of the participants at the time, and so whatever values are implied by the normative language become part of the overall set of values that the IETF expresses. The non-historic normative documents are effectively a codex from which our shared values are drawn.
Position statements come at this from the other direction. They establish an orthodox view within the IETF, effectively putting up a sign saying "If you disagree, maybe you ought not come here." That is far more exclusionary than any loaded technical jargon. By preemptively excluding those who disagree with the prevailing orthodoxy, we create an echo chamber and eventually come to assume that there are no reasonable divergent viewpoints. For the IESG to arrogate to itself the power to set the bounds of appropriate discourse on a non-technical matter on which many reasonable people can and do disagree seems a dangerous precedent.
Fundamentally, what this comes down to is that the IETF is a bottom-up organization. Not top-down. The IESG is there to serve the participants, as a well of expertise and a means for shepherding consensus for a coherent technical vision from a cacophony of voices, continuously changing and often wildly out of tune with each other. The IETF is not simply a factory for a vision chosen by the IESG.
On 7/25/20 10:58 AM, Kyle Rose wrote:
The IETF does have an inclusion problem, but I suspect it has very little to do with problematic technical jargon and a lot more to do with the all-too-frequent bullying, mocking, and dismissal that seem to be standard operating procedure for a small but vocal minority of the community.That statement could be credibly read in at least two ways:
1. the small but vocal minority of the community that claims the authority to bully people whom that small but vocal minority sees as being on the fringes
2. the small but vocal minority of the community that is on the fringes whom are seen as bullying others merely because they have different opinions (which they express even though they are different, and don't readily cave in to pressure from others)
Even in this particular discussion, which to me looks like it has been relatively respectful, there are signs that it really bothers some people that other people have different opinions, as if everyone should somehow agree with a vocal minority of people merely because that minority believes it has good intentions.
To me, part of what inclusion looks like is respectful tolerance of differing views even though some of those views make some people uncomfortable. I want to suggest that people being immediately comfortable isn't an appropriate goal, because it always makes some people uncomfortable that there are multiple valid perspectives on a subject. Instead, the community needs to cultivate a willingness to be uncomfortable when it is done in the service of accommodating different views and building rough consensus.
Keith
