Re: ietf meeting fees

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 29 May 2019 05:16 UTC

Return-Path: <brian.e.carpenter@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 E0CA5120045 for <ietf@ietfa.amsl.com>; Tue, 28 May 2019 22:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 7TBkFGh9rFHt for <ietf@ietfa.amsl.com>; Tue, 28 May 2019 22:15:59 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 E29A31200C7 for <ietf@ietf.org>; Tue, 28 May 2019 22:15:58 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id t1so625350pgc.2 for <ietf@ietf.org>; Tue, 28 May 2019 22:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=EJKSeszQa4AkBkLGJUHAdOtXGHGjGuPHmm2+fBC+1gM=; b=vS2EOLd9RTuxeC8n1GB9Xu6n0iv7mHgekE+l1NC2XdpNAsFwF98ybezoskBxWTTeoc Dd88vklI1Eo4KazMTABX1myZ7lin/zNkGrI2IPzrKDtMeF+4WIJmGjOsreCqwDgeh9k6 w+xDINrL+xCrre9zCCZTC+0lMZIN263z5S8OEWB0/s5/vuASzhVimbdjLxJpSWN/FLLz xtxdDddJ47yKf5jIKWzxDEYVjrVpGfw6JI74jgdO5afOcBH4TOjIuIQl2uOzAjX9l0sp nXMijX7BP7WPMknZ2tm21Ao7a8P/tPQ2+8uDNCWB9x+ZMvItydpPnGdEIqfGRf+qtmaS g87w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=EJKSeszQa4AkBkLGJUHAdOtXGHGjGuPHmm2+fBC+1gM=; b=no4j9Mqs0IPypH8RWfJ5SEXzCr+vCKJI07hKbXIVlxNrGJ7APdghAAF5ZuYf15BOWw S8hk2zxxdVYOYfdbGr7tUykCQxR2QrD3K7qjLXAbiy+QDKNrk3I+RDQFj/VCPljilIuT yrhsDT3RACk7b7lt/xpHUtf5eZbvmwsAoSnrEO2DjHaB1n3STw87bgMg/m94tDzx4T1F ZvCE+wGHOd5buoOlVipDfg1NKLu6BkXuWWEuB/p2UAFiUakooyDyuYPA3ogGgcFKuex/ PN01rcq/wH1svSejak1VYA1r+Kp8j/ffmzEGbN+WwdehGFMYcmIY+QJ2GA0nGhI3Vu2l 4Nrg==
X-Gm-Message-State: APjAAAXgbloURUOghGSPyx8gw8UClhbdskmO81q4AIrLNMfDDvMhSogQ 5pWRSHJR8zCPb8hNesUblOY4Xq5n
X-Google-Smtp-Source: APXvYqw28rBzmk8ibFPrXnKNudGIKst5yXi1iJodqT7e5KWcx0J/Tlys768Pi3Wj6i7NG+1Spf/QRw==
X-Received: by 2002:a62:6145:: with SMTP id v66mr22866917pfb.144.1559106958193; Tue, 28 May 2019 22:15:58 -0700 (PDT)
Received: from [10.71.7.45] ([119.17.54.66]) by smtp.gmail.com with ESMTPSA id r71sm7335441pjb.2.2019.05.28.22.15.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 May 2019 22:15:57 -0700 (PDT)
Subject: Re: ietf meeting fees
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9b84aace-2d9a-beb2-7785-a6f25a229d2c@gmail.com>
Date: Wed, 29 May 2019 17:15:52 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <d18a252b-6ac3-4241-bd0d-b1566f3822a7@network-heretics.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jjXnt_JD4nD-Y5kBpKJkH-VoUgg>
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 05:16:01 -0000

On 29-May-19 10:49, Keith Moore 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. 
> 
> 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.

My understanding is that IETF LLC's jobs include fund-raising, so we do
have this issue on somebody's to-do list.

     Brian

> 
>> 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
> 
> 
> .
>