Re: "Management team"

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 20 April 2020 03:34 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 6DC993A0DE1; Sun, 19 Apr 2020 20:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[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, URIBL_BLOCKED=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 gxHFnFPas2KO; Sun, 19 Apr 2020 20:34:15 -0700 (PDT)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 DBBDE3A0DDF; Sun, 19 Apr 2020 20:34:15 -0700 (PDT)
Received: by mail-pj1-x1035.google.com with SMTP id t40so3835606pjb.3; Sun, 19 Apr 2020 20:34:15 -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=xOMZ+zzIcsPZ7Ir6ui332lGQ6ZW3XKMJ3Pt7GDktAcc=; b=lHwoMlhpGZGvvt8UAK/b3cu+9dukgkriEdLG5GvweOfIAjGml5KJJO73d83nw5x714 ftpyEZmynjuEUQ/f8R9EnnfMn/8HepMOLox5qQcil91gJhh1fgN2C7dLVewbf8VAwrE0 Phs8n0cu8wVEzHTIxgBQIY/WVu1tmFCeZvsxkrOWWoHG76Vssw3o4YbFflX8M91lNcjA n1oFDavJSAJGUZaE9fcXC/ytJTtzyxhBkBJwfwXWpuLoYpV+V6gMp34OdIgTtFhTdgon YlMREUwTZFV9C3Eppk8vj6AETAurZEsREmjfKCDQgH9T13noU5/sbuiTntmIl3w/YfUf u9SQ==
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=xOMZ+zzIcsPZ7Ir6ui332lGQ6ZW3XKMJ3Pt7GDktAcc=; b=ud4O2jpBrATPWxqHCkWvG18FRQysQpnqVn2h/er9K4CrUH03helc/wcHBBXaRxBMYC 9iy0D74wKMSROGqFqjR04Inc/ynuyOb/dUjqx9rKINYVgOxLn8ZQ16ucoKInCBEt5CB7 kjjdT+p6W2F8Jm/TYm92bKlOAxfELRm/8oBQiJ2z6jtviqU/21GcsH2n2GLOfy7EFg65 qz/dkRk5LGOktqcOTBthYwWDAbsNQ8/CYI1HVrvUYJlCApRDNUpRZKO0WSuzxWpavsex 97UojgCxRdWDO1gHl1+3lOmneE8Mw4qGG0hQQoICVRDhWGiloahr0emsiXWhKbgG4gYJ sYzA==
X-Gm-Message-State: AGi0PubuBfEALtWZ47hecRdRrQpssG52f1ZCc1byKn9BUxBcov+Yq2ps EZdykKsTqfTsTz+B0t1Ttq2wFOt/
X-Google-Smtp-Source: APiQypJ/D8llTeyv1sksbU5A7ufgmThMApL/AEzfYiBzXJWS7gkowMvx5/ffnONepIldwS4Eqrzwrg==
X-Received: by 2002:a17:902:d34a:: with SMTP id l10mr2654511plk.234.1587353654893; Sun, 19 Apr 2020 20:34:14 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.25.143]) by smtp.gmail.com with ESMTPSA id x7sm11110363pfn.165.2020.04.19.20.34.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Apr 2020 20:34:14 -0700 (PDT)
Subject: Re: "Management team"
To: Jay Daley <jay@ietf.org>, John C Klensin <john-ietf@jck.com>
Cc: IETF <ietf@ietf.org>
References: <47A0EEE1BBB8EF41FD8B07E0@PSB> <26FF91F9-CD44-4045-991E-AF21A7208622@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <03339c63-8ef9-1ac8-d75f-b8e5391b0337@gmail.com>
Date: Mon, 20 Apr 2020 15:34:09 +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: <26FF91F9-CD44-4045-991E-AF21A7208622@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PmF5ZaQXTHfonYyae-TxsHgCCMg>
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: Mon, 20 Apr 2020 03:34:19 -0000

Jay,

