[Mtgvenue] business travel: (was: Re: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04)

Dave Crocker <dhc@dcrocker.net> Mon, 30 January 2017 15:47 UTC

Return-Path: <dhc@dcrocker.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 8558D1294C1 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 07:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.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 QdZYbfIpEZ3S for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 07:47:13 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 0E0DC129421 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 07:47:13 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v0UFmhUn028095 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Jan 2017 07:48:44 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1485791324; bh=pJZxxIFffk+AWN4kpQHM/zQOEss24997LSXMy3I440s=; h=Subject:To:References:From:Reply-To:Date:In-Reply-To:From; b=O7fpyF6OXLeL3dPj2+xq2F0tLOXsvbbi/cbBsPHf/muTrjvJ4dyjMg2G3TSA9udHC lJxpFsyWgixWaEOibzSET1pL8U4OGPNA5Jqlm9AtD/Y8smVUkHIA0YDPUD4JylXxmF wtRVaPq7zY31VVBV2k/vysI2NiBo0V7bkzeXxUm0=
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Eliot Lear <lear@cisco.com>, mtgvenue@ietf.org
References: <9139334c-9c5e-814d-4299-c6f5950039b8@cs.tcd.ie> <2dcdf5d1-4e93-7476-79ba-0369e41af1c0@cisco.com> <43126aa9-5bc1-fae5-ff76-3ad288e37340@cs.tcd.ie> <24c2e78e-97ab-9642-f067-1da4fc82d9b6@cisco.com> <092a25ac-ed8f-98a3-a421-6bc6af9d90a2@cs.tcd.ie>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <c249c576-8dea-077e-dd80-dfe8099e57ac@dcrocker.net>
Date: Mon, 30 Jan 2017 07:47:00 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <092a25ac-ed8f-98a3-a421-6bc6af9d90a2@cs.tcd.ie>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/8NpIBUKXQfJdjih5SxUoryZCqds>
Subject: [Mtgvenue] business travel: (was: Re: comments on draft-ietf-mtgvenue-iaoc-venue-selection-process-04)
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 30 Jan 2017 15:47:13 -0000

On 1/30/2017 7:07 AM, Stephen Farrell wrote:
>>>>> - 3.2, "within the norms of business travel": I don't like
>>>>> that characterisation - IETF participation might in future
>>>>> not live up to that budget. Ought we say "acceptable to IETF
>>>>> participants in general" maybe.
>>>> Didn't we just get away from having to evaluate what that means?
>>> Not sure what you mean. My point is that for some IETF
>>> participants (some of the time;-) "business travel" means the
>>> front of the plane and no problems with expensive hotels.
>>> Others are more constrained. I'd prefer we ground the acceptable
>>> costs on the "average" meeting-attending IETFers ability to pay.
>> I get it.  Just want to avoid consensus calls on what people think is
>> reasonable.  Maybe spelling out what is meant by "norms of business
>> travel" is best...
> I'd avoid the phrase "business travel" entirely. While IETF
> travel is business for almost all of us, that phrase has
> connotations of more comfort than some of us can afford, at
> least for me when I play the poor-mouth:-)


The draft has details carefully designed to cover those with lesser 
budgets.

The purpose of the phrase "business travel" is to give a generic sense 
of the style and expense of choices made for the mainstream IETF 
participant.  The meeting hotel is the obvious example.

"business travel" is not a precise technical term, but it is meant to 
invoke a basic tone or style.  (For reference, most businesses do not 
pay for business class airfare.)

The mainstream IETF venue choices are not 'budget'.  Nor are they '5 
star".  'Business travel' therefore gives a basic sense of the target 
quality and cost that is sought.

Again, we also have text that carefully covers requirements below that 
category.


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net