Re: Wow, we're famous, was WG Review: Effective Terminology in IETF Documents (term)

Colin Perkins <> Wed, 14 April 2021 22:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E45943A2191 for <>; Wed, 14 Apr 2021 15:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Status: No, score=-4.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id car-GLJzX7oQ for <>; Wed, 14 Apr 2021 15:00:26 -0700 (PDT)
Received: from ( [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 796F73A219E for <>; Wed, 14 Apr 2021 15:00:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=mythic-beasts-k1; h=To:Date:From:Subject; bh=aTh5+uqjixSgOU6Wq5XTUrNOWhZsY1Taboq6qCHfJjE=; b=MG/2ogK8kejxOebe58NIrnKi52 XSDUDWK5lYJ5vTSt0CuvB+XBk/OFMbOqWK1cXUw8Mlq89oxDB6cO+4/OBNuU9EqHK8Lau+N+OwpSv i4nLlk6ehyZsWUugLvogFjaFMbWbFmU452KKRERjFnUzR/7t8Sd3++pkwBa2KbPWm/tAmnL2Q2Ypm e9DYD4HjlssQ32WkZOsF7GhjAOAaKcwmLhDbaJD73Te4kleSujJqBL6KQOI2DK7rQeOmx98q95wWx Kq2LHLMriCjIkLx7xwyjoE7pH03nhVkm51z0jZD+Uo1m8rX2bx6gCAS9iyZfPCXm/Jj6bHGEm2Ulo 0aXkPFmw==;
Received: from [] (port=48401 helo=[]) by with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <>) id 1lWnYc-0004Ni-Hy; Wed, 14 Apr 2021 23:00:23 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Subject: Re: Wow, we're famous, was WG Review: Effective Terminology in IETF Documents (term)
From: Colin Perkins <>
In-Reply-To: <20210414184131.GP9612@localhost>
Date: Wed, 14 Apr 2021 23:00:18 +0100
Cc: The IETF List <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <20210413200535.BF29C72D2919@ary.qy> <> <> <> <> <20210414184131.GP9612@localhost>
To: Nico Williams <>
X-Mailer: Apple Mail (2.3445.104.17)
X-BlackCat-Spam-Score: 4
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: Wed, 14 Apr 2021 22:00:32 -0000

> On 14 Apr 2021, at 19:41, Nico Williams <> wrote:
> On Wed, Apr 14, 2021 at 07:33:45PM +0200, Eliot Lear wrote:
>> Here is what I take from those comments, Bron:
>> There is indeed no societal consensus on how terminology is should be
>> used.
>> We simply cannot stop at terminology when we address inclusiveness.
>> It’s a VERY small component in an overall strategy.
>> What does this mean to the IETF?  I don’t think it means “stop doing
>> TERM”.  Rather I think it means that we should work on the other
>> aspects.  We should make it easy and fun to be here.  And mostly it is
>> fun (of course I’m biased), but sometimes it’s not easy.
> Well, if we paid attention to practical proposals by participants who
> most have a need for them, we'd have IETF sponsors and/or ISOC providing
> sponsorships to participants from economically disadvantaged backgrounds
> or countries.
> E.g., see Fernando's commentary.
> But you know, the response to that so far has been CRICKETS.

We’ve had such a programme for many years for IRTF ANRW, and had a travel grant programme ready to announce for some other areas of IRTF, but then the pandemic hit, and travel stopped. We’re happy to accept future sponsors for such grants, to broaden the scope of the programme, for when the in-person meetings resume. 

Jason has mentioned activities on the IETF side. 

Colin Perkins