Re: Communications - Re: Ombudsteam update

Michael StJohns <> Mon, 28 January 2019 22:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9AF07130EE9 for <>; Mon, 28 Jan 2019 14:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 VREY3OBcrWrH for <>; Mon, 28 Jan 2019 14:53:15 -0800 (PST)
Received: from ( [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 043E2130EE6 for <>; Mon, 28 Jan 2019 14:53:14 -0800 (PST)
Received: from ([]) by with ESMTP id o7YZgrqnDaPJWoFmEgvVAw; Mon, 28 Jan 2019 22:53:14 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=q20161114; t=1548715994; bh=+tPexqYauyEpT8oCHq7cyp/ZvfGQAyNOh6GWax40R0A=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=FASBhTo2FOE6hFyN4R9OmsYFx0onr1oE2lZ9/nhq1fBHItS3RxvGcCcbiMYPkXEB7 4xx+3p+M9RUORwoPs2P566KLhxTt9pCdyjWmOdxhGNKoICcNMDEe22NE5A75SmT6ty yU8ZLU/UcE7zm5J3DZ8csU4bmrava4JGAE8Q6aftna/jFXz6Otdwm5FIuq+RpNnza6 Cb7++TUIeMMplU5Pn4fzKCbiBxjPw0UcYx/8AcOg1RBBwWMxkU3ftVNgYrQr6lOuU3 WrV/9ZQyRD5c8WgDzvEf3yPF9YvO+r52TyGjirshofJksDED+K6R3C8hWQAo5WkFHS BBtJ7P5uaPBFg==
Received: from [IPv6:2601:152:4400:4013:d857:756d:caef:f499] ([IPv6:2601:152:4400:4013:d857:756d:caef:f499]) by with ESMTPSA id oFmDgSOlgEfQFoFmDg1GLr; Mon, 28 Jan 2019 22:53:13 +0000
X-Xfinity-VMeta: sc=0;st=legit
Subject: Re: Communications - Re: Ombudsteam update
References: <> <> <> <> <> <> <> <> <> <> <>
From: Michael StJohns <>
Message-ID: <>
Date: Mon, 28 Jan 2019 17:53:10 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
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: Mon, 28 Jan 2019 22:53:17 -0000

On 1/28/2019 4:56 PM, wrote:
> Communicating with Americans is often hard work for non-Americans...

And then there's "Communicating with Americans is often hard work for 
Americans" and  "Communicating with IETF participants is often hard work 
for everyone including IETF participants".

Just saying.

Regardless, colloquial English of both the British and American 
varieties tends to provide loan words into lots of other language and 
cultural contexts.  It's difficult for a English  (both native and 
non-native) speaker to sometimes know where the limits are and to what 
extent they apply to any given person.  I'd like to suggest that we 
don't make too much of this, avoid "words of the week", but not worry 
about terms we (community collectively) have been using for years.  And 
add a sentence to the Tao that suggests "when in doubt, google it or ask 
the speaker"  which I had to do when a recent random encounter with a 
Brit had me googling for the meaning of "have a butcher's" and not 
understanding why he was pointing at a magazine cover.

All technical communities have their own languages - that's just the 
reality.  Learning to become fluent in that language is just the cost of 
doing business.  Staying fluent is also part of the cost (cf the 
discussions on git/github/etc).

Later, Mike