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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 09 September 2021 21:54 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 130A73A0C1E; Thu, 9 Sep 2021 14:54:17 -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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, 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 (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 8j_SKSPuhwfj; Thu, 9 Sep 2021 14:54:12 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 3E53B3A0C1A; Thu, 9 Sep 2021 14:54:12 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id n34so2955014pfv.7; Thu, 09 Sep 2021 14:54:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=vUfgh6lQ9LqRrH9+kmfCiqsmfIiGSiNfygyIJhuXiBM=; b=e+BANToNkmyorSZi2439UI9iF4veH3E1BXzpOcFzOQpwRlJ3Cg5JsFOm8eVg8R7v8h +Nr+lk14BSrASVOgCWCQN0TD8VApwofss4YJJW7Qkdfsparid70hB2KIyAxdC1HVqs38 931ijh5qK/prm+OdWEBHkUl6Xp7wC5ro4A8ezynkd+H5MLgHUGQ5FcwxSkQgqhwrzl8w DD1/OLZjw4XUlJTK04G/8Avviz/8+q3WC6PEH8DDqq4Ri+O9JHXCnPUyTBC605VD04MG LJuI7g2kma/B6AggzS35jKHAiVjRq/a7cEOVkOxLGhYrSHWUGZwdyl9NQWDJTa3FH5U7 e8Ow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=vUfgh6lQ9LqRrH9+kmfCiqsmfIiGSiNfygyIJhuXiBM=; b=PLn75yWfUEufcaRT/es/QSvdtxd0I5Impazk2hZGL8j30efgI0UdD/fqLjD0ZRCqzY 8NGyEVWvrcfuijEnCx6HZtiobw1Op52GWFXRf9neqGwcy4m6iJSGYCa3BpWdijpWvfLN OUWBWmF0Zn/dSGYdxM+5EzE17yzvvRDy8eRr3Fd8r3AdYkh4+wljTFgO97WpKtx2vNbg m/n5sE5IKg7uvWl2amaeNTpXllJhN9eboK0QjSbrkd4ESvkhPTX/teJbtyUXRw8V3e4a C9g5fXLp3wo9n8HDL9UnzuRcwLhImxPDpD0jwzFH+5y96ieYJtA4i7Em/9GlXP7dP7us PxVg==
X-Gm-Message-State: AOAM5338xdykiEkZ51TCiJnaHBj5F3c81vMacjFahY2rnpL+KsGGw9+p 4jgGw+ngEh5p5V/djF5LntdPPnKWDBQ=
X-Google-Smtp-Source: ABdhPJwy83pnsbppDHs+vVM8OnQLgBYTm6rYa0Z3Yis1CQClX63OqZwhWoWjyfWfNpg5MBZZqK7VUA==
X-Received: by 2002:a62:7542:0:b0:434:dfe5:8b37 with SMTP id q63-20020a627542000000b00434dfe58b37mr120386pfc.84.1631224450332; Thu, 09 Sep 2021 14:54:10 -0700 (PDT)
Received: from ?IPv6:2406:e003:11aa:d701:80b2:5c79:2266:e431? ([2406:e003:11aa:d701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id l22sm3527149pgo.45.2021.09.09.14.54.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 09 Sep 2021 14:54:09 -0700 (PDT)
To: Barry Leiba <barryleiba@computer.org>, Lars Eggert <lars@eggert.org>
Cc: GENDISPATCH List <gendispatch@ietf.org>, draft-eggert-bcp45bis.all@ietf.org
References: <163101639697.11702.11425677914483803771@ietfa.amsl.com> <CALaySJK7gF_FZRoYc_mhk62jGEvsO8oD-_rSpBErwNRvjHmpEg@mail.gmail.com> <40144D1F-3D7F-4C43-9C4E-2F914B5458D1@eggert.org> <CALaySJJ7=7W2BRHW9q=2EP15-W_sdypu6Z6K_=UeqAOMVK+hNQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0415be9c-4b25-0e08-fe9f-7c927c0765d3@gmail.com>
Date: Fri, 10 Sep 2021 09:54:04 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJ7=7W2BRHW9q=2EP15-W_sdypu6Z6K_=UeqAOMVK+hNQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/2OlV2DiLemNeMYsfvsG84h5ux38>
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 21:54:18 -0000

Nit pick:

> It absolutely makes the most
> sense for people to start with the IETF Chair

Actually, appeals (from WGs) start with an AD, so maybe this one
should start with the General Area AD? (I know it's the same person,
but wearing a slightly different hat.)

Better, perhaps: start with an AD, normally the General Area AD.
If the nature of the appeal personally involves the IETF Chair, the
appeal should start with some other AD.

Regards
   Brian

On 10-Sep-21 02:18, Barry Leiba wrote:
>> 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.
> 
> But you've already changed "complaints" to "could be appealed", which
> moves from something generic and undefined to something formal and
> documented.  And, in fact, this document is so markedly different to
> RFC 3005 that I couldn't use a DIFF at all, so I see the changes as
> not minimal.  Please re-consider this point, and make it clear that
> the normal appeals process applies.  It absolutely makes the most
> sense for people to start with the IETF Chair -- or at the least, the
> IESG -- before going to the IAB.  Appeals work best when there's more
> than one stage to them.
> 
> Barry
>