Re: [Mtgvenue] Issue #24: More than 1 hq hotel?

Bob Hinden <bob.hinden@gmail.com> Mon, 15 May 2017 16:18 UTC

Return-Path: <bob.hinden@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 7013812EAA6 for <mtgvenue@ietfa.amsl.com>; Mon, 15 May 2017 09:18:57 -0700 (PDT)
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 KIR42pee_LIp for <mtgvenue@ietfa.amsl.com>; Mon, 15 May 2017 09:18:55 -0700 (PDT)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 D507012EAAE for <mtgvenue@ietf.org>; Mon, 15 May 2017 09:14:51 -0700 (PDT)
Received: by mail-wm0-x243.google.com with SMTP id u65so29335950wmu.3 for <mtgvenue@ietf.org>; Mon, 15 May 2017 09:14:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Wf0EcTce4roFgSClRp1CEzKn2kO7dkHYCwuGSWWEVZA=; b=MAb3vn9Wa20LyNf8VANa9Q8yrouQoYWgwZQGV8CnO+jbJrphP2j8QgOeFqR2i6P4db RH/3THxuvxooKwP9d4zfvrTdZfkeTt5Z81agKTH5UmMbRteh2Wj132a2q+jUlomEltCr UyzsTOPpKY6uEGT3X/nmb9/Mkk0WOcXhFApszNcnmm9bjclQ4EWQpQBO0UnL5TpJK9Nw nEwmKftaVqWuEH6rWQuJlQ7n4o1Bj7btYMifyv8JPA3wtNBKba/LEXVyF4uinwHriEkL DJzPqzSRxobf5MjaWvE05R3qtPHfPqx1OQG8bTJvT3hPPs3xbZC4XvkXYMHIDfTS85nM i2cQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Wf0EcTce4roFgSClRp1CEzKn2kO7dkHYCwuGSWWEVZA=; b=roYWAO6kX0BhG5ejhUK1EeNUZEGmcpj76d4VJMRmKLGM6cEELjMzD76sOU2PULF8kN ZFvoyGzRNWN1xXNIzdgIB4zz/HL0TtKOi6IjjDoQvKSG85S1eO6/H82Hi05hgRTx7m9v ngBZJ3VhGsg4rCSZqOdM3Edw1682dsW+Tsl714oB+1jEz4KXDoqg8VyGYD/CI+6bWLgT Ze+Pr8ZonGRJCVW5+O4rOzCrjBSJlZS8XhakC4t0M+XVCnNNF01svSijqhsMTur6C+zM SBeuXSpk5dZEpT8dBx4gjL5r8LSlanEPRWAPumOFm3y30Gpmj/WOePKd/dqQKunUTsUV xu9A==
X-Gm-Message-State: AODbwcDHYARRP6y35UXOpxcuErf3O9xxLWwO828iOrpV3b8cC1SENtOu GLDcAIqokqC8qWHzKU0=
X-Received: by 10.223.150.167 with SMTP id u36mr4803039wrb.184.1494864890220; Mon, 15 May 2017 09:14:50 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:db10:25ef:2857:96f9:e17d? ([2601:647:4d01:db10:25ef:2857:96f9:e17d]) by smtp.gmail.com with ESMTPSA id p5sm7229452wma.17.2017.05.15.09.14.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 May 2017 09:14:48 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <FE8CC603-041E-4823-BC53-9DB1F627E7C4@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C8CE507F-A183-4BA8-A3FB-9961AAF73CA6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 15 May 2017 09:14:42 -0700
In-Reply-To: <8e365c06-99e5-e9f1-50d1-2e3558400248@cisco.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>
To: Eliot Lear <lear@cisco.com>
References: <9a41874c-24e2-aa0c-e58c-7bee8b35f91b@cisco.com> <2247.1494795324@obiwan.sandelman.ca> <e83d3fe9-4394-b82a-0a75-008329ef62a8@cisco.com> <8359.1494857281@obiwan.sandelman.ca> <8e365c06-99e5-e9f1-50d1-2e3558400248@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/6WpknVWkngWFTYl18k4wN_TJPy0>
Subject: Re: [Mtgvenue] Issue #24: More than 1 hq hotel?
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: Mon, 15 May 2017 16:18:57 -0000

Eliot,

> On May 15, 2017, at 7:41 AM, Eliot Lear <lear@cisco.com> wrote:
> 
> Michael,
> 
> 
> On 5/15/17 4:08 PM, Michael Richardson wrote:
>> Yes, I know it's still in the document, but you cut it from the message.
>> 
>> That matters wrt how the old and new text considers.  How can a lounge
>> in a non-HQ Hotel be between the meeting room and hotel entrance if
>> there are no meeting rooms in the overflow hotel?
>> 
>> 
> 
> Good point.  I now understand.  How about this:
> 
> OLD:
> 
>            At least one IETF Hotel has a space for use as a lounge,
>            conducive to planned and ad hoc meetings and chatting, as well
>            as working online. There are tables with seating, convenient for
>            small meetings with laptops. These can be at an open bar or
> casual
>            restaurant. Preferably the lounge area is on the path
> between the
>            meeting rooms and the hotel entrance, and is available all
> day and
>            night.
> 
> NEW:
> 
>            At least one IETF Hotel has a space for use as a lounge,
>            conducive to planned and ad hoc meetings and chatting, as well
>            as working online. There are tables with seating, convenient for
>            small meetings with laptops. These can be at an open bar or
> casual
>            restaurant. When a hotel is collocated with the Facility,
> preferably the
>            lounge area is on the path between the meeting rooms and the
> hotel
>            entrance, and is available all day and night.

To me this thread has moved from a requirement to how it should be implemented.  Isn’t the requirement that we want a lounge?  I don’t think we need to specify where it is in all circumstances.

Bob