Re: [Rfced-future] Model proposal

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 14 July 2020 00:39 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 1914F3A0C33 for <rfced-future@ietfa.amsl.com>; Mon, 13 Jul 2020 17:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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] 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 wpsv_ap4JCLC for <rfced-future@ietfa.amsl.com>; Mon, 13 Jul 2020 17:39:33 -0700 (PDT)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (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 D3F653A07C8 for <rfced-future@iab.org>; Mon, 13 Jul 2020 17:39:33 -0700 (PDT)
Received: by mail-pl1-x630.google.com with SMTP id p1so6273071pls.4 for <rfced-future@iab.org>; Mon, 13 Jul 2020 17:39:33 -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=6i/NiGTMqOYqBhwmusNl0ayXhevGSd4feKGlAjZEOko=; b=CY3eLJCecvDpdDFAivQXQM3lfLjqfIj4XC+X45M7KskA6i2j2haLc9qE8phu1cO+mh lfo2g+C2iQdzdo9c0ZbLm2MpWkix5rt5TpRzHw/jN8MNXBfDx1EgjtJM7vm662xwOlCP Dy1WsXR7GbQABr7gpSGQz01pJTUQZcgVgmmIUvBmZIHraHT8Ce2ycYzK7kEeeczy6Juj v63RNGobuCNLbmYrcfLv/iKxR60bu0QngBuJ84OTAM/DxQnZAybkSfnY2MtpG8lBfuvY vhwM/OIXyVesJUsj5wa6Gp2hBp629wb66J0gpfkrzWw6PSJKsbSN100BSWoxGliyYq+B V1qA==
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=6i/NiGTMqOYqBhwmusNl0ayXhevGSd4feKGlAjZEOko=; b=cxsxgTp8jemKG8INKuhWvFiUhZNNzKb5Iw0u2SXouxYs3Hsq2eD0fvvV+J8TMdjPeo fI7+Pl/eUm0OyFlH5/nYgzt//TCqmd6OKY+QO6RedARUcp1Dte85UkR/Mbw/6WCtrN4g Bt/BRaY8gdqcORe23ZEeZKqaFZbhrTxbT8vOp19O0M0zIZvTbNeRNFRkjhAvuNfRZSof PsJQbnNKlgxyv3gQ5ywnc+JIh9itoJuYhRMQxJUzm1SKaRVNIGbH77kgi4kBdWXvOOnL hAFGcd070xgmntERwTNjtvmuMPVegZWJcIirbHjG5tt+EHEIwGEFe7ziQAF//FwFmw+B kuvA==
X-Gm-Message-State: AOAM531oQN04+K3apCSmJQTV3hvbQ6ciQvtogzP33e8fyypcC3me1vlW /a5IWXT25tx33pvW6qLZ8mvDDVw6
X-Google-Smtp-Source: ABdhPJyhNkIEHizfacr/8YHqUN2tFO9bkKQMoa0dCrXllrdsijsYJMqyrEry7ivDhOR7GoLbF22Rvw==
X-Received: by 2002:a17:90a:9f4a:: with SMTP id q10mr1980234pjv.139.1594687173081; Mon, 13 Jul 2020 17:39:33 -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 w71sm15286560pfd.6.2020.07.13.17.39.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jul 2020 17:39:32 -0700 (PDT)
To: Nico Williams <nico@cryptonector.com>
Cc: Martin Thomson <mt@lowentropy.net>, rfced-future@iab.org
References: <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> <9d390288-1056-4997-a540-96510e19a099@www.fastmail.com> <3bb43b97-211b-cee3-c365-906192c4b337@gmail.com> <20200713072413.GY3100@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <97dd7100-73bd-79fb-0419-703fb9773c7a@gmail.com>
Date: Tue, 14 Jul 2020 12:39:27 +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: <20200713072413.GY3100@localhost>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Bw-BlwKH2Z41okNjUPOrNyfCQ4o>
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:39:35 -0000

On 13-Jul-20 19:24, Nico Williams wrote:
> On Mon, Jul 13, 2020 at 05:52:08PM +1200, Brian E Carpenter wrote:
>> On 13-Jul-20 11:16, Martin Thomson wrote:
>>> On Sat, Jul 11, 2020, at 06:57, Brian E Carpenter wrote:
>>>
>>> I stand by the formal piece.  My logic is that we should not create
>>> a new body for this process.  Of the bodies we have, the IAB is most
>>> suitable.
>>
>> Yes. The alternative is a new body. As I've said repeatedly since
>> about 1995, I'd like to see the IAB freed up to do nothing but things
>> related to Architecture. I count IANA and liaisons as part of that,
>> but not running a publishing service.
> 
> We almost certainly don't need a new body for this -- is there even
> enough work for it?  We weren't happy with the RSOC...  I do, though,
> understand and sympathize with the desire to free up the IAB to work
> only on architecture -- I just don't see how to shift this
> responsibility elsewhere.

There are various options that come to mind, but they all amount to a new committee or Board that answers to a wider community than the IAB does. For example:
(a) an RFC Series Strategy Committee nominated by the 4 RFC streams by their own processes, or
(b) an RFC Series Strategy Committee nominated by its own free-standing open nomination process.

And then:
(x) this Committee is constituted and hosted by ISOC, or
(y) this Committee is hosted by a stand-alone RFC Foundation or RFC Trust.

I'm sure there are other options. Once we move contractual oversight explicitly to the LLC, we have a lot of flexibility for the strategy/policy stuff.

Regards,
     Brian