Re: Specific Questions about Registration details for IETF 108

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 08 June 2020 13:54 UTC

Return-Path: <ajs@anvilwalrusden.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 BC5F33A0AD1 for <ietf@ietfa.amsl.com>; Mon, 8 Jun 2020 06:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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=yitter.info header.b=K+R4kHXb; dkim=pass (1024-bit key) header.d=yitter.info header.b=mTKIdlsP
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 D_ynLvRPa3h0 for <ietf@ietfa.amsl.com>; Mon, 8 Jun 2020 06:54:53 -0700 (PDT)
Received: from mx5.yitter.info (mx5.yitter.info [159.203.31.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB72A3A0815 for <ietf@ietf.org>; Mon, 8 Jun 2020 06:54:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx5.yitter.info (Postfix) with ESMTP id 16D71BD51A for <ietf@ietf.org>; Mon, 8 Jun 2020 13:54:22 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1591624462; bh=tQrlY83kk9tL0By1qJvbA32UcYP94zJNi9TtzU5TN1o=; h=Date:From:To:Subject:References:In-Reply-To:From; b=K+R4kHXbiT6IzXkR+qh5hDdd5NCpS7d11FVVhEy9iJV7a8UrKYNoTAa2wHFyxf8Hn Kw4rSWkJ5OtQCZ3wKsYFGPQ0D2Kho5+2huN7xABxmi0VGp2/V2XiZzxhA2bg4hzfqB rbLDOtfglas5z+DXno9QFJLOhna49CFZzouvVk6c=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx5.yitter.info ([127.0.0.1]) by localhost (mx5.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXJdZJEsvlEo for <ietf@ietf.org>; Mon, 8 Jun 2020 13:54:20 +0000 (UTC)
Date: Mon, 8 Jun 2020 09:54:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1591624460; bh=tQrlY83kk9tL0By1qJvbA32UcYP94zJNi9TtzU5TN1o=; h=Date:From:To:Subject:References:In-Reply-To:From; b=mTKIdlsPqc1bDn1fOCZomBjUEiKnYpm9R4g7JJ84D6Xk0a3vG0a5l2A5QWTfctn7i zyQYPgd7r0oFkgBzMg7Nh+9w/D/HB6myTQWWtoQD/8K7HCXDklavypFOPxKZnV9Q9B ua0pOzS/qkrrZfSXxqjiQGu90L6+KHZx25Onrb4U=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Specific Questions about Registration details for IETF 108
Message-ID: <20200608135415.jx2qpvdfnxyjohmv@crankycanuck.ca>
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <3B19A920-9D33-4E3D-8B8B-8134A5E55316@gmail.com> <86D7C39D-9778-4408-B7CA-CB74E9572B1B@ietf.org> <511A3EE0-976B-40FF-813A-58CC115E760A@gmail.com> <20200605153042.nospgcd7nku4luag@crankycanuck.ca> <FB3BDBCABF6F5FE86E54BF6D@PSB> <20200606030147.jx4cyox7j5wn7a24@crankycanuck.ca> <AC2C084E4B54AAFC224B6631@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <AC2C084E4B54AAFC224B6631@PSB>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rnE1fac7fIk0jNQ1ZodULPPbuSs>
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, 08 Jun 2020 13:54:58 -0000

Hi,

[ObDisclaimer: still employed by ISOC, still just my opinion]

On Sat, Jun 06, 2020 at 09:54:13PM -0400, John C Klensin wrote:

>And we don't require anyone, even lawyers planning to draw up
>into litigation, journalists with a record of hostility toward
>the IETF, curious bosses trying to check up on what they are
>spending resources when they allow employees to participate in
>the IETF, or people who want to observe meetings for a while to
>see if they want to participate or advise others to do so, to
>identify themselves and/or pay a fee to observe meetings in real
>time.
>
>Now that seems to me like a principle

I guess what I'm wondering about is the extent to which "in real time" is important there.  Why does it matter whether it happens synchronously or after the video &c is posted, given the differential costs to the IETF in managing an "observers only" stream?  The incremental cost to the IETF of letting anyone at all look at the stream on YouTube or anywhere else is 0, but there are costs involved in creating a second stream just for observers.  "Observe in real time" seems like it might be quite important when people are all in one place and could be having chats on the sidelines (so the "observer" status might be important in that case).  Not so in a virtual context: you can't tell when people are having such side chats, even though they might be, by observing them in real time.

>are a non-trivial number of IETF participants who have been
>participating remotely for multiple years and who have built
>personal (or corporate) budgets and plans around zero-fee remote
>participation.

Yes, I think that is probably true.  It strikes me that many people's expectations have been thrown out by the COVID-19 situation, and this seems to me like another one: it is possible that, if the IETF decided _more generally_ on a model where charging for remote participation would happen, it ought to be rolled out gradually or at least with warning so that people can adjust budgets appropriately.  But alas, the virus waits for no budget season, so here we are.  

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com