Re: [Rfced-future] **Consensus check on part of Issue 13: Is decision making in the strategy body open to all?**

Michael StJohns <msj@nthpermutation.com> Mon, 30 November 2020 04:21 UTC

Return-Path: <msj@nthpermutation.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 1EA873A0E5F for <rfced-future@ietfa.amsl.com>; Sun, 29 Nov 2020 20:21:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.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 GrOMDaQW2awz for <rfced-future@ietfa.amsl.com>; Sun, 29 Nov 2020 20:21:12 -0800 (PST)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 1AEFE3A0E43 for <rfced-future@iab.org>; Sun, 29 Nov 2020 20:21:11 -0800 (PST)
Received: by mail-qk1-x72f.google.com with SMTP id h20so9783060qkk.4 for <rfced-future@iab.org>; Sun, 29 Nov 2020 20:21:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=1kku8wYCu29W/sJGasAE2zIwnD4pOzxNHMK7BceyNcU=; b=GSfpIGmW3+KEzpnQ3X66ukCBH3n2/ESyrRU8vcMmg4aqlFn4fjgjyCzxH2zXcPChC+ po0FMdTWgX9nnk3hoZuIcK6yDpvXMyEX9Y8MouRbKJkYd4KMtBDRf4gGPSLVc0GTYlsL O5Paqbno/UVY26GG+HU77Y1HzcXpKi7XJCQkceLX/DKXyMlxFWBFlfHt5dDT9pJ1zmsh JXrRfPWWTAiGzGIrAVS0t4suOj4Z4kQLI5kNJY5euQwyF664LD12bwYllHb75AuEBrNl BUwL8i0p2Kexdwc0JLKVjCyNBDeShufFVMruXsE0O6P6/xSA5OBnsR8R+R7gTIFUPlBR cGoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=1kku8wYCu29W/sJGasAE2zIwnD4pOzxNHMK7BceyNcU=; b=I/JIhDwPucJd/wvV9BENuSKwvyfxWdLDyMikZF/DLUB3kIcMzzOxUpTYKPN93DAaFj wbCKg8s8RQ0AnJy7ArloqL8aa4EXh2kofuyQkzfNFLKOxJxmD3uvnZvz6Mmj/2Uro1bt hA61pPjX1r8ZduXz3WI0OjoMy0t9RRNW99G+u5qlTm131a1071dlFk+r2U5CpzI5vjcT IM8aOjIamUEwk4AwQb0G43cKbjshevdVyQi7YChnrv0RzF+R6tfIhtV1dvIat8w1uZQz VofsT67fZwQThGkCggR1r0Ou9tEwmSToTD8HOmYnfW311RO+0q5kscaeJmUipNQGCZ49 nyfA==
X-Gm-Message-State: AOAM532dLBKcM4vivR7XtUCAwlWfWBa2FpzEg7JWGU/A75Io9GqjESAi sYWLM5h4rxQoJ82NtSrzYsx3lV792692rgbt
X-Google-Smtp-Source: ABdhPJxAbFb1BIORD+fW44+4/QJ3yMp1SXgPr9Ozu0+gkkQsAlQts+2tVG75gMNj1hv+4lY4F6m5Yg==
X-Received: by 2002:a05:620a:164b:: with SMTP id c11mr20761250qko.203.1606710070355; Sun, 29 Nov 2020 20:21:10 -0800 (PST)
Received: from [192.168.1.23] (pool-108-28-189-254.washdc.fios.verizon.net. [108.28.189.254]) by smtp.gmail.com with ESMTPSA id r1sm9223831qta.32.2020.11.29.20.21.09 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 29 Nov 2020 20:21:09 -0800 (PST)
To: rfced-future@iab.org
References: <5EE071CB-30CA-474F-BFA5-45129FFFFCBA@cisco.com> <3689021a-b3b2-0baa-7463-45b677c72846@joelhalpern.com>
From: Michael StJohns <msj@nthpermutation.com>
Message-ID: <643805e0-cc17-45e8-c945-bc2c0ba88b8f@nthpermutation.com>
Date: Sun, 29 Nov 2020 23:21:08 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <3689021a-b3b2-0baa-7463-45b677c72846@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/mpqOo23YkJJwV7UkiD-gf0-kSK4>
Subject: Re: [Rfced-future] **Consensus check on part of Issue 13: Is decision making in the strategy body open to all?**
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, 30 Nov 2020 04:21:17 -0000

Hi Eliot -

I align strongly with Joel's view below.

I also don't believe that your third point is well stated - instead:

I believe "that there is consensus that the strategic body engages with 
the community, solicits its input, allows for observation of the 
decision process, and provides documentation of such decisions".   E.g. 
how the IESG, IAB and LLC generally operate - can listen on the call, 
and might be able to ask questions at the end, but not be part of the 
discussion for decisions taken (at least unless asked by the strategic 
body).

I do not believe there is consensus on "engage openly with the body" 
which I take to mean "everyone gets to participate as an equal and is a 
decision maker for the strategic body".

I believe there is no consensus on the set of decision makers yet.   My 
personal belief follows Joel's statement:  "if this [strategic] body 
[open to everyone] owns the whole strategic task, I think what you 
describe is a recipe for failure over time".

Mike


On 11/27/2020 4:05 PM, Joel M. Halpern wrote:
> I do not understand the third point below.
> If the strategic body is open to everyone to participate in, then that 
> seems to be the answer to "how is it composed".
>
> With a stronger senior technical publishing advisor than we seem to be 
> moving towards, I can see how that can work.  But if this body owns 
> the whole strategic task, I think what you describe is a recipe for 
> failure over time.
>
> Sure, we can make it work for a while.  We are making the current 
> setup work for a while.  But our goal is a long term structure, and I 
> just don't see it working well.  Given the number of working groups I 
> have seen where strong differences in philosophy have practically 
> paralyzed the working group, combined with the strong differences in 
> philosophy I have seen in this group, I have trouble getting my head 
> around how this is expected to actually work.
>
> Having said that I will reiterate that having a means for community 
> participation that is a serious part of the process seems to me to be 
> a good thing.  I am not saying "go away and let the experts do this 
> behind closed doors."
>
> Yours,
> Joel
>
> On 11/27/2020 10:39 AM, Eliot Lear wrote:
>> Please let us know in within the next three weeks if you disagree 
>> with any of the following:
>>
>> • The chairs think that everybody agrees that there is some strategic 
>> body
>>
>> • The chairs think that strategic decisions get documented in RFCs
>>
>> • The chairs think that there is consensus that the strategic body is 
>> open to all to engage openly, and that meetings should be open, 
>> minuted, agendas posted.  This is not to say that there is consensus 
>> about how the strategic body is composed.
>>
>> These points obviously do not close Issue 13.
>>
>>
>