Re: ietf meeting fees

Bob Hinden <bob.hinden@gmail.com> Wed, 29 May 2019 15:38 UTC

Return-Path: <bob.hinden@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 60996120224 for <ietf@ietfa.amsl.com>; Wed, 29 May 2019 08:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, US_DOLLARS_3=2] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 duCODMaVpTxS for <ietf@ietfa.amsl.com>; Wed, 29 May 2019 08:38:15 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 DBFD4120220 for <ietf@ietf.org>; Wed, 29 May 2019 08:38:14 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id d17so1997259wmb.3 for <ietf@ietf.org>; Wed, 29 May 2019 08:38:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=14ck7I72PjEvxY5shOP7rUctICC7ygKdZwopfOmxSpI=; b=UB5v7MUkpIOGCVoJMP0V51h/QcvFenqQ3LCCIo6X6j3ZqHpgJetzvSPPbQB8ymqDH8 7qVSxmA2ZWR7g4XN8NvBVo1FAXzrWwt7oEUmx+VDdpu0EDzmu4aQNOLVF8aDQzggUMXC saVhOR+CjT3QTWxx3z50yERCChNlNaniZdkRYLxdlRGhEhLRSjvbDCGgdLcBrFUYhuhe jmbKl58pB8TZgtqSVb7JS5xvcLy6FQpvktfdJqVbl+7rCCrFCHHhHOMcqLh/7w1KZVJf QEcm71C1aC3GaYmhAe9FB8fUWlRZ7rwT+t1GCAoYl7YPsoZiYArNnUkGd84TY21n2tik rTTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=14ck7I72PjEvxY5shOP7rUctICC7ygKdZwopfOmxSpI=; b=Ny/Wgg718o8/wYm4IchpgMggPxAkO7YM4GN1IboxYux85NGIq424FkWHJKK4kLWzFW vvjXboz7QjA8SzYTFTmqNgRyHLfMsc6r9PPhDCo6Bhg17c0wgb4EMvVGriesIDXRp/b6 Z4+dFipjyMlfY1+sFprm0rvuJNf5B7U1n8OCuKAi4Lm4g75dfjSqOCYKUT1ObVyHqW4S wwnWXA+RameamjCuBbNDKwnV5eJ3qbw2tdXCQ8YHUN1STb4/YqbVQnEYocQ/fTAW+TSI V6zBHJ6aXbtB0jfEoobEZ6N8sN7Ph9ci5gNTqgiwzM8ZyCI1HmDgrxQNJ1U5dAu5jz6+ Y2ZA==
X-Gm-Message-State: APjAAAW2Xx0baIa6ZKl53+7xZueklt7UGxBy00hQEjPbsUKZx8xDI2jw slirTMkAGcXYesjNxnFQpQ9tcmyo
X-Google-Smtp-Source: APXvYqzQ9W/e7AsLhUova+rlzE22OaHKgCNdgAraQ5NOVdJk+VQdLsMMMeTGaI/eYAdUnOs1yNXNJA==
X-Received: by 2002:a7b:cd15:: with SMTP id f21mr3320850wmj.99.1559144292988; Wed, 29 May 2019 08:38:12 -0700 (PDT)
Received: from [10.0.0.199] (c-24-5-53-184.hsd1.ca.comcast.net. [24.5.53.184]) by smtp.gmail.com with ESMTPSA id j7sm17305327wrt.31.2019.05.29.08.38.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 May 2019 08:38:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: ietf meeting fees
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <d18a252b-6ac3-4241-bd0d-b1566f3822a7@network-heretics.com>
Date: Wed, 29 May 2019 08:38:07 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <610AE97C-C0D1-4FB8-BCEE-92102269D57A@gmail.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>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j64dvUHIKyOxxItFfuzBOpz69CA>
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 15:38:16 -0000

Hi,

> On May 28, 2019, at 3:49 PM, Keith Moore <moore@network-heretics.com> wrote:
> 
> On 5/28/19 4:35 PM, Michael StJohns wrote:
> 
>> PS - like it or not, meeting fees provide a substantial amount of the money for the general IETF budget specifically including standards publication. 

The percentage of the IETF costs that the IETF meetings registration fees cover has been going down for a long time.  With the addition of the added expenses for the LLC less so now.

According to the IETF 2019 budget at:

https://www.ietf.org/documents/246/IETF_2019_Budget_Public_2018-12-19.pdf

Meeting revenue ($3,941,880) is greater than meeting expenses ($3,837,325) by $104,555.   So we are pretty close to the meetings just paying for themselves.   ISOC more or less is paying for everything else.

Also, the 2020 advice, shows a meeting deficit of about $12K.

Bob



> 
> 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.
> 
>> If you are arguing for actions that reduce or tend to reduce or have the potential to limit the intake of funds from that model, I suggest you also come up with a more than handwaving proposal for how to replace those funds or explain which functions supported by the IETF we're going to eliminate to cover such shortfall.
> 
> Perhaps we should also require more than handwaving reasons for staying the same.  :-)
> 
> (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?)
> 
> 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'm not accustomed to designing conferences, so if you want details, perhaps suggest what kinds of details are needed?
> 
> Keith
> 
>