The IETF has never had a manager (a.k.a. king or president) or anything resembling a CEO, and that didn't change in any of the documents, either the ones that originally created IASA or the recent ones that created IETF LLC. But in reality, whoever is running the administration (previously the IAD, and now the IETF LLC ED) has to go somewhere for decisions that are out of his or her scope. And where can they go except the steering group and its Chair? They are empowered to judge IETF consensus, and to judge when a decision needs IETF consensus.

I don't think any of that is news. What is a bit different is that for IETF 107, there really wasn't much time, and certainly not time for a long discussion on this list, so that a well-defined rough consensus could emerge. So decisions had to be made a bit hurriedly. I think that for IETF 108 and the big decisions about how to go forward in the next couple of years, there should be discussions here. But it's still the IESG and Chair that have to extract a rough consensus, and for some decisions there are hard deadlines.

(I haven't mentioned the IRTF, but the argument should be symmetric.)

Regards
   Brian Carpenter

On 20-Apr-20 12:57, Jay Daley wrote:
> John
> 
> Another way of looking at this is that the IESG have a set of responsibilities (delegated authorities if you prefer) as does the IETF Executive Director and as does the IRTF Chair, and if those get together to coordinate on how they do their work and do not exceed any of their responsibilities then why does that need a label or formal recognition?  Or is it your view that a) the responsibilities have been exceeded; or b) this type coordination across roles needs community consensus approval before it is allowed to happen?  Your note implies b) rather than a) which seems surprising so I suspect I’m just missing a nuance.
> 
> Jay
> 
>> On 20/04/2020, at 12:10 PM, John C Klensin <john-ietf@jck.com <mailto:john-ietf@jck.com>> wrote:
>>
>> Hi.
>>
>> In a note I posted to this list under an hour ago, I used the
>> term "management team".  I hope no one was offended by that as I
>> didn't mean any offense, only to describe something I see
>> unfolding.
>>
>> Under normal circumstances, the IETF has prided itself on making
>> decisions bottom-up.  Several aspects of that principle have
>> come up on this list in recent months including discussions of
>> where proposals for WGs should originate, discussions of how the
>> IESG interacts with the community, and so on.   In emergencies
>> and when tight deadlines suddenly arise, we generally allow
>> various leadership bodies, notably the IESG, a good deal of
>> flexibility to Do the Right Thing rather than failing to deal
>> with the emergencies or deadlines because we get too entangled
>> with procedures.   IMO, the decision to cancel the f2f meeting
>> of IETF 107 and instead take it "virtual" (online) was just one
>> such emergency, one that the IESG sensibly dealt with by
>> organizing a small team that consisted of its members, the IRTF
>> Chair, and, presumably the IETF (LLC) Executive Director,
>> consulting whichever WG Chairs and maybe other that they thought
>> reasonable to consult, and then made and announced a decision.
>>
>> However, it seems to me that we should now be returning to
>> normal, even if it is only a new, or even temporary, normal.  If
>> so, it is legitimate for the community to ask (or be asked)
>> whether it agrees with who is being included or excluded from
>> decision processes like that and who is making the decisions
>> more generally.  That is clearly not the IESG alone, it is
>> presumably not the Executive Director alone.  But, to the extent
>> to which a new body or group is being set up --one that, given
>> the nature of these decisions, I think resembles a management
>> team -- maybe the IETF community should be consulted about its
>> organization and structure.    I don't recall anything in the
>> IASA2 or LLC documents that says the community has turned that
>> authority over to any other body, explicit or ad hoc even though
>> it is clear that, in both the IASA and IASA2 decisions, the
>> community decided that it wanted to get out of decisions on
>> day-to-day operations, contracts, and administrative procedures.
>>
>> I also think is is entirely plausible that, if consulted, the
>> community will decide that the current apparent decision-making
>> structure is just right; I'm only suggesting that some
>> consultation is in order.
>>
>> Or maybe I'm the only one who cares about these things, in which
>> case apologies for wasting people's time.
>>
>> best,
>>    john
>>
> 
> -- 
> Jay Daley
> IETF Executive Director
> jay@ietf.org <mailto:jay@ietf.org>
>