Re: Diversity and Inclusiveness in the IETF

Fernando Gont <> Tue, 23 February 2021 08:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3E9343A289E for <>; Tue, 23 Feb 2021 00:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zUrROdT_bSMd for <>; Tue, 23 Feb 2021 00:41:31 -0800 (PST)
Received: from ( [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 629183A289D for <>; Tue, 23 Feb 2021 00:41:29 -0800 (PST)
Received: from [IPv6:2800:810:464:2b9:4897:2501:35bb:1428] (unknown [IPv6:2800:810:464:2b9:4897:2501:35bb:1428]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id E93FC280260; Tue, 23 Feb 2021 08:41:25 +0000 (UTC)
Subject: Re: Diversity and Inclusiveness in the IETF
To: Bron Gondwana <>,
References: <> <>
From: Fernando Gont <>
Message-ID: <>
Date: Tue, 23 Feb 2021 05:34:20 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 23 Feb 2021 08:41:34 -0000

Hello, Bron,

On 23/2/21 01:19, Bron Gondwana wrote:
> Thanks Fernando,
> I would add to this document something about inertia, backwards 
> compatibility and existing dysfunction.

Could you elaborate a bit more on what you mean by each of these?

And, if you could provide examples, and any suggestions on what might be 
done to fix or improve the issue, that would also be nice.

> ... all that to say.  One of the biggest barriers to entry in the IETF 
> is stumbling across an area in which no work is able to progress due to 
> entrenched issues within that area.

Agree on this one.

> And I'm not arguing for "no barriers to entry", because there needs to 
> be a sanity check that we're actually producing high quality 
> specifications, and that our specifications are compatible with each 
> other so the entirety of the IETF's work product is a coherent whole.  
> But it's hard to get started if you don't already have the connections 
> to have your work sponsored by somebody who already knows their way 
> around the IETF's idiosyncrasies.

Also agree on this one.


Fernando Gont
SI6 Networks
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492