Re: ietf meeting fees

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 29 May 2019 16:37 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 7FAEF120114 for <ietf@ietfa.amsl.com>; Wed, 29 May 2019 09:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 S3b1rAVztFRM for <ietf@ietfa.amsl.com>; Wed, 29 May 2019 09:37:39 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60FBD1200D5 for <ietf@ietf.org>; Wed, 29 May 2019 09:37:38 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id A9C763826E; Wed, 29 May 2019 12:36:32 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id CFF0E9B0; Wed, 29 May 2019 12:37:36 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id CE8D58EF; Wed, 29 May 2019 12:37:36 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Keith Moore <moore@network-heretics.com>
cc: ietf@ietf.org
Subject: Re: ietf meeting fees
In-Reply-To: <d18a252b-6ac3-4241-bd0d-b1566f3822a7@network-heretics.com>
References: <6.2.5.6.2.20190509041736.0d6d4548@elandsys.com> <f5834466-8f40-42bd-82d8-4dcb7d418859@www.fastmail.com> <6.2.5.6.2.20190509105617.0c08ef60@elandnews.com> <e854adaf-1ead-41d0-95bf-df56cb5a5914@www.fastmail.com> <6.2.5.6.2.20190514234822.0bc461f0@elandnews.com> <15BCE05FEA1EEA6AD0E7E5BD@PSB> <6.2.5.6.2.20190516103829.11f9fb18@elandnews.com> <E85C84CF-DB0B-410E-A0B2-A7C7E705E469@kaloom.com> <6.2.5.6.2.20190518141450.1163e590@elandnews.com> <82E6BD6B-41F4-4827-8E18-3FF63511DFEA@gmail.com> <EC966FE1-C1EE-453F-A66E-61B007293792@episteme.net> <CDAD735A89911ADC5F0F2DFA@JcK-HP5.jck.com> <B5AF3E16-1C6E-4EFE-8207-8D9D90025858@episteme.net> <3415C5F0030817714DA1891B@PSB> <42cda6df-4c55-f729-b4ec-fc1d6237ace3@nthpermutation.com> <d18a252b-6ac3-4241-bd0d-b1566f3822a7@network-heretics.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 29 May 2019 12:37:36 -0400
Message-ID: <9386.1559147856@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bvnqnfzAfLGbf7Tfb0iXIClGqyc>
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: Wed, 29 May 2019 16:37:41 -0000

Keith Moore <moore@network-heretics.com> wrote:
    >> PS - like it or not, meeting fees provide a substantial amount of the money
    >> for the general IETF budget specifically including standards publication.

    > It's a given that there has to be some way to pay the bills.  But if we have
    > so much inertia around this way of raising revenue that it makes IETF less
    > and less relevant over time, maybe IETF should address this problem sooner
    > rather than later.   No organization can hope to remain viable if it refuses
    > to even consider adapting to changing conditions.

a) The meetings are not as "profitable" as they once were.

b) At this point, the November Asia meetings are not profitable at all, and from what I
   understand are now being planned on that assumption.  Some speculate that
   a March Asia meeting might do better, but that experiment is a few years
   away, and as yet, to my knowledge, unscheduled.
   March 2022 is the first spring where it could happen.
   (Same speculate that summer asia meeting would be intolerably warm.)

c) my understanding of the ISOC/LLC budget process seems to suggest to me
   that ISOC understands that these revenues are expected to decline to
   become insignificant.


(To be clear: "profitable" --> funds generated by in-person meetings that are
spent on secretariat and other non-meeting related expenses such as
RFC-editor, IANA, etc.  As a whole, the IETF does not make any money)

    > (There's a familiar set of arguments for staying the same:  If you don't
    > provide a detailed proposal, it's labeled handwaving. If you do provide a
    > detailed proposal, it's easy to pick it apart as naive because it hasn't yet
    > benefited from broad exposure and feedback.   Or is there no longer any place
    > for brainstorming in IETF?)

Internet-Draft?
Design-Team meetings/mailing lists?

    > I do suspect that there's likely a market for technical conferences that
    > serve as a more effective way for IT and operations people to keep abreast of
    > standards development and also to provide feed-forward about the problems
    > that they are having and which need to be addressed.   And that such
    > conferences might also attract more "doers" to IETF.

I think that ISOC has tried to run conferences like this; I think that most
IT operations people do not attend many conferences for the simple reason
that they have no time.
It's not about cost of the meeting, it's about the time away.
So to get their attention, it has to be near them, but if it's near them,
then they can not focus much.  I suspect that well done youtube videos
chopped into 20 minute segments might be best.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-