Re: [Rfced-future] Model proposal

Russ Housley <housley@vigilsec.com> Fri, 10 July 2020 16:09 UTC

Return-Path: <housley@vigilsec.com>
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 A74FD3A0F1F for <rfced-future@ietfa.amsl.com>; Fri, 10 Jul 2020 09:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XhgKGVLCegBG for <rfced-future@ietfa.amsl.com>; Fri, 10 Jul 2020 09:09:10 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E43253A0F16 for <rfced-future@iab.org>; Fri, 10 Jul 2020 09:09:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 0ACCC300B23 for <rfced-future@iab.org>; Fri, 10 Jul 2020 12:09:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GHWVFJmKAMR6 for <rfced-future@iab.org>; Fri, 10 Jul 2020 12:09:04 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id 293B8300670; Fri, 10 Jul 2020 12:09:04 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <48E30FDD-24B1-4602-9740-BB4DA2A4A7C1@sobco.com>
Date: Fri, 10 Jul 2020 12:09:04 -0400
Cc: rfced-future@iab.org, Martin Thomson <mt@lowentropy.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A6E6D1C-FD14-4285-92A2-2483D9452CE9@vigilsec.com>
References: <d4d1cd2d-6df2-4cb4-b63a-f9bba45b48c0@www.fastmail.com> <51b72823-f2a2-29bd-bd88-f63e13522387@gmail.com> <d1f33279-0656-4caa-81e7-aa665d3a4acb@www.fastmail.com> <098fb5bf-f65c-d741-5fa7-baa6ae2c8358@nostrum.com> <F30FBA82-510C-4DC1-8535-FFA30345CEA7@kuehlewind.net> <DE2B2759-03FF-4D2C-B765-3C7C9AFA0955@vigilsec.com> <2A7C36D3-62CD-4BA0-88BE-F19A06D991DB@sobco.com> <48E30FDD-24B1-4602-9740-BB4DA2A4A7C1@sobco.com>
To: Scott Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ecE_qAEObAXFEbKCRJyOLacDCpQ>
Subject: Re: [Rfced-future] Model proposal
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, 10 Jul 2020 16:09:12 -0000

Scott:

I stand corrected.  I mis-read the last sentence of Section 6.5.2.

All:

The overall point remains, does RFC 2026 apply here? If not, the the only appeal body would seem to be the IAB.

Russ


> On Jul 10, 2020, at 11:32 AM, Scott O. Bradner <sob@sobco.com> wrote:
> 
> from 2026
> 
> 6.5.3 Questions of Applicable Procedure
> 
>   Further recourse is available only in cases in which the procedures
>   themselves (i.e., the procedures described in this document) are
>   claimed to be inadequate or insufficient to the protection of the
>   rights of all parties in a fair and open Internet Standards Process.
>   Claims on this basis may be made to the Internet Society Board of
>   Trustees.  The President of the Internet Society shall acknowledge
>   such an appeal within two weeks, and shall at the time of
>   acknowledgment advise the petitioner of the expected duration of the
>   Trustees' review of the appeal.  The Trustees shall review the
>   situation in a manner of its own choosing and report to the IETF on
>   the outcome of its review.
> 
>   The Trustees' decision upon completion of their review shall be final
>   with respect to all aspects of the dispute.
> 
>> On Jul 10, 2020, at 11:29 AM, Scott O. Bradner <sob@sobco.com> wrote:
>> 
>> this is not correct
>> 
>> under 2026 the only thing that can be appealed to the ISOC Board is a claim that the procedures as written are incorrect (e.g. unfair)
>> 
>> Scott
>> 
>>> On Jul 10, 2020, at 10:14 AM, Russ Housley <housley@vigilsec.com> wrote:
>>> 
>>> Martin proposed:
>>> 
>>>> Concretely, this proposes forming a RFC Series Evolution program of the IAB that uses the auspices of an IAB program, one that closely follows the model proposed in [RSEME]. This results in a group that follows [WG] procedures, with the exception that the functions performed by the IESG are instead performed by the IAB. In particular, selection of chairs and appeals regarding the execution of the process are directed to the IAB to resolve.
>>> 
>>> In an IETF WG, the appeals chain is:
>>> 
>>>  WG Chair --> Area Director --> IESG --> IAB --> ISOC Board
>>> 
>>> I think this proposal is saying that for this activity, it is:
>>> 
>>>  Program Chair --> IAB --> ISOC Board
>>> 
>>> Is every decision appealed to the IAB possible to escalate to the  ISOC Board?  Usually, disputes can only be escelated to the ISOC Board that claim that Internet standards procedures were not followed.  However, the appeals chain is quite short here, and ir is unclear to me that the Internet standards procedures applies to IAB programs.
>>> 
>>> Russ
>>> 
>>> -- 
>>> Rfced-future mailing list
>>> Rfced-future@iab.org
>>> https://www.iab.org/mailman/listinfo/rfced-future
>> 
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org
>> https://www.iab.org/mailman/listinfo/rfced-future
>