Re: [Rfced-future] Model proposal

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 14 July 2020 00:27 UTC

Return-Path: <brian.e.carpenter@gmail.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 078263A0808 for <rfced-future@ietfa.amsl.com>; Mon, 13 Jul 2020 17:27:50 -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 TElXg6LLHoX0 for <rfced-future@ietfa.amsl.com>; Mon, 13 Jul 2020 17:27:48 -0700 (PDT)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 3EAA23A03FA for <rfced-future@iab.org>; Mon, 13 Jul 2020 17:27:48 -0700 (PDT)
Received: by mail-pl1-x62f.google.com with SMTP id k5so6246354plk.13 for <rfced-future@iab.org>; Mon, 13 Jul 2020 17:27:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=6W41yPkOfy6zBLG8XwuhIpRulJ6SLcZSBTy6oMrnlq0=; b=ttRMQ3oLYdHkBe+CvQ1OiG+xVKMWvvIrmL/eLzZ4uIBmybUnpwyMRcuU7zJalyTpdI 8nmPLGOH+HJCjeMAQJucCTmcF4LoL6nzbYqch/zgAAKKaJ/9Um5JFdB2BGRq3QED89fo Cfbld8ne6zCWqr/IVgtfnsbv+urLIKvDUk7yZhA2jDrPY7ZP+HmVHyOvR95XwL4JbOoP AbkxuDts+EFiaiTqhz/2rWDCOzVbjcxqS2Fs+FBn6A/oqV2y/E+98dTxXEQGCgflHiko Ti3cnnpA6K5Z37V0LfhW0ZYTqqhWqTWgkzEq/r58y9sn+UDmiRxpNzF1IBWCgdofDy3W MmUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; 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=6W41yPkOfy6zBLG8XwuhIpRulJ6SLcZSBTy6oMrnlq0=; b=M7wN+kbEQ67kJp85Xj8p5X6Rj4yjDHutjMLLa/Q1wa8+blyKOg6/GqfwEykD7+vwx5 AMhfYp1Co2JOZkwsFC6rTLWlQQ4AVf2TmjB419VFa991dDhQhmmDoO4snyMATMXsILy1 pGEZ3WgN1w6mtax5Bn6quz5c7hADbvUzAWXue3YzYpwGfiBwHdK9qsL6nT0LA1TcuAcO OpK0rfyF2NHRR7H5KLwTuy/xVeVtiQOj2IVXdW1r3NXnFZjYkL/gB2NaaiWY1p7yjcZw 2Z7b/xdo6a1d1Ts1Eailt96yKAztDnuD1hJv59Pj910yjfdEXi4Y8AupwDhOys9QG39b ptLQ==
X-Gm-Message-State: AOAM533k92VfIQ3CIs+O4i6wfNBtebZ2G+1UNGkXIjqUbm2oV5Zkiv+3 cGodR9wNguDHbV0m9FBolCK+XGkt
X-Google-Smtp-Source: ABdhPJwQCLfIqJEw8FqhPs3X25u/y5SqAtNi+ojhrcSSEvSSd5PrEOvrJdZjU+QU0x9HFP/5yYvklg==
X-Received: by 2002:a17:902:c181:: with SMTP id d1mr1778869pld.176.1594686467385; Mon, 13 Jul 2020 17:27:47 -0700 (PDT)
Received: from [130.216.37.170] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.37.170]) by smtp.gmail.com with ESMTPSA id q13sm16661606pfk.8.2020.07.13.17.27.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jul 2020 17:27:46 -0700 (PDT)
To: Eliot Lear <lear@cisco.com>
Cc: rfced-future@iab.org
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> <35E314A9-1FF1-45FA-86B1-34A7F15B7F03@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <2924fac2-9b69-f19c-7eda-43c5d55bc4ec@gmail.com>
Date: Tue, 14 Jul 2020 12:27:42 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <35E314A9-1FF1-45FA-86B1-34A7F15B7F03@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/XtnjtdCY0gRFjUIy7KXIZyEY7Zw>
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: Tue, 14 Jul 2020 00:27:50 -0000

On 13-Jul-20 21:07, Eliot Lear wrote:
> 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.

Certainly, as long as the contracts are held and administered by the LLC, dispute resolution relevant to the contracts must involve the LLC. I was thinking more of potential disputes about the strategy/policy process.

   Brian

> 
> Eliot
> 
>> On 10 Jul 2020, at 22:57, Brian E Carpenter <brian.e.carpenter@gmail.com <mailto: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 <mailto: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 <mailto: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 <mailto: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 <mailto:Rfced-future@iab.org>
>>>>>> https://www.iab.org/mailman/listinfo/rfced-future
>>>>>
>>>>> -- 
>>>>> Rfced-future mailing list
>>>>> Rfced-future@iab.org <mailto:Rfced-future@iab.org>
>>>>> https://www.iab.org/mailman/listinfo/rfced-future
>>>>
>>>
>>
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org <mailto:Rfced-future@iab.org>
>> https://www.iab.org/mailman/listinfo/rfced-future
>