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

Lars Eggert <lars@eggert.org> Sat, 11 September 2021 05:37 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 02EDB3A0A2E; Fri, 10 Sep 2021 22:37:09 -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 LdT0fqQ0B9zK; Fri, 10 Sep 2021 22:37:03 -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 1BCD23A0A2C; Fri, 10 Sep 2021 22:37:02 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:c99d:320:675b:ac33]) (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 33F3F600373; Sat, 11 Sep 2021 08:36:42 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1631338602; bh=2gOvRFUi90cAdZc5mnDzVlenYGTo3Bmo1rlH4bmRPPM=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=oscp/gqjCRR9kI7it9Oks/1xoDRIlfKCVuTRPs95Etd6n97WCIYozZpRwkboAtsUc MPu2eUV/9Xm2Wy8K5G1LbGuXUreUcdnmEVcpWGqHGkcIRh5bjsF3oWAba+wQzHU9sc F1ez7pTZXWYyqIeATjHUoaGQjtZIF/hiLAHfY8fU=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Lars Eggert <lars@eggert.org>
Mime-Version: 1.0 (1.0)
Date: Sat, 11 Sep 2021 08:36:39 +0300
Message-Id: <B45896C1-F9F1-44F6-9BF7-8AF9B573233C@eggert.org>
References: <0a918f8f-b2bd-4756-b0f5-23ff8063f1e8@gmail.com>
Cc: Barry Leiba <barryleiba@computer.org>, GENDISPATCH List <gendispatch@ietf.org>, draft-eggert-bcp45bis.all@ietf.org
In-Reply-To: <0a918f8f-b2bd-4756-b0f5-23ff8063f1e8@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-MailScanner-ID: 33F3F600373.A3818
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/0k1FPJYwRipYOod_zWUOQjYzLaE>
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: Sat, 11 Sep 2021 05:37:09 -0000

Hi Brian,

Is that an option in your reading of 2026? They way I understand it is that if the AD is conflicted, the entire IESG is the next step?

Thanks,
Lars

-- 
Sent from a mobile device; please excuse typos.

> On Sep 10, 2021, at 23:20, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 10-Sep-21 23:01, Barry Leiba wrote:
>> That works for me, Lars, and thanks.
>> 
>> I see Brian's point about Gen AD instead of IETF Chair, but I don't
>> agree with it here, because the SAAs are explicitly appointed by the
>> IETF Chair, not related to the Gen Area.
> 
> You're correct. There's still the corner case where the IETF Chair is
> conflicted - for example, if the message(s) objected to by the SAAs
> made allegations about the IETF Chair themself. Probably another AD
> should be the first recourse in that case.
> 
>   Brian
> 
>> 
>> Barry
>> 
>>> On Fri, Sep 10, 2021 at 3:11 AM Lars Eggert <lars@eggert.org> wrote:
>>> 
>>> Hi,
>>> 
>>> I have a proposed change to use the normal RFC2026 appeals process in https://github.com/larseggert/bcp45bis/pull/7/files. This is the current change:
>>> 
>>> --- a/draft-eggert-bcp45bis.md
>>> +++ b/draft-eggert-bcp45bis.md
>>> @@ -192,8 +192,8 @@ manner.
>>> 
>>> 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.
>>> +decision can be appealed to the IETF Chair, per {{!RFC2026}}. Decisions by the
>>> +IETF Chair can be appealed to the IESG as whole, again per {{!RFC2026}}.
>>> 
>>> # Security Considerations
>>> 
>>> Please let me know if this expresses what is desired?
>>> 
>>> Thanks,
>>> Lars
>>> 
> 
> -- 
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch