IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 10 September 2021 20:19 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 78C113A194D; Fri, 10 Sep 2021 13:19:56 -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 7eWtupkOvzmH; Fri, 10 Sep 2021 13:19:51 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 8E8D43A194E; Fri, 10 Sep 2021 13:19:51 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id d17so1859877plr.12; Fri, 10 Sep 2021 13:19:51 -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=BKzbt4BQpusMtfE1k9LU3bsEJBW76MgXpUjWsc3eiwg=; b=VKzxryykQbij31NcSR/BqORDmmM4ZmA1BIwjzrAj+GOkjVXn+1//amP19IuWVQ6B+p 5s3oxViGt4BX1iUdtpEWTd6+0uyf4rbDEswAjrPDxBdQ39r5XU++w8qwpZtdS+o03Yhz WNCJz9KHo2Sd7dfXAH99aVlqyG1+7dfkUyYThGuXFiG+pZo2eu3i/S1uLJrqau2l9Boj 5CyOHZK6+1KybLXv6K5t4CjXH3xEAJ6mwBNBwPWVEui1chGmKsFqI5yfgnxnjzcrWv8R Wwz8UPj8qHVbFwUJlh4Gfr6B14NnHZqq3tPjP9Xl5g+aT5boKYnIkpH+/06gKFk0LZu5 LWhQ==
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=BKzbt4BQpusMtfE1k9LU3bsEJBW76MgXpUjWsc3eiwg=; b=j6toNx793m8a9/OkvrM+g5xMcUeAjBB2d91xtqjweJzqsxfBVQy3mebmg6lVihZbkk Z52bQIcx3UEqlPHLYEk/83IJreDGhpNDljSsUDLrcmYpwXwccxE6Ygz38kaVG0ipP0Ge QT7uZW+uiEwdUc6ritRxoBlt84gqF0/HFW4wplHw+wu/sWXrZQcPz/M6OYlp6lsKtE8Q Si/P0JczZmCSeFcgV3yf6zAbCYsNq/oywrF52ptbWDB2CZ8DPzmPpsa0evZCWhpu3SAE ZsCcZz7IreXrheUZqjXhGd9+8aLWKdnrhXdNT2NnEbAo/k+KeQyk8X5SHN173YgiHA5a GIPg==
X-Gm-Message-State: AOAM533qdxrQrGocIROU4KSPqquy3pjQlLXESwA4MC8Sntk2vViUxeAa /QjPWjHLrWTDB8Lrgz+mesHMrJvmSdOA6g==
X-Google-Smtp-Source: ABdhPJzUzGDOiUy4pzSDSC5P3Br0ybq/8A8YUeBBKwNPxs8fJJqhGV4bKQ61JrWsa9QDYXX5otN7TA==
X-Received: by 2002:a17:90b:33c6:: with SMTP id lk6mr11538841pjb.203.1631305190470; Fri, 10 Sep 2021 13:19:50 -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 t13sm3706291pfe.199.2021.09.10.13.19.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Sep 2021 13:19:50 -0700 (PDT)
To: Barry Leiba <barryleiba@computer.org>, Lars Eggert <lars@eggert.org>
Cc: draft-eggert-bcp45bis.all@ietf.org, GENDISPATCH List <gendispatch@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> <0415be9c-4b25-0e08-fe9f-7c927c0765d3@gmail.com> <1130F786-31F0-4421-A062-DE3F80F4B368@eggert.org> <CALaySJJh=TMfKnQ+K9XcaUU8o=zBzEsPM59M2HLxspMb4by=_A@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0a918f8f-b2bd-4756-b0f5-23ff8063f1e8@gmail.com>
Date: Sat, 11 Sep 2021 08:19:46 +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: <CALaySJJh=TMfKnQ+K9XcaUU8o=zBzEsPM59M2HLxspMb4by=_A@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/w_S8QyTzP80vRs-tcXJsAIXVr80>
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: Fri, 10 Sep 2021 20:19:57 -0000

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
>>

v2.23.0 | Report a Bug | By Email