Re: [EXTERNAL] Re: IETF 104 Registration and Hotel Reservations Openo

Lou Berger <lberger@labn.net> Sun, 06 January 2019 22:05 UTC

Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63314130E5D for <ietf@ietfa.amsl.com>; Sun, 6 Jan 2019 14:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 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=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 DKteHmrrlqA6 for <ietf@ietfa.amsl.com>; Sun, 6 Jan 2019 14:05:06 -0800 (PST)
Received: from outbound-ss-579.bluehost.com (outbound-ss-579.bluehost.com [74.220.218.175]) (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 565DA12D4ED for <ietf@ietf.org>; Sun, 6 Jan 2019 14:05:06 -0800 (PST)
Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id 954011E0E1B for <ietf@ietf.org>; Sun, 6 Jan 2019 15:05:02 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id gGXWgreGDu4p1gGXWgHbRI; Sun, 06 Jan 2019 15:05:02 -0700
X-Authority-Reason: nr=8
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:Cc:To:Subject:Sender:Reply-To: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=EJ6bduFRF+Ci/Si+lCOmKLrqNGuJX7nVr5PWx9QXulI=; b=Q4vmI5pEJyU7YGexhnNWAp3v0M xXUgULQEvkJUMkMm5bmkILBAb8XWkes6+REKLaTp2wTSo11NOpD5Tct0lZmtYHveIxQO8OhgXrte0 YlwEry91YNrAQWiUTui21dTTH;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:36682 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1ggGXW-002dcS-32; Sun, 06 Jan 2019 15:05:02 -0700
Subject: Re: [EXTERNAL] Re: IETF 104 Registration and Hotel Reservations Openo
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: John C Klensin <john-ietf@jck.com>, Alexa Morris <amorris@amsl.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <20181220194742.39286200BC3F9B@ary.qy> <C4C3E99E-7FDF-42AD-8AAF-BA9A7BF9DF62@soton.ac.uk> <alpine.OSX.2.21.1812211147590.48467@ary.qy> <E0B84494-6B60-4AEB-B8E9-8C6F673624FA@tzi.org> <E73FC76E-6CD5-4543-A189-D51ACC7EAEBE@amsl.com> <167d262e9c8.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <23396A80-F252-4FFB-B0D0-B17D86F1C73E@amsl.com> <44640168-deb7-c613-3420-ad5df95b1736@labn.net> <956E76FA5156981CD09F5C1F@PSB> <098ecda6-b344-7cb7-5943-d6279ee89108@labn.net> <7C9DD929-2301-4993-9B03-A15B41B8D664@nbcuni.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <b7ad36a4-2b15-86cf-081d-7b6c087b80c7@labn.net>
Date: Sun, 06 Jan 2019 17:05:00 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <7C9DD929-2301-4993-9B03-A15B41B8D664@nbcuni.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
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: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1ggGXW-002dcS-32
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net ([IPv6:::1]) [72.66.11.201]:36682
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q9AlhFJOwOM0jKNdYicN5J4PdOs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2019 22:05:08 -0000

Glenn,

     I have no issues with the clause if it translates to a reduction in 
our rates.  That hasn't been my experience - the lower rates disappeared 
when the clause was inserted and are  once again gone now that we've 
notified the hotel that they were there.

FWIW I would have pushed this while on the IAOC had I realized the 
practice was still going on.

> I will add that the IETF main mailing list is not the place to debate ietf meeting hotel practices. That belongs on mtgvenue@ietf.org which is the working group for meeting venue stuff.
I'm fine with moving on from the discussion ...

Lou

On 1/6/2019 4:41 PM, Deen, Glenn (NBCUniversal) wrote:
>
>> On Jan 6, 2019, at 12:24 PM, Lou Berger <lberger@labn.net> wrote:
>>
>> Obviously we can't change existing contracts, but we can stop asking that the "no lower rates offered" clause be inserted in future contracts -- again, it is my understanding (which of course can simply be wrong) that this clause was first added to hotel contracts by the IETF, specifically the IAD at that time.
>>
>> Lou
> I’m not sure I agree with you in this.  The purpose of the clause is to say “the IETF negotiated rate is the lowest that the hotel will offer during the meeting window.”  In other words they are agreeing negotiate one rate with the IETF as part of our overall meeting contract and agreeing to also not then go and negotiate a undercutting rate with some travel web site for instance.
>
> One big part of this is intended to make sure the ietf rate is the best rate across its whole block.  Another big part related to the first is that ietf attendees do not need to worry they there was a better deal that they missed because they didn’t spend a couple
> of hours on other travel sites, or a better deal because the booker early or waited.
>
> Being consistent for the whole IETF room block is an important part of this negotiation.   While a hotel may offer a couple of rooms at a discount they certainly aren’t doing that for any number of rooms as big as the ietf block which can be (simplified general numbers here)   600 rooms at say 6 nights for a total of 3600 room nights that are available to IETF attendees all for the same price.
>
> This is as opposed to what I’ve seen on many hotel booking sights where the price changes up or down each night and you are
> competing against every other customer to grab the cheapest rates before they are gone. Or you get a cheap first or last night and pay more for all the others.
>
> This is very different to the ietf rate which is the same for every room night for every attendees and is the same if you book as soon as registration opens or if you book just before arriving.
>
> The ietf gets a consistent and good rate for all its rooms and all times of booking. That’s a huge benefit for ietf participants, especially those that have to wait to get approval before booking their travel.
>
> Opposed to that consistency is the kind of room pricing that places like PriceLine engage in. Sure some individuals can get some deals occasionally, but it’s one thing to compete against the open market especially if you don’t have a particular goal of staying in a specific meeting hotel - it is an entirely different thing to pit IETF attendees against one another to edge out each other for a better room rate while leaving the scraps to those willing to pay the full rack rate when the supply gets low (which is a real and painful part of playing the hotel pricing market place).
>
> So I don’t agree removing the clause is in the best interest of the ietf community.  It requires the hotel to act consistently with all IETFers who book a room at the hotel and it says that they do not need to waste time
> hunting across the hotel discount sites looking for a better deal - because they have already got the best deal to be found on those sites.
>
> I will add that the IETF main mailing list is not the place to debate ietf meeting hotel practices. That belongs on mtgvenue@ietf.org which is the working group for meeting venue stuff.
>
>
> Regards
> Glenn
>
>