Re: [Ietf108planning] Registration open for IETF 108

Pete Resnick <resnick@episteme.net> Thu, 11 June 2020 18:35 UTC

Return-Path: <resnick@episteme.net>
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 0CFD03A0D61; Thu, 11 Jun 2020 11:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 h7cyC0pdvkpK; Thu, 11 Jun 2020 11:35:20 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2E853A0D29; Thu, 11 Jun 2020 11:35:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 17678B049464; Thu, 11 Jun 2020 13:35:16 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id he4NP6Yrstrp; Thu, 11 Jun 2020 13:35:11 -0500 (CDT)
Received: from [172.16.1.10] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 65D6FB04944B; Thu, 11 Jun 2020 13:35:11 -0500 (CDT)
From: "Pete Resnick" <resnick@episteme.net>
To: "tom petch" <daedulus@btconnect.com>
Cc: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>, "Jay Daley" <jay@ietf.org>, ietf <ietf@ietf.org>, ietf108planning@ietf.org
Subject: Re: [Ietf108planning] Registration open for IETF 108
Date: Thu, 11 Jun 2020 13:34:46 -0500
X-Mailer: MailMate (1.13.1r5683)
Message-ID: <4196EDE2-E81A-4E9B-A78C-37CE89231857@episteme.net>
In-Reply-To: <1UWB5RhEL2.1bMPW5hKaR9@pc8xp>
References: <159166311543.4506.736406779378278905@ietfa.amsl.com> <B4293B17-6F83-4B9E-89BF-C0B1388F346F@cable.comcast.com> <CABmDk8=gxXiQ60hpdCNB6jK0EG_ssAQnzjgJp=c9yXNKabHKeA@mail.gmail.com> <CABmDk8mwVfWZQmBwZ9c4xaoStwv7CeRRceihTR846iq_LYPFFw@mail.gmail.com> <F6BFB099-2526-4EEB-A267-F2A1D0A7DDFB@cooperw.in> <35fb0076-a240-096a-de7f-280d5e7ad1e3@cs.tcd.ie> <2F0FDD2B-03C8-4E76-9149-A2666147C66E@csperkins.org> <27875646-243d-8d03-b588-866b883fea7c@cs.tcd.ie> <8C935847-70C8-439B-8F4C-83DB9A43E4DF@ietf.org> <c1b11160-c50b-9434-6ba8-9ec587a17743@cs.tcd.ie> <1UWB5RhEL2.1bMPW5hKaR9@pc8xp>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iy7BR-DT7gGSg9pEP2jznOCfDsA>
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: Thu, 11 Jun 2020 18:35:23 -0000

On 11 Jun 2020, at 11:37, tom petch wrote:

> Looking at RFC8711 I see
>
> "7.5. IETF Meeting Revenues
> Meeting revenues are another important source of funding that
> supports the IETF, coming mainly from the fees paid by IETF meeting
> participants. The IETF Executive Director sets those meeting fees,
> in consultation with other IETF LLC staff and the IETF community,
> with approval by the IETF LLC Board. Setting these fees and
> projecting the number of participants at future meetings is a key
> part of the annual budget process."
>
> Elsewhere in that cluster of RFC that came out in February, in the 
> context of venue, it explicitly calls out the need for consensus as 
> declared by the IETF Chair.  Here there is no call for consensus.  If 
> the IETF had wanted more control then it should not have approved 
> RFC8711:-)  I think that Jay was well within his rights to take the 
> actions he did.

Tom, it was made pretty clear in the discussion of RFC 8788 that when 
the IETF referred to "meetings", it did not have in mind the idea of an 
entirely remote meeting. Similarly, in the same cluster as 8711, neither 
8718 nor 8719 anticipates the idea that a meeting would be held with no 
"location" or "venue" at all. So to say of 8711 that 7.5 clearly 
anticipates entirely online meetings is a bit of a stretch. It doesn't 
absolutely conclude otherwise, but the discussion of 8788 should have 
been a pretty good hint that the community would have been surprised by 
the interpretation, and the better course would have been to ask the 
community what it intended by the text in 7.5 of 8711.

Also, I know of several people, and I'm sure others know of similarly 
situated folks, who are regular participants but are from 
time-to-to-time between jobs or in other financial situations, who have 
specifically decided not to attend the physical meeting and instead 
participate remotely because of the lack of registration fee (in 
addition to not having to pay for travel). Folks have come to expect 
that participation in the face-to-face meeting would incur expenses, but 
participating remotely, whether by listening to the audio feed and using 
jabber or email to send in comments, or more recently by Meetecho, was 
going to be free. While not the only reasonable interpretation of our 
history and BCPs on the matter, having remote participation be free is 
certainly not an unreasonable interpretation of the status quo.

So "well within his rights" seems a bit of a reach. Perhaps "not 
completely unjustified in assuming" is closer.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best