IETF Logo Mail Archive

Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model

Eliot Lear <lear@lear.ch> Fri, 11 March 2022 20:07 UTC

Return-Path: <lear@lear.ch>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212923A00E3 for <rfced-future@ietfa.amsl.com>; Fri, 11 Mar 2022 12:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lear.ch
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 fdh0S-0tAITS for <rfced-future@ietfa.amsl.com>; Fri, 11 Mar 2022 12:07:19 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A2233A011B for <rfced-future@iab.org>; Fri, 11 Mar 2022 12:07:18 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::9] ([IPv6:2001:420:c0c0:1011:0:0:0:9]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 22BK7DHL794932 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 11 Mar 2022 21:07:13 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1647029234; bh=7JHqAWT1zZEHDTwZknt2HkO5ucDHLwHlznUSWRNOSZA=; h=Date:Subject:To:References:From:In-Reply-To:From; b=VWLoQxz5RJgx+pniQS50bkVEPybGfyLZciA31bN6hhBRcAYrpXms2bKnm873co/iB aSNrY7pHE+zyV+NGuQ/BuuMUWqTqclHhUcqpayb72uW5udRDrXff2kjJqQbsdawuOp +ttBvnKjUragmt7t1DF4selXcg2z8iWtOKPcMxBE=
Message-ID: <c99085ab-002e-491e-0b58-12a72e7bfc99@lear.ch>
Date: Fri, 11 Mar 2022 21:07:10 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.2
Content-Language: en-US
To: Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org
References: <CAL0qLwbHobErxtCxiMCtYtqByJJhWF79XAwtw2jV9DNte1OuUQ@mail.gmail.com> <e3e01de3-8b69-852a-7dca-cb0e9735ce4a@lear.ch> <CAL0qLwZnaZ2J=7YnOS96h42135w6NrEdn-Obj7QOWwwRxDj1vg@mail.gmail.com> <c059e4d2-99a1-3148-16d4-c789673575df@lear.ch> <CAL0qLwZkaebQmmQdfKsW7oCd58X5DRWY6_QpUaVUueZAyGVA6g@mail.gmail.com> <797efdc3-e674-504e-80e0-fa2b48923bb1@stpeter.im> <CAL0qLwauRS-G+_OcKPx-bRB0EpDKyib+XysWLTBRBka1CqQkmg@mail.gmail.com> <caaea09f-92cc-beae-2a4f-5df4cbf6ad7f@stpeter.im> <50286473-556a-f469-4447-130e2e9807b3@nthpermutation.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <50286473-556a-f469-4447-130e2e9807b3@nthpermutation.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------t0GPsMxq4rv5QtKRWzxMj6oq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/58EMPDRvcpqFHC3QggC-nO6vbmE>
Subject: Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2022 20:07:25 -0000

By my reading of RFC 2026 Section 6.5.2, this would not be permissible:

>    If circumstances warrant, the IAB may direct that an IESG decision be
>    annulled, and the situation shall then be as it was before the IESG
>    decision was taken. The IAB may also recommend an action to the IESG,
>    or make such other recommendations as it deems fit. The IAB may not,
>    however, pre-empt the role of the IESG by issuing a decision which
>    only the IESG is empowered to make.

Eliot

On 11.03.22 20:11, Michael StJohns wrote:
> Has the IAB ever resolved an appeal in a manner that directed the IESG 
> to approve the publication of a document?

v2.23.0 | Report a Bug | By Email