Re: [Gendispatch] I-D Action: draft-eggert-bcp45bis-01.txt

Lars Eggert <lars@eggert.org> Tue, 30 March 2021 06:57 UTC

Return-Path: <lars@eggert.org>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 572163A0BED for <gendispatch@ietfa.amsl.com>; Mon, 29 Mar 2021 23:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lkfnkTzCr2_4 for <gendispatch@ietfa.amsl.com>; Mon, 29 Mar 2021 23:57:04 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB9783A0BDF for <gendispatch@ietf.org>; Mon, 29 Mar 2021 23:57:03 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:1894:d982:c139:2ff9] (unknown [IPv6:2a00:ac00:4000:400:1894:d982:c139:2ff9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 58BBA600076; Tue, 30 Mar 2021 09:56:55 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1617087415; bh=mzXfqsaishC41v8MpVJ/jg8nlqXStCm5n4edJyOH3vE=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=kn6cuUKLhjsbl17bkdgdpTJ/1V9QUDjeG7IamgB6ht3K4kqprtmU3OXym9yvQ2bSW DCh2+mRuT01snBhHxNi4UYZXykDPoylsIx8QdK2R9leupWb9C3sLJi2N8b7HNS2MwV 3QPf3ZmgFtRWfJvJmzexHkxUKw2wSwvZoLcgS1p4=
From: Lars Eggert <lars@eggert.org>
Message-Id: <D277EB6F-FDB1-4588-A77B-FC29B0FB782F@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_C5FBDE1C-1D97-4EF5-9C77-55D74DE15940"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Tue, 30 Mar 2021 09:56:54 +0300
In-Reply-To: <55b4e061-f25d-8958-1e75-868bec0c735e@gmail.com>
Cc: gendispatch@ietf.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <161701910454.13044.908232164554537032@ietfa.amsl.com> <55b4e061-f25d-8958-1e75-868bec0c735e@gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-MailScanner-ID: 58BBA600076.A1E71
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/YjdffghDR-WzopsGeTYcce1oz4o>
Subject: Re: [Gendispatch] I-D Action: draft-eggert-bcp45bis-01.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Mar 2021 06:57:08 -0000

Hi,

On 2021-3-29, at 22:59, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> *  Questions and clarifications concerning IETF meetings, although
>> most of these topics are better brought up on the discussion list
>> for IETF LLC administrative issues [ADMIN-DISCUSS] or the attendee
>> discussion list for a given IETF meeting, such as
>> [IETF110-ATTENDEES] for IETF-110.
> 
> However, since not everybody attends IETF meetings, and therefore
> not everybody is on the attendee lists, we should be clear that
> messages like "we are going to discuss the very interesting topic X
> at the next IETF meeting" do IMHO still belong on the IETF list. The
> previous bullet in the draft already says this, but maybe we could
> reove any doubt by having this bullet start:
> 
> * Questions and clarifications concerning practical aspects of IETF meetings...

thanks, that is a good suggestion!

Thanks,
Lars