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

Keith Moore <> Mon, 03 October 2022 01:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B7BDEC14F73E for <>; Sun, 2 Oct 2022 18:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Status: No, score=-2.608 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, 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 wvf2mgOlCerZ for <>; Sun, 2 Oct 2022 18:14:12 -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 BB99CC14F736 for <>; Sun, 2 Oct 2022 18:14:12 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id 026D132005C1; Sun, 2 Oct 2022 21:14:11 -0400 (EDT)
Received: from mailfrontend2 ([]) by compute4.internal (MEProxy); Sun, 02 Oct 2022 21:14:12 -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=1664759651; x=1664846051; bh=2 HOetkhS6bK7hlH32jXdCXAmjrWRjkgoqFJBqGknyI4=; b=kvc8hq1eGWLDGJ0LH O+CZYQQOnrZhHcKtVRUV/OuVf9uZhFdRVW7VmcTIDVZAoTf14Meyy6cryYjHJ6nz Au5omTt3a4S1Nb4sVUM+6c4xB54Q8ZLNhIVzGr+Te3K6jyv2UwYgnxeRqKxOaqR9 E/ne6So/cX3HuQAGICFHzVHP+jMhYD+LnYslRVJam0UqEwC4FdxVe0YGZ/liijoW Tcz2HXsOoAaGMzAw97fDhn4Vj0C22PEXATW23GmPFLOChbGHwSltCZjmxCH8BDIR 8h2tYiajARriPyJjd0e6P0Izsn/svOuQyUNtusXc86Q9kMOT5l0GIpxKAHJBk5sR Imo1Q==
X-ME-Sender: <xms:Yzc6Y2NYSmuOJaYqfxzJ08wtojE2u-k2vE_v0r2DB-xmaws85vXa9Q> <xme:Yzc6Y0-wShcAUnrT-UfrvjEeIDU9JMDRziluaY7ZrkpxCYDTVh2bt4byDcEYj6nSg WWFNpLtfbG0JQ>
X-ME-Received: <xmr:Yzc6Y9RjaAeraHcns-5lE3mtSUyryE0tgXtkvNSNsJPVx3_EWUvl7EGHKRfWq_Ak2yB6EUaT9YBwCkzmtHvi0fPqcUbztpMXWo4yzPEpXdCv_Z37Gcflng>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeehkedggeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomhepmfgvihht hhcuofhoohhrvgcuoehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh eqnecuggftrfgrthhtvghrnhepfedtvdelieejveekjefhueduheeviefhjeefvdfgudfh fffhudduudefgefgteevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:Yzc6Y2tldhXVVZjQEq48ruzLdXd_YIZORVuBX89-VMLl5nsiMqd5mw> <xmx:Yzc6Y-cUbwe8XGQ_EbGU5NtlUbB6topesecInifXZe4z0p9oiXl3xQ> <xmx:Yzc6Y60M7g4b6IVEBbyjeg84a4oTsWVstoOB8OWr0a-Fg5ohCpwPJg> <xmx:Yzc6Ywr-UGDmCTS-CsL3o8u1Ey1S2Ef2kSA8mLZuIMkZKRDqfi5l3A>
Feedback-ID: i5d8c41f0:Fastmail
Received: by (Postfix) with ESMTPA; Sun, 2 Oct 2022 21:14:11 -0400 (EDT)
Message-ID: <>
Date: Sun, 02 Oct 2022 21:14:10 -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
To: Brian E Carpenter <>,
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] 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 01:14:16 -0000

On 10/2/22 21:04, Brian E Carpenter wrote:

> On 03-Oct-22 13:17, Keith Moore wrote:
>> I would instead say that any group that, whether via the charter or 
>> the chair, is told "you have to do it this way" should be immediately 
>> shut down.
> Hang on. There are occasions when the charter is quite restrictive for 
> a good reason connected with the "running code" part of our mantra. 
> For example, I think the original NFS WG was restricted by 
> backwards-compatibility with proprietary NFS. (However, I don't know 
> where I'd look to find the original NFS charter.) In the current DMARC 
> charter it says:
> "The working group will seek to preserve interoperability with the
> installed base of DMARC systems, and provide detailed justification
> for any non-interoperability."
> I'm sure there are many other examples, as well as quite a lot of 
> charters referring to a personal I-D as a starting point. So while 
> charters cannot preempt the final rough consensus, they can certainly 
> restrict the starting point.

I will concede that there are a few good examples, particularly those 
for which interoperability with a substantial installed base is 
considered important.   But I've seen lots of charters that essentially 
dictate the solution without a good reason that I could see.

(It still troubles me, for example, that it's 2022 and the Internet 
still doesn't have a widely-applicable file system access protocol.)