Re: [Rfced-future] Upcoming meeting: aiming towards approaches

Brian Rosen <br@brianrosen.net> Thu, 09 July 2020 12:59 UTC

Return-Path: <br@brianrosen.net>
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 098D03A09D1 for <rfced-future@ietfa.amsl.com>; Thu, 9 Jul 2020 05:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.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 3xC7ZOfKsbt8 for <rfced-future@ietfa.amsl.com>; Thu, 9 Jul 2020 05:59:12 -0700 (PDT)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 363A23A09A4 for <rfced-future@iab.org>; Thu, 9 Jul 2020 05:59:12 -0700 (PDT)
Received: by mail-il1-x133.google.com with SMTP id t18so1935527ilh.2 for <rfced-future@iab.org>; Thu, 09 Jul 2020 05:59:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IsoN1cH5vm3Ok0srtvxH+RMRGnOZiyf1CPoC/fapYbM=; b=RKbvsvKJFlwG2uPAfKhxisw69Ydhy35EDdQ/QOX7Nl1IabKcNkNWgtkCAzZ1LEE1wX auHcX8Joxlxwr7XfgVK8Q7xth7bBfMUcDdF9t72798XjDOCy5dGjl+N+MFaMVZYDCsE3 jlSNR4ii8jjSgzm+FI5Br5kASAArPAx7Z7nXJTgHceK4mFIVX3b2MWRHt4BXPss760dL uLmQx8+4C35QrG8Ae4P1PSZ0m0HzTiuX3jStsQa9XbJEGk9PYMoL6scl4Nk9uCTCBKTB bi7u84ycU8jx5SPASCNHFmQfQXzCintNB1C6DH5EPMYDK8W+nOQ78lsTV3Wohjzf3oTy 22xA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IsoN1cH5vm3Ok0srtvxH+RMRGnOZiyf1CPoC/fapYbM=; b=aj8NhqrXF4Didre6LwEJUQbMtvklm6qQubSZnYYLR7Y+QJteymGU+bDvHvmoFKlKcv uDa84npkAXECm6TgFDPdwCESXyWPFfzmEatgh4nRP4j9KIplBt9UCFjVjperA/ffXjWm Q70qzgcv0sLi8wxYkKp2pGLYxhBp9CkKu2JOBdth1Bq3iWCmN4js1s+NREYGjXLE3WDp 7JI2MUPL+eitI9iX2xuyFQKN92W3eqb/Xg3MyzHpYRbmoL6dz5qf7adiPM53yZGSPeaz JH5c5Ih+4xkXBVRjwLvCg0drkuk4xBCQl+v4ClsvzMA976XmwwJ2d5HctXnV2ExYiMOJ Vbjw==
X-Gm-Message-State: AOAM530o6dPj/76RimkOJU9QaJ5ZsB6wgxdtd7rwR5DlP2Eb/DjuHlEg uucS9yaR5hxYetB3Qo3PBdoJRw==
X-Google-Smtp-Source: ABdhPJzIPXPBFUtCsv3njSqJAZzQpnamLnQod+38Z1UTS84fRocd2pQNEI5ZgywvR2SCi6HdPsjrxg==
X-Received: by 2002:a92:a197:: with SMTP id b23mr44910185ill.58.1594299551399; Thu, 09 Jul 2020 05:59:11 -0700 (PDT)
Received: from brians-mbp-2871.lan (dynamic-acs-24-154-119-158.zoominternet.net. [24.154.119.158]) by smtp.gmail.com with ESMTPSA id y12sm1852649ilg.84.2020.07.09.05.59.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Jul 2020 05:59:10 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <677db945-44a5-3947-d531-2e68f0ffe5bc@gmail.com>
Date: Thu, 09 Jul 2020 08:59:09 -0400
Cc: Eliot Lear <lear@cisco.com>, Eric Rescorla <ekr@rtfm.com>, rfced-future@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <12905793-9461-4FFA-BC2D-9FFCC8477E1E@brianrosen.net>
References: <81D8F035-A1C3-41BC-A77C-10CA731A2B5B@cisco.com> <CABcZeBNBF4fHDCcF=kkY1rQJOFhm++==rncj+yMekDP2VpvjVA@mail.gmail.com> <AD86D86A-35E9-4000-BCE1-1EA76F5C7434@cisco.com> <CABcZeBNmbM0v01cVBW6GfAbDcp7ZqET9OL7d8Lqm4bvRX3BcZw@mail.gmail.com> <677db945-44a5-3947-d531-2e68f0ffe5bc@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/Kz3xQJZZqhVk5VgIOUYu9kE_U24>
Subject: Re: [Rfced-future] Upcoming meeting: aiming towards approaches
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: Thu, 09 Jul 2020 12:59:14 -0000

Inline

> On Jul 8, 2020, at 7:11 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 09-Jul-20 07:24, Eric Rescorla wrote:
>> 
>> 
>> On Wed, Jul 8, 2020 at 12:06 PM Eliot Lear <lear@cisco.com <mailto:lear@cisco.com>> wrote:
>> 
>> 
>> 
>>>    On 8 Jul 2020, at 21:04, Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com>> wrote:
>>> 
>>> 
>>> 
>>>    On Wed, Jul 8, 2020 at 12:02 PM Eliot Lear <lear=40cisco.com@dmarc.ietf.org <mailto:40cisco.com@dmarc.ietf.org>> wrote:
>>> 
>>>        Dear colleagues:
>>> 
>>>        The chairs have been tracking all conversations that have been taking place, and the contributions have been made.  Thank you all for providing your views to each other, and for responding to Brian’s earlier questions.  As you might imagine, we have been reviewing your input and refining based on your comments and other contributions.
>>> 
>>>        For IETF 108, we would like to test where consensus is on various key points.  Refining our earlier list of questions based on the list discussion, we now think we should ask:
>>> 
>>>          * Is there a person other than Jay who manages the RPC?
>>>          * Would people like to see a board, a standing working group/program, or both?
>>>          * Is there a leader who can run a community who is expert in publishing?
>>> 
>>>    This does not seem like the right question, as it presupposes a bunch of other points which are not yet decided.
>> 
>>    How so?  Is this just a wording issue? That should probably read more cleanly: “Is there a need for a leader…”. Does that change your view?
>> 
>> 
>> That seems somewhat better.
> 
> I think the somewhat hackneyed phrase "thought leader" is perhaps even better. I'm no longer hung up on the job title being "Series Editor". 
Yes, please let’s not get hung up on the title of the person.
We deliberately separated the notion of the manager of the RPC from the leader (or thought leader) of the process

> 
> While I'm here,
> 
>>>> Is there a person other than Jay who manages the RPC?
> 
> I think that's the wrong question because it assumes internal details about the LLC.
We didn’t think so.  We’re asking if there is some new person.  We think the community can decide that.  If we decide there is, I think we all assume that the LLC issues a contract or hires an employee.   Of course the manager and leader roles could be filled by the same contractor/employee.  There are a range of possibilities there, and we think we don’t need to discuss those until we get a consensus on whether we need one or both roles.

> 
> Try: Are the RPC contracts managed exclusively by IETF LLC?
> 
> And isn't there a 4th question:
> 
> * Is the IAB the correct body to approve (a) the RPC contractor and (b) the RFC Series general policy?
If there is a manager, we plan a follow up questions of How is that person selected? and Who does that person report to?

We think we’re better off concentrating for the moment on the structures/people and then work on the process.   We have a question formulated as “How are community decisions adjudicated?" We thought we wanted to get the “Is there a board/working group/program or both" answered before we asked that one.
> 
>    Brian
>