Re: [Gendispatch] New Version Notification - draft-eggert-bcp45bis-04.txt

Lars Eggert <lars@eggert.org> Thu, 09 September 2021 06:51 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 27DD03A1E90; Wed, 8 Sep 2021 23:51:00 -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 vDQ-mcyfQH8r; Wed, 8 Sep 2021 23:50:56 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 C5D443A1E8B; Wed, 8 Sep 2021 23:50:55 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:c1e:417f:b160:6754]) (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 C36146003D5; Thu, 9 Sep 2021 09:50:49 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1631170249; bh=qBbdu5KYfBNqKrUlc5mDtaIbBqsf2zzcDJMoQcMnxBU=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=gApKtDhDzlYaqIOMw+9hXPlNlvC0NwlJWFPyj87NqAdlpvYNH+TdQ9evFhY72f90e P6WjoymhtHt/Wxvp1R120cyBDihvLyQuY6cJR0vh6344R3mStFvbE+IIy1UIlroyL1 c27e6u3OlqYbkrX3jmkHCE2cemhLOr37rBSV0iIE=
From: Lars Eggert <lars@eggert.org>
Message-Id: <40144D1F-3D7F-4C43-9C4E-2F914B5458D1@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_A25CEB52-777F-4227-9061-81D504C14B3B"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 09 Sep 2021 09:50:49 +0300
In-Reply-To: <CALaySJK7gF_FZRoYc_mhk62jGEvsO8oD-_rSpBErwNRvjHmpEg@mail.gmail.com>
Cc: draft-eggert-bcp45bis.all@ietf.org, GENDISPATCH List <gendispatch@ietf.org>
To: Barry Leiba <barryleiba@computer.org>
References: <163101639697.11702.11425677914483803771@ietfa.amsl.com> <CALaySJK7gF_FZRoYc_mhk62jGEvsO8oD-_rSpBErwNRvjHmpEg@mail.gmail.com>
X-MailScanner-ID: C36146003D5.AF98B
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/c_mupE7dsuMZe-c5jKR-F1hI9mI>
Subject: Re: [Gendispatch] New Version Notification - draft-eggert-bcp45bis-04.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: Thu, 09 Sep 2021 06:51:00 -0000

Hi,

thanks for the suggestions. Please see https://github.com/larseggert/bcp45bis/pull/6 for a PR that rolls those in.

On 2021-9-8, at 23:41, Barry Leiba <barryleiba@computer.org> wrote:
>   Because an SAA serves at the discretion of the IETF Chair - even if
>   the IETF Chair is not otherwise involved in the operation of the SAA
>   team - any SAA decision could be appealed to the IAB.  The IAB shall
>   then review the situation and attempt to resolve it in a manner of
>   its own choosing.
> 
> Why are we varying from the normal appeal process here?  One reason to
> keep the IETF Chair out of the operation is exactly so the first
> appeal *can* go to the IETF Chair, as it normally would.  Then to the
> plenary IESG, and then to the IAB.  I don't see a good reason to
> change that process.

This was also brought up by Rob during his AD review. This text is based on the current text in BCP45, which says:

   The IETF Chair, the IETF Executive Director, or a sergeant-at-arms
   appointed by the Chair is empowered to restrict posting by a person,
   or of a thread, when the content is inappropriate and represents a
   pattern of abuse.  They are encouraged to take into account the
   overall nature of the postings by an individual and whether
   particular postings are an aberration or typical.  Complaints
                                                      ^^^^^^^^^^
   regarding their decisions should be referred to the IAB.
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I assumed that "complaints" were supposed to be appeals, because otherwise it's undefined what the IAB was supposed to do with these complaints.

I'm fully OK with using the regular appeals process here, but since it would be a change from the original BCP45 and the intent was to do a minimal bis, I didn't make that change.

Thanks,
Lars