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

Lou Berger <lberger@labn.net> Tue, 11 April 2017 17:41 UTC

Return-Path: <lberger@labn.net>
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 CE82F12EB2D for <mtgvenue@ietfa.amsl.com>; Tue, 11 Apr 2017 10:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level:
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 ZAnct4WHC0wC for <mtgvenue@ietfa.amsl.com>; Tue, 11 Apr 2017 10:41:54 -0700 (PDT)
Received: from gproxy8.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FE3512EB2F for <mtgvenue@ietf.org>; Tue, 11 Apr 2017 10:41:54 -0700 (PDT)
Received: from cmgw4 (unknown [10.0.90.85]) by gproxy8.mail.unifiedlayer.com (Postfix) with ESMTP id B506C1AB3D8 for <mtgvenue@ietf.org>; Tue, 11 Apr 2017 11:41:51 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id 75gY1v00W2SSUrH015h66c; Tue, 11 Apr 2017 11:41:50 -0600
X-Authority-Analysis: v=2.2 cv=QdwWhoTv c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=N659UExz7-8A:10 a=xqWC_Br6kY4A:10 a=AzvcPWV-tVgA:10 a=xPBN89oeI-auCyhBT4QA:9 a=pILNOxqGKmIA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=xjCUEchp0vgD7sW3oG9g4eVcvxLK8Sj11Va0l04IgHk=; b=qIR8mByEJzS7jWqjwUwNKi+ZHv feJClknHZnMiwiJVn7RLyNPBMQ4RWxEAJNKn7J3IE4Q4f11WOIRgdIayGag7l2iiLkbeS6gqYge9Y XYZ3MkvIDgUMlUZ4TBzIsUi1B;
Received: from pool-100-15-84-20.washdc.fios.verizon.net ([100.15.84.20]:54464 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1cxzmJ-0003NE-Vx for mtgvenue@ietf.org; Tue, 11 Apr 2017 11:40:32 -0600
To: mtgvenue@ietf.org
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> <20170411171823.GE2378@mx4.yitter.info>
From: Lou Berger <lberger@labn.net>
Message-ID: <34f8e5ff-abe9-a8ce-5281-8d3c4b9ce498@labn.net>
Date: Tue, 11 Apr 2017 13:40:30 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170411171823.GE2378@mx4.yitter.info>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.84.20
X-Exim-ID: 1cxzmJ-0003NE-Vx
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-84-20.washdc.fios.verizon.net ([IPv6:::1]) [100.15.84.20]:54464
X-Source-Auth: lberger@labn.net
X-Email-Count: 17
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/49lTsvATlB2ARSMbiFlT3yqMxH4>
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 17:41:56 -0000


On 4/11/2017 1:18 PM, Andrew Sullivan wrote:
> On Tue, Apr 11, 2017 at 01:12:20PM -0400, Lou Berger wrote:
>> There's a bit of distance between saying we're preserving/codifying the
>> old model and that it's okay to knowingly setup a meeting that is going
>> to loose money, i.e., which will likely translate to increased meeting
>> fees. 
> Why does that follow?  It could be that a new sponsorship arrangement
> supports IETF activities generally, and maybe meetings are a net loss.
> I suspect that's how ICANN operates, just for instance (their meeting
> budgets are amazing, and it seems unlikely that they get enough
> sponsorship to cover them.  And they charge no fees).

Then these meetings don't operate at a loss, they are covered by
sponsorships or other donations.   I guess we need to define net loss -
unless you're suggesting that not covering costs in a projected /
budgeted fashion is acceptable?

Lou

> A
>