Re: [Gendispatch] Diversity and Inclusiveness in the IETF

Dominique Lazanski <> Tue, 23 February 2021 08:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 468A33A0E34 for <>; Tue, 23 Feb 2021 00:50:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2NHOltcLfK_v for <>; Tue, 23 Feb 2021 00:50:10 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F21133A28B2 for <>; Tue, 23 Feb 2021 00:50:09 -0800 (PST)
Received: by with SMTP id v17so1037738ljj.9 for <>; Tue, 23 Feb 2021 00:50:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WJHpUoP20Emfsn7RmHLV6CQq9AzQGefhZekvDsEVJKg=; b=IenIPCype7fB+FwKMKvd8HOcUnSCJerkMKw/mpnFq+Ej+spFdUZhIM8UzPS24lwlb+ jEdZlE3S3JZnE0CGO2FxMFbkmmnuyKSVoGIoufQt7b8gUo/P28QX4hBdHbiD2DqVy5mV jLW/mpMFHSnBSV8JvEJUj724HHTluQ1G2duPsx6THx/MLg4kH1QBgKdPIBYn0Y5sx1Em eAjPs2VwkZth7rTYTdUrlyMLUf1UCJ+aJzW9ZCUnKV5zR3dod5cHZdLkFggkXuAnHDmk VqOcHj+FvNdPq07xepE4hZalKB4tue2yLx58FKcEJXnrANKiBCVDV/VT+m456RI13LgS ezhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WJHpUoP20Emfsn7RmHLV6CQq9AzQGefhZekvDsEVJKg=; b=D/oWrTqE7atpO5BOaQY8c5E/fWXMcCYCO/hqowx7VGItGlcU757FYfEgGNwjDnoIPF v/fpLkTcsIg1h3XNcefQ2DoQrhQDswuwtCd4QSITKtF0V4btF39OPXh5I/3k/L+jys81 PLSEpdpA+ZAX7z7RjVPM4LOG6rLy+lf+OHlxCDxC4kuQt8ZJZ5haAgkHr1x8Ao+1jOUd +03/c/mQ71/FjuYJCb8MBRywIpDk0nMR36dz+rivZhfhl/2oGIfVGNguc4Ufdx7Ly4tu fyMTR8EE0AKFJ91FXHATwq+a5zWATUTFwwJVaLwLuBvdWJEv+aJmuth5ABQkpfqQIF4m 9mYw==
X-Gm-Message-State: AOAM533IC2xbvh7jdQJmv0qjBHgPDSiHQGDVcysEI6UpOltwB7T7sYP/ 6U1nJ+EyM6MDmQWbpUvgekROnA==
X-Google-Smtp-Source: ABdhPJxFMrkQ6t5Ktsg8Gp7DzxC8pbQBHW58ukNgd83Gnz++ImayRQZh6FiWXfTYCCgxHlqJ0BD5Hg==
X-Received: by 2002:a2e:90cf:: with SMTP id o15mr5449400ljg.218.1614070207780; Tue, 23 Feb 2021 00:50:07 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id i8sm1880561lfe.158.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Feb 2021 00:50:07 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
Subject: Re: [Gendispatch] Diversity and Inclusiveness in the IETF
From: Dominique Lazanski <>
In-Reply-To: <>
Date: Tue, 23 Feb 2021 09:50:06 +0100
Cc: Bron Gondwana <>,,
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: Fernando Gont <>
X-Mailer: Apple Mail (2.3654.
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:50:17 -0000

> On 23 Feb 2021, at 09:40, Fernando Gont <> wrote:
> Hello, Dominique,
> On 23/2/21 05:18, Dominique Lazanski wrote:
>> I would support Bron’s experience and also say that there are several other barriers to entry that I’ve found. One is different approaches to topics than the mainstream IETF approach held by most IETF attendees. I am thinking about privacy/encryption, for example.
> Could you elaborate a bit more on this one? e.g., some example (so that we can understand better what you mean)... and if you can think of anything that might be done to improve things in this respect, that would also be nice.

Sure! This is purely my experience, but I have found it challenging (and hostile) to engage in controversial topics which don’t have consensus. I think encryption is the most obvious one and consolidation another. I don’t want to dwell on the issues, but would rather suggest solutions. I think it would be great to organise open sessions of an hour just on these topics focused specifically on having difficult and challenging conversations only about one topic. Obviously we have open IAB, plenary and etc, but a focused, short meeting would be one idea.

>> But the other big barrier to entry is the draft upload tools. For a new person attending for the first time the tools are a relic of 1990 of thereabouts and can be confusing and difficult.
> FWIW, we have already started to work on a revision of the draft (working copy at:, and this is what we currently have in the Section 8.2 of the upcoming rev:
> ---- cut here ----
> 8.2.  Difficulty in Authoring and Submitting Internet-Drafts
>   There are so many formatting rules that an Internet-Draft (and
>   eventually an RFC) needs to comply to, that in practice the only
>   reasonable way create and submit an Internet-Draft is via the set of
>   tools available at: . Tools such as xml2rfc
>   are of a lot of help to produce documents that comply with the
>   Internet-Draft formatting rules -- but its error messages might
>   result cryptic to the unexperienced user.
>   The number of tools has expanded so much that they probably deserve
>   their own guidelines.  And existing guidelines such as
>   [ID-Guidelines] should probably be updated with the assumption that
>   Internet-Drafts will be produced with the set of available tools.
>      This means that e.g. it becomes less important to the Internet-
>      Draft author what formatting rules a document needs to comply to,
>      since the existing tools will guarantee such compliance.  On the
>      other hand, an author may benefit from guidelines on how to use
>      the set of available tools.
> ---- cut here ----
> Is there anything you'd suggest adding to it?

This is great news! I will definitely go to git and add a few things.

>> In any case, I shall join the gendispatch group to discuss further!
> Please do, but also feel free to discuss it here if you wish, too.
> Thanks a lot!
> Regards,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail:
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492