Re: [Mtgvenue] business travel:

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 30 January 2017 19:12 UTC

Return-Path: <brian.e.carpenter@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 9849F129AB8 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 11:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 AOR5Qe2TUtJ0 for <mtgvenue@ietfa.amsl.com>; Mon, 30 Jan 2017 11:12:49 -0800 (PST)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (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 68AD1129AA1 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 11:12:49 -0800 (PST)
Received: by mail-pf0-x241.google.com with SMTP id 19so23839307pfo.3 for <mtgvenue@ietf.org>; Mon, 30 Jan 2017 11:12:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=SclxQMOnNy6fbtkKKNrcTO+uzJZrBSGPWKTgPeA059g=; b=nTcHtZj3Zd7kzgkZq9EGmq9AtZ6kfCZlymm/BEcIb8Z8OuTr6Srhh6Iv4jdIgy7pkU D+QL0gg/BwqtjnW5uIXdPZnWrs5P2sfhVD8bWTsN0KBFB94Gc4N44EhFCWuOXQ+szZ3q SWq8CLzi3LWq7TGvwUEZHsXYWerQZKDDqanYR25/oX26j1hrjFwIi2tetszL/VPwu9dP tLzNFt3rCyO48Z5Yg4ILNzi7iUUAM1FfPI5PjVuWe2Tx+fi8e4I6d1XiBhL5E2nJWMaX 2X87/kFG2Yt/WhGaeteMNVw8gGgbvM+kIevaJWdbb2hA4ZfgPe1W2pjeLVs+ySn3cmqd GYwg==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=SclxQMOnNy6fbtkKKNrcTO+uzJZrBSGPWKTgPeA059g=; b=eaxNTP/F4HauaMAyGJfyjsHElY4u7UredKsIJ6YKdRFXPeMbVEoLpZVIAbHGU/bgP1 B3yk+zGH7sORW8eLj0nazHlDpptno+fETyyXVyxg7N04YjXTgoykwmH5hk65O+NRdfMb mwOMlkzN9jrBiSHKDWFcqF2t+d6nYCRKarUkJB+mQZljNtQTI8qFgH280iCOpyUQt5h0 3LCuD7zCmKpc80FK4ghJkjXlp4o/5fAPcsuW/Ikaxkhhc4T6E/2AqoQStl32zkT3jVDW UcwKWwugjwORPOM7yM5EJlAuSBYkdd4ZzLqoMaF29+j7H8RDaIJ4Ceb2tTiYoMieQara 3FWQ==
X-Gm-Message-State: AIkVDXKifi/gfm39kbPYEx10lnmFNN69evSRBNpGMEop7BXKBQWyyRw3NAs8TM+RB+gF9w==
X-Received: by 10.84.232.141 with SMTP id i13mr33771558plk.119.1485803568914; Mon, 30 Jan 2017 11:12:48 -0800 (PST)
Received: from ?IPv6:2406:e007:7505:1:28cc:dc4c:9703:6781? ([2406:e007:7505:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id n70sm34575904pfg.34.2017.01.30.11.12.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jan 2017 11:12:48 -0800 (PST)
To: dcrocker@bbiw.net, 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> <c249c576-8dea-077e-dd80-dfe8099e57ac@dcrocker.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <af53b69c-e5dd-b2b3-78a8-4ffaaf186f16@gmail.com>
Date: Tue, 31 Jan 2017 08:12:44 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <c249c576-8dea-077e-dd80-dfe8099e57ac@dcrocker.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/B3HGwePDNspQEetw2VqnvFHvToc>
Subject: Re: [Mtgvenue] business travel:
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 30 Jan 2017 19:12:50 -0000

On 31/01/2017 04:47, Dave Crocker wrote:
> 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.)

Perhaps "typical business travel" would clarify the meaning.

  Brian

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