Re: [Last-Call] OT: change BCP 83 [Re: Last Call: BCP 83 PR-Action Against Dan Harkins]

Keith Moore <> Mon, 03 October 2022 21:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AE1E6C152591 for <>; Mon, 3 Oct 2022 14:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 EvTvQrwS4Fja for <>; Mon, 3 Oct 2022 14:05:35 -0700 (PDT)
Received: from ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id AD17FC14F73D for <>; Mon, 3 Oct 2022 14:05:35 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id 88A593200937 for <>; Mon, 3 Oct 2022 17:05:34 -0400 (EDT)
Received: from mailfrontend1 ([]) by compute3.internal (MEProxy); Mon, 03 Oct 2022 17:05:34 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1664831134; x=1664917534; bh=/ pU8ag0xvrr9qD5/FA6MqF1yXqS741/EVXjijT6DcmM=; b=UuMFw/9+/ZoWJ/CO1 93Gveo8TmK50QZBjUDxSGtsu20psKlgQWshbWRBDevOsC5XR+N5Pls8E62sqLe+5 Dlw1r6jmC/5EiGwRTnAAsycUcvZtEbdz3hSUo5ZxgpB6ucBu6WH6u9Kh1GJ4+oeA 6+bxPBjSHxAjoZM4S/v9Ajq0cKIobhns3plmOKEYjzYNaxiI42tVd1XmTKreaHEN jT+3DpAOK9z8IOtVX6e3j6G7L5Ad7mynIKXHoBaFLs4P8shI1pMH/jmTXAEbuBPW fqbStwJSQ7vfXjb9Ha2g434Xozs2qaNU+3bnI9zyolU6PWyQVawwnH5BP+20HwzH NrhfA==
X-ME-Sender: <xms:nk47Y90FZQc0nmHdw3wcUj1TkqLdAPxS3KGpGzySqsfGzq1XYdQTSQ> <xme:nk47Y0Ep-j5_D1Sdf1FNlQVsOlmSY15m7jRGkfJxwL018pY2_KkkbhCt74vI7F_yI F6uxfPcEGB1Og>
X-ME-Received: <xmr:nk47Y95O4O69G7gwNnywEyAPkkAmmI-sNSfCxSQxCzg6ZzVANHvuMlUH2xdQ-ADfNEJr06msU7GugSA-8L9UCkPyRR5bLh9zLDnjvcE7ZAQv6pSR11lGJg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeehledgudehiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepfedtvdelie ejveekjefhueduheeviefhjeefvdfgudfhfffhudduudefgefgteevnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifoh hrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:nk47Y6106LnJRLsmF1fHp7uKBM0EN74AR90AkZYWpurXwHknK8WXqQ> <xmx:nk47YwHgjNIr4bk4utT7PQVRMSySCmtSGrttlke940SYWydFaB1Wmw> <xmx:nk47Y7_iDhfH_c7VbamCXBZDtcEeihPw9kW3T0PZWZg-HSnnqMYmkg> <xmx:nk47Y0Rv61pLvJgFLa1KpEIjCTNiXGOVHUdF3fUEF8NbQ78T8lVXag>
Feedback-ID: i5d8c41f0:Fastmail
Received: by (Postfix) with ESMTPA for <>; Mon, 3 Oct 2022 17:05:33 -0400 (EDT)
Message-ID: <>
Date: Mon, 03 Oct 2022 17:05:33 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
References: <> <> <> <> <> <> <>
From: Keith Moore <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [Last-Call] OT: change BCP 83 [Re: Last Call: BCP 83 PR-Action Against Dan Harkins]
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 03 Oct 2022 21:05:40 -0000

On 10/3/22 16:00, Brian E Carpenter wrote:

> On 04-Oct-22 08:04, Toerless Eckert wrote:
> ...
>> - There is no clear explicit list of what is in evidence, instead we 
>> are asked to find that
>>    evidence ourselves from long mailing lists, not knowing how far 
>> back judgements where made.
> Huh? The Last Call messages includes an explicit list of example 
> messages, which in my opinion are sufficient on their own.
In my opinion, the list is nowhere nearly sufficient to support the 
charges they are making.   The general refusal to specifically say what 
was wrong or what rule it violated are one of the huge problems with 
this PR IMO.
>>    and drafts that have been completely removed, so we can not vet 
>> those either (now).
> Consider yourself fortunate. Those of us who read them at the time 
> were mainly glad to see them removed.

I objected to their removal.  I said at the time and still consider it 
an inappropriate action on the part of IESG, one that increased the 
toxicity of IETF.   I will concede that the Swift references (and also 
Orwell, if I recall correctly) were probably lost on those who weren't 
schooled in English-language literature.

>> - To me, this "discussion" looks a lot like a misguided public trial 
>> with an unclear separation between
>>    accusers and judges, but without any clear assigned defender.
> If you think the BCP83 process has that defect, see the above Subject 
> header. As far as I can tell, the IESG has followed the current 
> process correctly.
As far as can tell, they have indeed followed BCP83 correctly. That 
they've followed the process doesn't mean it was a responsible or 
prudent choice.   I'm increasingly convinced from this that BCP83 needs 
a drastic rewrite.

I doubt that BCP83 envisioned the extremely intolerant environment that 
IETF is today.  IETF was, as best I recall, much more tolerant in those 
days, and I expect that BCP83 was intended for far more abusive posts 
than anything we've seen from Dan.
>> IMHO all that makes those process steps overall more hurtfull to the 
>> reputation of the IETF than helpfull,
> I don't agree. I think it's better to have the debate on the record 
> than behind closed doors.

Transparency is essential, and I think a closed door proceeding would do 
even more harm.