Re: Extended: Consultation on IETF LLC Draft Strategic Plan 2020

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 12 May 2020 23:14 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8DE33A0C6A; Tue, 12 May 2020 16:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=cs.tcd.ie
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 Px3HQHT97RbO; Tue, 12 May 2020 16:14:08 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A8D43A0C61; Tue, 12 May 2020 16:14:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 23A9CBE20; Wed, 13 May 2020 00:14:06 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xu32_9FGX7JX; Wed, 13 May 2020 00:14:03 +0100 (IST)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 633C7BDCF; Wed, 13 May 2020 00:14:03 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1589325243; bh=7xpGH1Pk1hCkKUKU05C53rIz0OCBhR8M2JP124B1CIs=; h=To:Cc:References:From:Subject:Date:In-Reply-To:From; b=LUxkbkNhcnCrStXzO7uaauOPSoZGbx6PmYDAMkjKTbO0DQuy64OE0qlACV6WdWtOE fit9aTqFq+aeftzzOH7mWrwJpQZJHZOGU7TWKQbesy3G+lFkJpRuuEpl7hTKvFamca Y0DEpXK+921wn5n2nc783BRwDmDQieLzQ8oKbwQ0=
To: Pete Resnick <resnick@episteme.net>
Cc: Jay Daley <jay@ietf.org>, ietf <ietf@ietf.org>
References: <158924936047.27653.16895891130229666110@ietfa.amsl.com> <92ddbd6e-4b9f-a474-242e-668bd26582fe@cs.tcd.ie> <F5FF5DCC-67A8-410A-912D-6E31E1FF70C7@ietf.org> <07d1133a-a10c-3845-3a39-9e16faf59b24@cs.tcd.ie> <BE422D01-D5BD-4C0C-BDCF-C3023647281E@episteme.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Autocrypt: addr=stephen.farrell@cs.tcd.ie; prefer-encrypt=mutual; keydata= mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh 5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+ QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKr EMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZU bUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqO Vz+7L+WiVfxLbeVqBwV+4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJg b097ZaNyuY1ETghVB5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k 4LyM2lp5FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK 7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5Xi HzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQABtDJTdGVwaGVuIEZh cnJlbGwgKDIwMTcpIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPokCQAQTAQgAKgIbAwUJ CZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUCWj6jdwIZAQAKCRBasvrxexcr6o7QD/9m x9DPJetmW794RXmNTrbTJ44zc/tJbcLdRBh0KBn9OW/EaAqjDmgNJeCMyJTKr1ywaps8HGUN hLEVkc14NUpgi4/Zkrbi3DmTp25OHj6wXBS5qVMyVynTMEIjOfeFFyxG+48od+Xn7qg6LT7G rHeNf+z/r0v9+8eZ1Ip63kshQDGhhpmRMKu4Ws9ZvTW2ACXkkTFaSGYJj3yIP4R6IgwBYGMz DXFX6nS4LA1s3pcPNxOgrvCyb60AiJZTLcOk/rRrpZtXB1XQc23ZZmrlTkl2HaThL6w3YKdi Ti1NbuMeOxZqtXcUshII45sANm4HuWNTiRh93Bn5bN6ddjgsaXEZBKUBuUaPBl7gQiQJcAlS 3MmGgVS4ZoX8+VaPGpXdQVFyBMRFlOKOC5XJESt7wY0RE2C8PFm+5eywSO/P1fkl9whkMgml 3OEuIQiP2ehRt/HVLMHkoM9CPQ7t6UwdrXrvX+vBZykav8x9U9M6KTgfsXytxUl6Vx5lPMLi 2/Jrsz6Mzh/IVZa3xjhq1OLFSI/tT2ji4FkJDQbO+yYUDhcuqfakDmtWLMxecZsY6O58A/95 8Qni6Xeq+Nh7zJ7wNcQOMoDGj+24di2TX1cKLzdDMWFaWzlNP5dB5VMwS9Wqj1Z6TzKjGjru q8soqohwb2CK9B3wzFg0Bs1iBI+2RuFnxLkCDQRaPVAyARAA+g3R0HzGr/Dl34Y07XqGqzq5 SU0nXIu9u8Ynsxj7gR5qb3HgUWYEWrHW2jHOByXnvkffucf5yzwrsvw8Q8iI8CFHiTYHPpey 4yPVn6R0w/FOMcY70eTIu/k6EEFDlDbs09DtKcrsT9bmN0XoRxITlXwWTufYqUnmS+YkAuk+ TLCtUin7OdaS2uU6Ata3PLQSeM2ZsUQMmYmHPwB9rmf+q2I005AJ9Q1SPQ2KNg/8xOGxo13S VuaSqYRQdpV93RuCOzg4vuXtR+gP0KQrus/P2ZCEPvU9cXF/2MIhXgOz207lv3iE2zGyNXld /n8spvWk+0bH5Zqd9Wcba/rGcBhmX9NKKDARZqjkv/zVEP1X97w1HsNYeUFNcg2lk9zQKb4v l1jx/Uz8ukzH2QNhU4R39dbF/4AwWuSVkGW6bTxHJqGs6YimbfdQqxTzmqFwz3JP0OtXX5q/ 6D4pHwcmJwEiDNzsBLl6skPSQ0Xyq3pua/qAP8MVm+YxCxJQITqZ8qjDLzoe7s9X6FLLC/DA L9kxl5saVSfDbuI3usH/emdtn0NA9/M7nfgih92zD92sl1yQXHT6BDa8xW1j+RU4P+E0wyd7 zgB2UeYgrp2IIcfG+xX2uFG5MJQ/nYfBoiALb0+dQHNHDtFnNGY3Oe8z1M9c5aDG3/s29QbJ +w7hEKKo9YMAEQEAAYkCJQQYAQgADwUCWj1QMgIbDAUJCZQmAAAKCRBasvrxexcr6qwvD/9b Rek3kfN8Q+jGrKl8qwY8HC5s4mhdDJZI/JP2FImf5J2+d5/e8UJ4fcsT79E0/FqX3Z9wZr6h sofPqLh1/YzDsYkZDHTYSGrlWGP/I5kXwUmFnBZHzM3WGrL3S7ZmCYMdudhykxXXjq7M6Do1 oxM8JofrXGtwBTLv5wfvvygJouVCVe87Ge7mCeY5vey1eUi4zSSF1zPpR6gg64w2g4TXM5qt SwkZVOv1g475LsGlYWRuJV8TA67yp1zJI7HkNqCo8KyHX0DPOh9c+Sd9ZX4aqKfqH9HIpnCL AYEgj7vofeix7gM3kQQmwynqq32bQGQBrKJEYp2vfeO30VsVx4dzuuiC5lyjUccVmw5D72J0 FlGrfEm0kw6D1qwyBg0SAMqamKN6XDdjhNAtXIaoA2UMZK/vZGGUKbqTgDdk0fnzOyb2zvXK CiPFKqIPAqKaDHg0JHdGI3KpQdRNLLzgx083EqEc6IAwWA6jSz+6lZDV6XDgF0lYqAYIkg3+ 6OUXUv6plMlwSHquiOc/MQXHfgUP5//Ra5JuiuyCj954FD+MBKIj8eWROfnzyEnBplVHGSDI ZLzL3pvV14dcsoajdeIH45i8DxnVm64BvEFHtLNlnliMrLOrk4shfmWyUqNlzilXN2BTFVFH 4MrnagFdcFnWYp1JPh96ZKjiqBwMv/H0kw==
Subject: Re: Extended: Consultation on IETF LLC Draft Strategic Plan 2020
Message-ID: <24c8d567-1aaf-8b50-149a-d7b0cfbf47a8@cs.tcd.ie>
Date: Wed, 13 May 2020 00:14:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <BE422D01-D5BD-4C0C-BDCF-C3023647281E@episteme.net>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="ME34454P051W0NVuSLGKvbjEaInjwc8N4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iXrFvmZ8Py_6uUiLZizsLq0mWpw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 23:14:11 -0000

