Re: [Rfced-future] Model proposal

Eliot Lear <lear@cisco.com> Mon, 13 July 2020 09:07 UTC

Return-Path: <lear@cisco.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 0FEF63A0C5E for <rfced-future@ietfa.amsl.com>; Mon, 13 Jul 2020 02:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.7
X-Spam-Level:
X-Spam-Status: No, score=-7.7 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 3Ynehxmkz1fN for <rfced-future@ietfa.amsl.com>; Mon, 13 Jul 2020 02:07:40 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCAD03A0C5B for <rfced-future@iab.org>; Mon, 13 Jul 2020 02:07:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12230; q=dns/txt; s=iport; t=1594631259; x=1595840859; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=Bd3uJkbTVNZFiXccvkfCgK3IQfAlfWth/tcOqR/4YnM=; b=fcXvFqoemAzcIgTYt8xigO7DIuv6TAoBfJPBnNwhVrfdkwAfHUvTAh+r ZRsmspIog2vKVThqY/54SEK1qjZX7lWDp6mN6F8xE4E6ag5rPtDye64wy dT3aH5awMgMnNIGdrX45+a6jAoaHIQF4Et/OOaf6jq11GqNuEQqkiir+e 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BZAAAXJAxf/xbLJq1gGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBggqDGVQBIBIshDOJAYgaigKJcIgXCwEBAQwBARgBCgwEAQGETAKCGSU4EwIDAQELAQEFAQEBAgEGBG2FWwyFbwEBAQECAQEBIQRHCwULCxIGKgICIQYiDgYTgyYBgksDDiAPplh2fzOFUYJgDYIcBoE4AY0LggCBESccgk0+ghpCAYR2M4ItBI8xpR5NgmeDBpFihHADHoJ0iTaEfCiNXJ5pjiWDUgIEBgUCFYFqI4FXMxoIGxU7KgGCPj4SGQ2XI4VEPwMwAjUCBgEHAQEDCZAOAQE
X-IronPort-AV: E=Sophos; i="5.75,347,1589241600"; d="scan'208,217"; a="27854799"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Jul 2020 09:07:35 +0000
Received: from [10.61.229.127] ([10.61.229.127]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 06D97YRG017478 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 13 Jul 2020 09:07:35 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <35E314A9-1FF1-45FA-86B1-34A7F15B7F03@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D6EA3A85-05CD-4270-AA75-26268745B703"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 13 Jul 2020 11:07:34 +0200
In-Reply-To: <14ef71ed-8f2f-22f4-edf0-ca22b004ec7c@gmail.com>
Cc: rfced-future@iab.org
To: Brian E Carpenter <brian.e.carpenter@gmail.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> <9A6E6D1C-FD14-4285-92A2-2483D9452CE9@vigilsec.com> <14ef71ed-8f2f-22f4-edf0-ca22b004ec7c@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.229.127, [10.61.229.127]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/5dE9AQEUV4Yd9SWa0GaCizMz6_k>
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: Mon, 13 Jul 2020 09:07:43 -0000

When discussing appeals chains, it is probably worth asking a few questions to be sure we have this right:

What can be appealed?
What remedies are permitted in the appeal at what level?
What are the interests in potential appellate bodies that might conflict?
Would a potential appellate body agree to extend its remit to cover such service?
Does the potential appellate body have the necessary authority to institute a remedy?

In particular, I would suggest that all of this be considered in light of the existence of the LLC and its board and their fiduciary responsibilities.  I’m not suggesting a particular answer here, but merely a line of questions that we should be comfortable answering.

Eliot

> On 10 Jul 2020, at 22:57, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> 
> Russ,
> 
> On 11-Jul-20 04:09, Russ Housley wrote:
>> 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.
> 
> It will be what we define it to be at the end of this discussion. Please remember that I for one believe that we should probably take this responsibility away from the IAB completely. I can't see any reason except history for an "Architecture" committee to be in charge of a publishing service.
> 
> I'd certainly be inclined to put the ISOC Board at the end of any appeal chain, but it's a new thing, not part of the IETF standards process.
> 
> Regards
>    Brian
> 
>> 
>> 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
>>> 
>> 
> 
> -- 
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future