Re: [Rfced-future] Model proposal

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 07 July 2020 22:55 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 3BE513A0B68 for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 15:55:22 -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, 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 gEZcEYN4aKuG for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 15:55:21 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (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 0558F3A0B65 for <rfced-future@iab.org>; Tue, 7 Jul 2020 15:55:20 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id m22so10329628pgv.9 for <rfced-future@iab.org>; Tue, 07 Jul 2020 15:55:20 -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=dRjpESYLLqrXSR6+jfHFMeVN8LH/s2Tz2vJPNuAQWmo=; b=iiw0DllS2cvyWjrJpgDMGKUJ9HH63nqEAys3ckT6tr+wCjCH994rOWV3qb02CMrMs5 AVPedeX6yX+bUCeX2XdIAcp7l3cBjbuRuG4qmD4XWbuURgaFYPhuHl67IdbST6vI4XM/ VZRPOseVa/w0Ts4+8DxPov1dw+3FaTdkqYJB7d1brcfV04INSCzIsiY61J4ECQfFuTEq dERuVsECw5nW1dA9wnBjfVHG5G387v6PeyeIeyBCMpRJe3z6q5TlDaDjEjELDFLLDN9d 57zcEsIChk3hsXcSeq82Xz4RcxpRMZm050DUMfZNHP58d6Gi3XGtieRLHYon4iH5KH2X HhPg==
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=dRjpESYLLqrXSR6+jfHFMeVN8LH/s2Tz2vJPNuAQWmo=; b=WWHHW03HdJgwnWsValE6R6HnOggCtUAKlJS8hT6peKEEGzcTheNH5czkUTsmrFCwA3 t3zBLuLMiLb4dEg2o3nu8Da6eRXAJp/koxEIuaOV0UObcwwXPNyAWwnkB28zPh87J8Xx EB1ceOFgEcAXki8go+M2XQ2u5MnHUQJQLRYwuEqSf8NCAk+OpaoHu4mm7cTYK/pI77Fi mtFhhMmU1JfUcVOMyVsSOj1R5xwU2iQnAprpyo5BdpQ7y8j4ahcq0PoJ4e8pqX8sVvHe nKyXy7x9lnYIUiFxMNi2lQWkBwFn235LIQsArCgD4xNV2x8ndb5P0Z37y8pxSx9VIqfz QKKw==
X-Gm-Message-State: AOAM532u+VN7Kjzj27ty6ENiQw+p3r/dmQNSkj3WubJeSdEprPPMYA9H dBW6/Du0VgL6xX55cXHHmE8=
X-Google-Smtp-Source: ABdhPJxTn5Egda6w3xK4RfvgPRUVk+oLbAI2Dh36Acre2WeahixJ+NWXWo7n9t2xOusT+bIuZZmm1g==
X-Received: by 2002:a63:cb03:: with SMTP id p3mr46120249pgg.444.1594162520399; Tue, 07 Jul 2020 15:55:20 -0700 (PDT)
Received: from [192.168.43.137] ([118.148.101.145]) by smtp.gmail.com with ESMTPSA id y19sm23779090pfc.135.2020.07.07.15.55.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Jul 2020 15:55:19 -0700 (PDT)
To: Nico Williams <nico@cryptonector.com>
Cc: Eric Rescorla <ekr@rtfm.com>, rfced-future@iab.org, Martin Thomson <mt@lowentropy.net>
References: <d4d1cd2d-6df2-4cb4-b63a-f9bba45b48c0@www.fastmail.com> <51b72823-f2a2-29bd-bd88-f63e13522387@gmail.com> <d1f33279-0656-4caa-81e7-aa665d3a4acb@www.fastmail.com> <CABcZeBMdrfjy+kqQ20MS_1fZrNddff+ycwau5VdC5qAFQN2qVA@mail.gmail.com> <20200707174930.GP3100@localhost> <CABcZeBMGxE6+29_BfNEANjZVJ=0UKFYM+pCp_ECsDw6e2aFMwQ@mail.gmail.com> <37d1d244-ae3f-26db-11c7-d4fcfd25a747@gmail.com> <20200707222803.GV3100@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <5f0ca6a7-7c08-4d7f-0f16-d565632e261b@gmail.com>
Date: Wed, 08 Jul 2020 10:55:14 +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: <20200707222803.GV3100@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/Zuj3ZL7KkOJ5DoTqzZaRCTutlE8>
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, 07 Jul 2020 22:55:22 -0000

On 08-Jul-20 10:28, Nico Williams wrote:
> On Wed, Jul 08, 2020 at 09:45:34AM +1200, Brian E Carpenter wrote:
>> Absolutely I think that community discussion and rough consensus is
>> appropriate for this and other strategy or policy issues. My concern
>> is that this needs to be facilitated and informed by someone with
>> relevant knowledge and experience in the editing/publishing/library/
>> archival world and that is not us. It's certainly not a skill set that
>> the NomCom typically looks for when picking IESG or IAB nominees. It's
>> a skill set that we did look for when appointing the previous RSE.
> 
> The IESG and IAB need, above all, decision-making skills and mastery and
> respect of process.  They have at their disposal, too, a great deal of
> collective expertise from the community, shepherds, directorates, and
> RSE, so they don't necessarily need to be experts in any one area in
> order to make decisions in that area.  Moreover, IAB and IESG members
> tend to have been through the RFC publication gauntlet, so they almost
> necessarily have at least a modicum of publication expertise of their
> own.
> 
> If there's no question that some issues must consume some of their
> attention, then I'm not sure that the IAB performing RSE oversight is a
> problem.

Sadly, I think we did get a demonstration that it can be a problem
last year. However, since we largely seem to agree that separating
out the IT and contract management aspects is the right way to go,
we are transforming the issue quite a bit.

All the same, I believe the actual evidence is that we (engineers)
don't understand the editing/publishing/library/archival world at
all well and we need help.

On 08-Jul-20 10:18, Eric Rescorla wrote:

> Stipulating for the moment that this is true, I don't really see how you get from there to "and this person needs to be in charge of the process". To give an example that I think I also gave on the most recent virtual call, we often have to do things that require a bunch of relevant expertise in the legal world, and that's not us, but address that problem by engaging a lawyer and asking their opinion. Why doesn't that work here?

It might, if we set it up right. I think this is worth exploring.

    Brian