Hiya,

On 12/05/2020 23:38, Pete Resnick wrote:
> Hi Stephen,
> 
> On 12 May 2020, at 16:06, Stephen Farrell wrote:
> 
>> ... overall I think the text is overlong and overreaches
>> in ways that could lead to the LLC setting policies for the
>> IETF. That isn't ok. Sorry to be so negative but I think
>> this would be best refactored down to something much
>> smaller and that very carefully doesn't accidentally put
>> the LLC into a position of controlling what the IETF does.
>> I make specific comments below, but would suggest those not
>> be used for wordsmithing, but rather that this document be redone
>> starting afresh.
> 
> Caveat that Jay can (and should) state his own view on the matter: While
> I agree with you that some of the items in the document are beyond the
> scope of what the LLC ought to be doing (some of them are variants of
> things I mentioned in my message and that others have mentioned as
> well), I don't think on the whole the document structure is an overreach
> or needs to be redone from the beginning. But maybe there are some of
> your statements that I don't understand. Trimming as I go on the items
> which seem like reasonable edits or that are overreaches with which I
> simply agree (or have no strong objection):
> 
>> - "As the IETF LLC is a support organisation to the
>>   IETF/IRTF/IAB, the strategic goals should ideally reflect
>> their strategic goals." As written, this makes no sense to me,
>> given the IETF lacks strategic goals.
> 
> We don't? 

I don't know the URL or RFC number for the current set
of "IETF strategic goals," so I think, no, we do not.

> Is "creating useful Internet standards" not a strategic goal?

I don't think it is really, in this context. Presumably
many of us would also like "processes that don't take
forever" and that'd be in conflict with your putative
goal above from time to time and topic to topic. The IETF
hasn't said how to balance those so I don't think the LLC
can take a position on where we might land. (It may be a
fine outcome of this process to identify things the IETF
can and ought strategise about I guess.)

