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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 30 March 2021 20:03 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 BDE483A2059 for <gendispatch@ietfa.amsl.com>; Tue, 30 Mar 2021 13:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 QHUSmJhLVi3M for <gendispatch@ietfa.amsl.com>; Tue, 30 Mar 2021 13:03:23 -0700 (PDT)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 D05A53A2058 for <gendispatch@ietf.org>; Tue, 30 Mar 2021 13:03:23 -0700 (PDT)
Received: by mail-pj1-x1036.google.com with SMTP id kk2-20020a17090b4a02b02900c777aa746fso16877pjb.3 for <gendispatch@ietf.org>; Tue, 30 Mar 2021 13:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ruVWQakEhtqq1sPsTfLjl3SPdOK9Ar+mSDZgupaULZs=; b=OEBpQ0ntAvzyZYdxej5161+7LvksyCrOK7K5S11k3xIrePK2qQO7rxExsVLzjSeyuE 51EqSRZpfOlpO0cRC4xmFh9s9TKcAe8RPaKay6mrG0wAOFo3JMMRwBz6iXCLEhfGsW1m yvryCsQLI8CrhQGmYBR8T1pMgCMlZzhSwmA7joSOOqxOZIQ2ZGkTixzlfvzndjxjEumw +yLtXodTBae75lAdUmHwAF1nIARrD2fktmYcIPNqo6A+5M2s3zxEXO5SbM/+E4Y4E1UG WdC35Um4840oEpEtGJgEfnDZJJdqkxSM8sSgjvPbOQRfJKcNjvly65jw30e4QZKnJRGM Kf9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ruVWQakEhtqq1sPsTfLjl3SPdOK9Ar+mSDZgupaULZs=; b=X+spovyJKddcjuvWMik4ogAx2FlIu+romZkQzJWuF/xIGjsloVJAg26sTt7egpGypv gl52RWtbX+hBaTuLIaDN+vmyQB79D5Ygz8Pqmjs66DFUQCRaW+FtjgJs5eXDh73IivF8 ve4oA4kgPcgaC3ZBsDrI3twEsm3VB/RiBWwOBPEyjvTvc+8QgGwDNnvjofOc0mkNmOEc O882gEU2Nr7mUIF1sa5uvCFlYRR+2lPDdVT9yb7NSp+K7mTEbR4TEXdz3knVPxeTK9Rs n9BmMudbkvzMJMzVGm6fwkiAaYC4ui/n9j4m0wWxa6ZR2rte6p2JJRZT45WKYMDlejaJ wrIg==
X-Gm-Message-State: AOAM530FY65CsAX9U+OQBo9mPLuTZfpKursIupq3bNZKzgrKF6FJrHxE EvzjGzrn8Vg2hQXprAgM1IqZfheJMN8RNg==
X-Google-Smtp-Source: ABdhPJzEF0kjyWk8Pq2CY++uwtjJSmGoQbtdQmpAAeHyzhe/sroTwLXM1/moc7B+TRaMXP89viPLLA==
X-Received: by 2002:a17:902:bd41:b029:e6:933a:f3ef with SMTP id b1-20020a170902bd41b02900e6933af3efmr34933302plx.19.1617134602038; Tue, 30 Mar 2021 13:03:22 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.131.14]) by smtp.gmail.com with ESMTPSA id h19sm21651644pfc.172.2021.03.30.13.03.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Mar 2021 13:03:21 -0700 (PDT)
To: Mark Nottingham <mnot@mnot.net>, Lars Eggert <lars@eggert.org>
Cc: gendispatch@ietf.org
References: <161701910454.13044.908232164554537032@ietfa.amsl.com> <55b4e061-f25d-8958-1e75-868bec0c735e@gmail.com> <D277EB6F-FDB1-4588-A77B-FC29B0FB782F@eggert.org> <963ED8F3-712F-4E8D-BF29-A3E7735E4641@mnot.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2c6a819e-ca2a-775d-94e3-183114ae1549@gmail.com>
Date: Wed, 31 Mar 2021 09:03:17 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <963ED8F3-712F-4E8D-BF29-A3E7735E4641@mnot.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/_vCLNBmamkhvkc8hQfUPY6YYDGc>
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 20:03:29 -0000

On 30-Mar-21 20:05, Mark Nottingham wrote:
> 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...
> 
> 
> If the intent is to makes sure that people are aware of relevant discussions, even if they're not on one of the attendee lists (and I usually decline that), it might be better to use ietf-announce@ -- e.g., in a "rollup" e-mail before the meeting, where submissions are solicited ahead of time. Or with an open calendar / wiki space (we rely on e-mail to much for stateful things anyway).

Sure, if it's an "official" topic that somebody with posting rights for -announce decides to publicise.
 
> Again, ietf@ should _not_ be the default place for announcing things. It is a subset of the community.

But it's the list that anybody can write to about possibly heretical ideas, including people outside the leadership bubble. (Also, BTW, ietf-announce is a shockingly small subset of the community. A lot of people apparently limit themselves to specific IETF echo chambers.)

On that topic, my own experience is that twice in my life, I have stopped reading ietf@ for about a year - once when I stepped down from the IAB, and once when I stepped down from the IESG. Both times, I felt like a break from the rather weird threads that sometimes develop there. Both times, I rejoined because I don't know a better way to hear what's on people's minds.

Regards
   Brian