Re: [Mtgvenue] issue #3: Too many mandatory

Fred Baker <fredbaker.ietf@gmail.com> Tue, 11 April 2017 18:27 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91D0A12EBF4 for <mtgvenue@ietfa.amsl.com>; Tue, 11 Apr 2017 11:27:23 -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_PASS=-0.001, URIBL_BLOCKED=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 OCpGBV72E0FP for <mtgvenue@ietfa.amsl.com>; Tue, 11 Apr 2017 11:27:22 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (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 BE3D912EBB2 for <mtgvenue@ietf.org>; Tue, 11 Apr 2017 11:26:36 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id l28so3456798wre.0 for <mtgvenue@ietf.org>; Tue, 11 Apr 2017 11:26:36 -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=d0eWwKLdCKJCeNxBFRHhx+Rdnnfc9sJJ1ffgB2EPg/k=; b=r12dzhYXWRlCiBex6P1JJBbzOMR1rfF+fM95jZHQpSGd7hoTTj5kWlgZzRfmmQMC11 wx2m/lR8GSNhIorKiwDftI80sLSZF7bTgI2vVarEGEENzXIWuqziXGC2FB30190bJrlP AtTy3X2Qm9gUHYxe/F2CFxio5ziobLc42VB7FmwD0zfQAC3vLeBl16IjRzivULCcgahC y40x3XjmpZV/w6EaJr17r+kR1BjNSKCwUtB9wslG1B+8K5J04lwXNcvM+Avw3+u85L0d bsskcUFOVe9/T9wg0iSOd5cX7TC9aiP0uUKDjoFeLecMUNpUNEEDLl6qs1vvz/Zbj10W V5iQ==
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=d0eWwKLdCKJCeNxBFRHhx+Rdnnfc9sJJ1ffgB2EPg/k=; b=is4roDbHo22I++hN35Elf9la2zxmgurm5M+4irLN5r0JBNsZ4SKXonHRRmXR3IFT/q eWBfbIthdjhosuob0s9Yuk4ejfysya01gzuAD70eOCGOlTazr3jSAcoQgQxin3LfW0ba cbxzxYasjlVlj1RpK3Cv3qBIZtS+C6aKjepV1RupxXjNnP81ZnTZoGyB0ON42f2aye3E 1p4qBVidJe026xRHjPAE6Pa/EaFexPg6t9EM+nnmi/4p2/ZD5LtZ48P1j+TRyceuZIv4 yScOLzql60EppRJKcY/J3/AvOFgGHpTs+TiO/yHXoLEu0YpqKhmJ6CQWjr05tHUwOyYN HAiQ==
X-Gm-Message-State: AN3rC/6Hb+E4akn+xkefQjbvIRxX7/QHVkGT6VIwdzmF6YZVD0Dprs5X4ORQjEr1WHLxZw==
X-Received: by 10.223.139.22 with SMTP id n22mr23647439wra.38.1491935195202; Tue, 11 Apr 2017 11:26:35 -0700 (PDT)
Received: from 209.66.20.149.in-addr.arpa (209.66.20.149.in-addr.arpa. [149.20.66.209]) by smtp.gmail.com with ESMTPSA id h20sm3473998wmd.29.2017.04.11.11.26.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Apr 2017 11:26:34 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <c11ca278-3835-743b-c68c-e4dde7c9b0af@cisco.com>
Date: Tue, 11 Apr 2017 11:26:31 -0700
Cc: Lou Berger <lberger@labn.net>, Pete Resnick <presnick@qti.qualcomm.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0B703C9-D549-4E01-AE2A-E1BF442F37F0@gmail.com>
References: <37de22dc-04a4-f868-698e-cf03cd791957@cisco.com> <a1b4fb14-64ec-2848-91e7-faa93ba6e697@labn.net> <cfd7ace5-d834-fb41-57a4-ea11d0126f0f@cisco.com> <10ee5913-87d4-d895-e880-54471b2469a7@labn.net> <759DD927-BEC2-4989-A9F5-46B7DD090B24@qti.qualcomm.com> <4fdf7dea-b565-845e-1e0e-541d88a530e1@labn.net> <1CB0773F-602C-4F45-BBEF-E9708F80032E@qti.qualcomm.com> <9d19e10a-8030-2d79-c587-256e07a7892e@cisco.com> <b4365a4f-f378-2766-26fa-d430e1d80916@labn.net> <c11ca278-3835-743b-c68c-e4dde7c9b0af@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/kcScFTEb2viis1BoAkBRedZ40hk>
Subject: Re: [Mtgvenue] issue #3: Too many mandatory
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 18:27:24 -0000

> On Apr 11, 2017, at 10:44 AM, Eliot Lear <lear@cisco.com> wrote:
> 
> Hi Lou,
> 
> 
> On 4/11/17 7:12 PM, Lou Berger wrote:
>> The text in question reads:
>> 
>>    The economics of the Venue allow the meeting to be net cash positive.
>> 
>> To make make it clear that it's not saying preserve the current model, how about:
>> 
>>    The economics of the Venue allow the meeting to not result in a net
>> loss.
>> 
> 
> What was said in the meeting, as I recall, was that even planning a loss
> at ONE meeting is okay, so long as the IAOC can see their way clear from
> a budgetary standpoint.  For instance, Jari was complaining about the
> cost of going to Japan.  Maybe what happens (and I don't know if this is
> the right thing to do) is that the IAOC decides to subsidize a meeting
> with Japan from somewhere else.  Should that not be allowed, and should
> the IETF community care?  And if we do, what precisely is it that we
> care about?

I think that is stated too tightly.

The IAOC has a budget for IETF operations 365 days a year, which includes the costs of the secretariat, IT expenses, yada yada yada, and OBTW, meetings. Meeting fees pay for part of the costs; we also have ISOC funding, which is primarily derived from organizational member fees and PIR profits (which Steve Crocker will tell you exist for exactly one purpose, which is the funding of the IETF), and we have funding from hosts and sponsors. The point is that the sum of the revenues meets or exceeds the sum of the costs.

So it's not "let's make enough in meeting X to pay for the loss in meeting Y", it's "let's fund the entire budget".