> Perhaps "meeting in plenary 3 times a year to advance our work on
> Internet standards" is too tactical, but it's some sort of goal, and the
> output of MTGVENUE seemed a bit strategic. We don't have a "strategic
> plan" of the sort that the LLC seems to be creating for themselves, but
> I feel like maybe we do have some stated strategic goals from time to time.

So the LLC gets to randomly pick the (parts of the)
BCPs it would like to map to an "LLC strategy"? It's
not that I mistrust anyone - I just don't think that
is an ok decision to put upon the LLC.

> 
> But even if we don't, couldn't this be fixed to simply say that the
> LLC's strategic goals should be set to reflect IETF/IRTF/IAB expressed
> administrative needs and desires?

Maybe. But that raises the concern that the LLC, being
better organised with a strategy starts to determine the
"administrative needs and desires" of the IETF. I do
like the idea the LLC has longer term plans, but those
need to be carefully scoped/constrained.

> 
>> - "To secure long-term funding for the LLC/IETF/IRTF/IAB that is
>>   more than sufficient to meet their plans." What plans?
> 
> I assumed our plans included meeting a few times a year in plenary,
> having technology to do online interim meetings, having tools to manage
> our documents and standards activities, etc. Isn't that what we want the
> LLC to secure long-term funding for?

I'm not clear we have those plans for 2025. In 2010 it
would have been clearer that we probably did have those
plans for 2015 but I'm not sure it remains the case.
(That's not a covid-related change, I think our current
modus operandi has been becoming less defensible for a
while.)

> 
>> - "To rapidly mature the IETF LLC into an organization..." that
>>   reads to me like a statement I'd see in the usual commercial
>> "take over the world" kind of plan.  I hope we have as a goal
>> that the LLC be lean, and not bloated. Where is that represented
>> here?
> 
> Being "mature" does not seem incompatible with being "lean".

There is no sense in the document that "lean" is a goal.
There is a stated desire to dominate.
I'm unkeen on the latter myself and very keen on the
former.

>> - "The focus currently is very much on developing capability and
>>   capacity" that reads to me as if there is a desire for a
>> bigger LLC and not for a lean LLC.
> 
> I think that was stated as the current problem, not the desire.

Kinda the same point as the one above, but I was more
reacting to "build capacity" as a desire, and interpreting
that to maybe mean "bigger LLC" is good.

> 
>> - Transformation#1 seems to me to imply the LLC tells the IETF
>>   what to do.  That isn't acceptable. I don't believe it's the
>> LLC's job to try "fix" the IETF in terms of (our lack of)
>> strategy. The stated result is not possible, as none of the
>> IESG, IRSG  nor IAB can set strategic objectives for 5 years
>> time and the community has not given those bodies any such
>> strategic objectives.
> 
> This one I truly don't get. The transformation (the "To" part) sounds
> like it's saying, "Talk to the IESG/IRSG/IAB and make sure that the
> LLC's objectives align with theirs", not fixing their objectives. Even
> if those bodies don't have 5 year time horizons on their objectives,
> nothing says that the LLC can't try to figure out what it's 5-year goals
> will be based on what the IESG/IRSG/IAB are saying about their next year
> or two. I just don't see the implication you're seeing. Can you explain
> how you got there better?

I can try. I think the IESG (for example) can't set itself
goals/objectives for 2025 because of how we setup the
nomcom process. That's a good thing with undesirable
consequences for longer term planning. If the LLC set
itself a goal/objective for 2025 in agreement with the
2020 IESG, and then tell the 2024 IESG "no, you can't
do <y> because the 2020 IESG agreed with us to do <x>"
then I think that's giving power and initiative to the
LLC that isn't what we intended when setting up the LLC.
There need to be somewhat well-defined limits to the
kinds of policy/strategy/goal/objectives we're dealing
with here to ensure that doesn't happen for damaging
cases. There isn't  really anything in the current text
that envisages such limits.


> 
>> - "Clear, strongly supported and well articulated value
>>   proposition for the IETF/IRTF/IAB that supports all our
>> engagements." That reads to me like marketing gibberish (hey,
>> I'm an academic:-) but if such a thing is needed, it is not up
>> to the LLC to drive that process.
> 
> I thought this meant that the LLC should have a clear sales pitch to
> (e.g.) potential funders about what's good about the IETF/IRTF/IAB. I
> think the LLC is the right group to do that. Is that not how you read it?

I don't read "all our engagements" as being limited to
"pitching to funders." The current text could be read to
allow/encourage LLC staff going around promoting the IETF
at random trade shows. If what's intended is much more
limited, then the text needs to reflect that.

> 
> I suspect that the answer(s) to the above questions will help me figure
> out why I think there are just a bunch of important edits whereas you
> think this needs a major restructuring or rewrite. But I'm not seeing it
> at the moment.

TBH, I think there are so many mismatches that a restart
may be better. I can totally get why Jay would like the
LLC to have sensible longer term plans, but I think those
need much more careful framing to help preserve some parts
of what's good about the IETF setup. I further assume
we all share preservation of such things, or better, as a
goal. (Though merely being preserved isn't a super-
attractive sounding goal:-)

Cheers,
S.


> 
> Cheers,
> 
> pr