Re: Specific Questions about Registration details for IETF 108

Jay Daley <> Mon, 08 June 2020 23:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 31DC53A003C for <>; Mon, 8 Jun 2020 16:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Bvy4WtxZsotm; Mon, 8 Jun 2020 16:06:49 -0700 (PDT)
Received: from macbook-pro.localdomain (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 6733D3A003B; Mon, 8 Jun 2020 16:06:49 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Subject: Re: Specific Questions about Registration details for IETF 108
From: Jay Daley <>
In-Reply-To: <ED0D140CAE95FA7851E7389C@PSB>
Date: Tue, 9 Jun 2020 11:06:46 +1200
Cc: IETF <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <FB3BDBCABF6F5FE86E54BF6D@PSB> <> <> <ED0D140CAE95FA7851E7389C@PSB>
To: John C Klensin <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Jun 2020 23:06:51 -0000


> On 9/06/2020, at 7:11 AM, John C Klensin <> wrote:
> Similarly, the LLC Board, as I have understood it, is supposed
> to be responsible for thinking about things strategically and to
> be at least minimally accountable to the community for that
> thinking.  We aren't seeing much evidence of strategic thinking
> and planning that should have, IMO, been well underway in March.
> Instead, we are seeing announcements of fees and associated
> arrangements with the same "emergency", "we have decided", and
> "no time to consult the community, even about principles"
> discussion we saw in March.

I think you are significantly underestimating the level of work that we have had to put into planning in a very short time in response to a global crisis that has taken a new trajectory almost every week.  

One of the first things we had to do was to establish a sound foundation on which to assess if an in-person meeting can go ahead or not - the go/no-go framework.  If you recall, that was not a simple matter and took a lot of work to produce and a fair amount of community engagement.

The second thing was to understand what the community wanted of an online meeting - what it should contain, how it should be structured, when it should operate and so on - without time for the community to deliver that as consensus guidance.  That was addressed through the survey, which was a very large piece of work.  At that stage we needed to know what form of meeting, if any, we were expected to operate before we could work out costs/sponsorship/fees, and so only one question in the survey addressed fees.  (I’m glossing over the different responsibilities of the IESG and LLC in this as they're not relevant to the key points about resourcing and dependencies).

Yes, we could have started earlier to unpick the issues of principle around charging and the practical impact of some of the edge cases, and that’s on me for not being familiar enough yet to understand the need for that.  Other than the one prescient comment on list in March [1] there was no mention of this in the community that might have alerted me otherwise.

Having said that, I’m not sure it would have been wise for the LLC to lead that.  You may have seen from the Many Couches list that a few people including the IETF Chair drafted a proposed charter [2] some weeks ago for a new WG (Stay Home Move Online) to look at all of these issues and provide community guidance to the IESG and LLC, though including fees in the scope came later [3].  This is the best approach by far as the guidance is consensus guidance and because it ensures that we don’t run into a tail-wagging-dog scenario if instead the LLC had led that conversation.



Jay Daley
IETF Executive Director