Re: Registration details for IETF 108

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 02 June 2020 17:15 UTC

Return-Path: <hallam@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 595DB3A0CB2; Tue, 2 Jun 2020 10:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 LcZzfb86xPNY; Tue, 2 Jun 2020 10:15:21 -0700 (PDT)
Received: from mail-ot1-f48.google.com (mail-ot1-f48.google.com [209.85.210.48]) (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 7F2963A0CBE; Tue, 2 Jun 2020 10:15:21 -0700 (PDT)
Received: by mail-ot1-f48.google.com with SMTP id o7so7055900oti.9; Tue, 02 Jun 2020 10:15:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E0z4f9CUv9BmX5H3JQwfkwnFfTIBHYlelfKu32Dsr5w=; b=i/fG1m3TWQNymu9XJIKys9mlRs/6edEy+4+4OiQxR3ifmanq28b05ckXuZDZMKu0/p mYlW9t+HdzCKdoH1QbpZSmBE5FFCZpTPc7jpxRY5q2yDwfTT74eI+5RcSWFz2Gvy5BZh m26hBE1JwLIEw6PBzzUYwTo55VP/sc3UtlFkLo9jG8mEwUM5kpoXVGK3Jls72076rjQL pqS70JzVjsne8fmot09huF7I1KDbZQYHm6CtAtHHLOkRBhw9WKNIp4MPtSmiZU/JRRMe mJFqtaUpK6iX/jlYDbUrwPTQCYPzgmLQLXuFAkP6uIiomOA58oB0VPqMrvGPGsCKqN92 fULQ==
X-Gm-Message-State: AOAM530TrtCxisWQX/isQ77OVYsrySUxztm+AwtEg7OLF1jkaHojkjmK NxmzxYd73yCle3k8YYlk6Dklg34LKrd9EUdzKtY=
X-Google-Smtp-Source: ABdhPJxKeAnOxDyHG2QYjOA9UWIrSOxzbEj4iUqHnxpka8hLzfZWTHZlAYncY/mriSLxFJa6adUUSNFDYRLWKiIsPM8=
X-Received: by 2002:a9d:220c:: with SMTP id o12mr236929ota.155.1591118120653; Tue, 02 Jun 2020 10:15:20 -0700 (PDT)
MIME-Version: 1.0
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6.2.5.6.2.20200531121457.0b249858@elandnews.com> <CABcZeBOzVHaSZa0A3eDz12RwNuCiHtiJL8wqvAhhLPN6YEQOkQ@mail.gmail.com> <afa11959-3348-4054-409c-803824a2f332@gmail.com> <b31bc70b-cc73-45e4-9449-d85313a88037@gmail.com> <f1d15bec-080a-7726-1921-8a06949b231f@cs.tcd.ie> <8f464404-5278-8178-66e5-44eaed748141@gmail.com> <5B1FD06B-BC4F-49E0-97A2-DF8A48CC24FB@cooperw.in> <e1044eb4-68be-1f36-eff5-f2d60e6d1ff9@gmail.com> <F6B24ECC-7969-4D72-92A3-DA6C2E47BF66@cs.ucla.edu> <CAOj+MMHmWnfXo4rYTxEvQ6LspMHxSo26DqZrLBin-7Wa-Dqs+w@mail.gmail.com> <D2FB84F2-2FD5-4091-BB70-580F4545FFF4@ietf.org> <96d361c2-de64-8966-60a6-bad1763af790@cs.tcd.ie> <680AEF9F-7733-4957-805D-FB90C1E099B8@ietf.org> <CAKKJt-d7UPOvxAVZivcuTEc=V8SPMchD9qL2J5SBCbAZDH7ZyQ@mail.gmail.com>
In-Reply-To: <CAKKJt-d7UPOvxAVZivcuTEc=V8SPMchD9qL2J5SBCbAZDH7ZyQ@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 2 Jun 2020 13:15:08 -0400
Message-ID: <CAMm+LwhUCSYajyVY_oZn2pFTM6SKs69JweUfX=eNM_8wDX7xyw@mail.gmail.com>
Subject: Re: Registration details for IETF 108
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Jay Daley <jay@ietf.org>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000060998e05a71d0e6a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/81Zy6d7CXdqintX-FWoN7K1N3ks>
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, 02 Jun 2020 17:15:23 -0000

On Tue, Jun 2, 2020 at 12:41 PM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> To the community, not just to Jay,
>
> I'm current on the mail thread as of when I hit "reply all", but am
> replying here because that's point in the discussion I had an opinion
> about.
>
> On Mon, Jun 1, 2020 at 5:50 PM Jay Daley <jay@ietf.org> wrote:
>
>>
>>
>> On 2/06/2020, at 10:39 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
>> wrote:
>>
>>
>> Hiya,
>>
>> On 01/06/2020 23:14, Jay Daley wrote:
>>
>> Would it still apply when onsite meetings start to happen ?
>>
>> No decision has been made about that.
>>
>>
>> Would it be sensible to promise/ensure that a community
>> discussion that determines direction, within the bounds
>> of practicality, precedes, rather than follows, that
>> decision? FWIW, I think it would and it's important that
>> that be the case. IOW, let's sort out our approach to
>> this before the timeframe of IETF109.
>>
>>
>> It would be excellent if that could happen.
>>
>
> Speaking only for myself, my IETF 107 wasn't actually canceled all at
> once, but enough working group chairs and research group chairs canceled
> meetings that I probably should have requested refunds then, instead of
> waiting for the IESG's pronouncement. I might have still gone to Vancouver
> if the IESG hadn't canceled the face-to-face meeting, but it would have
> been to show support for the organization, not to get specific work done.
>
> See the discussion about whether working groups have an incentive to meet
> during IETF virtual meeting weeks for more details, but the community
> really does have a lot of influence on the decision to resume in-person
> meetings, whether anyone else thinks they do, or not.
>
> So, I'm reading Stephan's point about IETF 109 as "if the community is
> going to have an opinion about whether IETF 109 is virtual, we should
> probably start that discussion, like, now". Did I misread that?
>
> If I'm good so far, my questions are
> on this mailing list, or elsewhere?
> who's sending the first e-mail to start the discussion?
>

There is a discussion of sorts on manycouches. I don't quite have time for
that at the moment (working on a technical proposal).

Having a discussion of anything related to IETF 108 is pointless because
there were no real decisions to be made. Discussion of 109 seems much more
to the point as there are still options open.

The constraint with 109 is that while the IETF can decide NOT to have the
meeting, it cannot decide that it will. There are too many other factors
involved. Not least among them the likelihood that many of us may be
unemployed by then. The notion that the winds blowing through the rest of
the economy won't affect tech seems somewhat optimistic to me.

What we can usefully discuss is:

* Is it better to decide to cancel now rather than continue in an uncertain
state.?
* Does it make sense to concentrate meetings in a single week with the
inevitable scheduling conflicts that then arise?
* What sort of work does and does not work at remote meetings?
* How far do we want the IETF community to extend?

The last one is something that I think people should think about seriously.
One of the big drawbacks to IETF for many network related groups was the
cost of participation: Three in person meetings a year. Thats more than
most folk working on open source apps can afford.

Consider the following scenario: IETF moves to schedule with one in person
meeting and two virtuals a year with most of the WG effort taking place in
bi-weekly interims. At that point the cost of participation in IETF is
lower than OASIS or W3C. And maybe IETF becomes an attractive venue for a
lot of efforts that it isn't attractive for at the mo.

And that then gets us into further consideration of the role of the
secretariat, IESG, RFCs and so on. How much control do we actually want?
The IETF is rather strange in that the constitution gives the IESG the
highest level of direct involvement in WG decisions and the least
accountability to the membership (none, the membership cannot appoint or
remove and isn't even recognized as a membership).

Now we are at the point where it is impossible to carry on as in the past,
it seems now is a good time to think about how we think we should carry on.