Re: British or American spelling in IETF docs

S Moonesamy <sm+ietf@elandsys.com> Tue, 18 August 2026 22:30 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id BCBAF12BF5172 for <ietf@mail2.ietf.org>; Tue, 18 Aug 2026 15:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787092213; bh=oKwl3GFVBkFXHA+ZJbKL9ExBP0m3ADQSEQzKQpeGdmo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pZaCrVW009B5Cx2TM/AXKcfyaSalU7c6B8O5yyPbNbR2U76kMbAtXpEQpAEJZxEcI 5DqcAyTJ8sljs9W5A8UUeGWWraQT+j9bcdGM5IP57QZCS0IJVgAmgyjNZ9Tk+Vm9Wj Rc6czEnFzra+NA/ai2zHdb250i3OFIf7cpUFZWKE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEGGSeELrlU2 for <ietf@mail2.ietf.org>; Tue, 18 Aug 2026 15:30:13 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id E7ED112BF516F for <ietf@ietf.org>; Tue, 18 Aug 2026 15:30:12 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.225.52.222]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 67IMRSik001546 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Aug 2026 15:28:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1787092104; x=1787178504; i=@elandsys.com; bh=oKwl3GFVBkFXHA+ZJbKL9ExBP0m3ADQSEQzKQpeGdmo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZSJ8itPh2k1/k3PC0tcgU+m5NfFMwY8W7AENWDzdThC7jkYHzXHZo4UMn+HwAkIdQ cqFkQc3uHddOjbtrdotJzWqWbhpHxXeS33xgTr9lpq6Z5Y4CFLL8SQWoaA6HtOKncC 63/TUFFeDimhbFpV2IBJy7VfQ5jYbAxYI8+vOBsE=
Message-Id: <6.2.5.6.2.20260818142758.0d0be1e8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 18 Aug 2026 15:26:57 -0700
To: Ken Kubota <ietf@kenkubota.de>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: British or American spelling in IETF docs
In-Reply-To: <B5B990C6-63B4-4326-84D5-1845970F2991@kenkubota.de>
References: <9BC576A20221A4094704F309@PSB> <950516DB-371F-4678-8907-19E68A282CAF@foobar.org> <AFA0585BCCA202087CDB3CEB@PSB> <CAD499eKy89UmFNrnSX5rmoCwBiiaDuVhojJQ+fXVFUtAmNf8zQ@mail.gmail.com> <831033585.3019495.1786695344443@mail.yahoo.com> <B5B990C6-63B4-4326-84D5-1845970F2991@kenkubota.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: ABH7WSKLCGEVRMVHI4N4HMV7ARA7V56D
X-Message-ID-Hash: ABH7WSKLCGEVRMVHI4N4HMV7ARA7V56D
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; header-match-ietf.ietf.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: jordi.palet@consulintel.es
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U1FNqEbsjVircpsB5F4rRujnHxk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

Hi Ken,

The draft was posted around 2018 {1].  The last time the topic of 
spelling was discussed on this mailing list was on or around 
2020.  The question which Jordi Palet asked is related to RFC Editor 
policy.  Anyone interested in changing the policy could do it through 
the RFC Series Working Group (it's not considered as an IETF working group).

One possible fix to a "which spelling" issue would be to use large 
language models.  That topic was recently discussed: 
https://mailarchive.ietf.org/arch/msg/ietf/3VaBJ6pEdhtkpOtnZYA_HcVHejU/ 
The (possible) fix would cause other problems (John Klensin hinted 
about that somewhere in the "spelling" thread).

Regards,
S. Moonesamy

1. https://mailarchive.ietf.org/arch/msg/ietf/wZLsfyrwpT9ydLNwLqB0bfMaGUU/