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

Christian Hopps <chopps@chopps.org> Tue, 15 January 2019 14:58 UTC

Return-Path: <chopps@chopps.org>
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 E1D9412D4E7 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2019 06:58:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 HoDABCAIu6zz for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2019 06:58:56 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id BC68C129A87 for <ietf@ietf.org>; Tue, 15 Jan 2019 06:58:56 -0800 (PST)
Received: from tops.chopps.org (47-50-69-38.static.klmz.mi.charter.com [47.50.69.38]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 7922060428; Tue, 15 Jan 2019 09:58:55 -0500 (EST)
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>
User-agent: mu4e 1.0; emacs 26.1
From: Christian Hopps <chopps@chopps.org>
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: Lou Berger <lberger@labn.net>, John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [EXTERNAL] Re: IETF 104 Registration and Hotel Reservations Openo
In-reply-to: <7C9DD929-2301-4993-9B03-A15B41B8D664@nbcuni.com>
Date: Tue, 15 Jan 2019 09:58:54 -0500
Message-ID: <sa6va2qotld.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MDKFXiaPzJpI67OlyFC8wNdkGu0>
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: Tue, 15 Jan 2019 14:58:59 -0000

Why not KISS? IETF should negotiate a fair rate that is worth what we will be paying *upfront*, and leave it at that.

Notwithstanding the complex turns of logic presented on this thread, it just feels wrong for me to find a better deal only to have IETF come in take it away from me.

Thanks,
Chris.

Deen, Glenn (NBCUniversal) <Glenn.Deen@nbcuni.com> writes:

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