Re: [EXTERNAL] Re: IETF 104 Registration and Hotel Reservations Openo
Mary B <mary.h.barnes@gmail.com> Mon, 07 January 2019 14:53 UTC
Return-Path: <mary.h.barnes@gmail.com>
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 DB8BE130EAA for <ietf@ietfa.amsl.com>; Mon, 7 Jan 2019 06:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_RED=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 GjHk7Z1Al1F1 for <ietf@ietfa.amsl.com>; Mon, 7 Jan 2019 06:53:24 -0800 (PST)
Received: from mail-it1-x133.google.com (mail-it1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 DF5CF130E9E for <ietf@ietf.org>; Mon, 7 Jan 2019 06:53:23 -0800 (PST)
Received: by mail-it1-x133.google.com with SMTP id i145so1446133ita.4 for <ietf@ietf.org>; Mon, 07 Jan 2019 06:53:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dftqqC6WdVGL/C7/7K7FCCqduSnUfIJfUGJoI1o7Vq0=; b=QWEhO3QtLukCqSlXgiJYF8qAzWZrHmtRUHNtsLeUp0TB6WgWLpuqkPQlZl1UYj23dr ylRYuu7lzrwkdnkvDIk354D7DkNXNDa0sxR4uCOoXqWE/OpzCNXSGgWM8jDbzZ7wfkVo RIgISLaxYxkCTst65oQ8aUUupTRoGcVyV2Pq4VCdf24FmYnsZXJMIxGPjC5MpZJJqfLP X9PNJIKzLdrHYNPSCmWTcxzd4QpVXHAlkl3Yo847iv17ltjrDlFS7Dt3dwCJVABUaQ1w 37vJZxN+PLRn7UAYHj9mmFJ/LEpoGjtubxLumlHMeCQPh4h2/AHEe9HyED4HSpmq2r1x auXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dftqqC6WdVGL/C7/7K7FCCqduSnUfIJfUGJoI1o7Vq0=; b=lckanoXIouX3x3aSGKUKtLf8UD48/onZLjWHZAm9WGSWRIDzBUVMJvy6ytkF6Ni7D/ TT6Qo+R0jxDf9UXU+XT6ZqyiOPpnm/0vpkaYIkUDPwZctM0P/fjZPmSNcx5Zp9lLsgFX l2bV4Efp5NVfefof4wBRBebgMLm4ZXZT0rXejreI504gdNnk0cSYVu/LIleJ4EgOM4tm Vx+AZ7am+bdyf9HFUtxGJ31iYgpmtOnNjh+J4rGdOCYRzbp6Bbm2AUbGlLK4SAkH+Or6 exvPcDsmucB6BVBuqzWRO5HIiYKmGLt1iN2Xpgas/AMcooPWRsswhYaKRnRLXWTEI8B7 oMrg==
X-Gm-Message-State: AJcUukd2gNE6KT8vyHbZLQRbV58348tjV3OsUfKH/FsLdPjOzX0TTJJH ZsaeXSLRQuMKWc9xg3kgeD+fM80s76zS//Cm46E=
X-Google-Smtp-Source: ALg8bN4EN62K58jo4sba/I3B9Wgz92ELgpeWcINXJ+JOQpNzeeylkNthy9YugT1VYXpyiJID3XVK6J5jUBD8es6Ywcw=
X-Received: by 2002:a05:660c:128c:: with SMTP id s12mr5767930ita.145.1546872803162; Mon, 07 Jan 2019 06:53:23 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <7C9DD929-2301-4993-9B03-A15B41B8D664@nbcuni.com>
From: Mary B <mary.h.barnes@gmail.com>
Date: Mon, 07 Jan 2019 08:53:11 -0600
Message-ID: <CABmDk8nSnkN=+SFE-t_dAr67OmOG1s2ipE_o1VS_J1vMokHi3A@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: IETF 104 Registration and Hotel Reservations Openo
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>
Content-Type: multipart/alternative; boundary="000000000000f1fd9a057edf635a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KdgCkxkC2Od6rrAohkJkIXu1vO4>
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: Mon, 07 Jan 2019 14:53:27 -0000
Just as an aside, the lower rates weren't on another booking website. They were on the Hilton.com website. I will also note that some of the ones available on hilton.com were noted to be recently remodeled rooms. I didn't see that for the IETF room block. Given past experiences with the difference between refurbed rooms and non-refurbed, this is a bigger deal IMHO. Personally, I don't think the general notion of lower priced options is a big issue either way since IETF meeting hotel almost always sells out quickly. And, breakfast was included in IETF rate and not in some of the other rates, so I think the other rates were likely fairly equivalent in that regards. Now, Prague maybe different in terms of filling the room block because we've been there a number of times, so folks may have optimized their search for lower price options as is. Regards, Mary. On Sun, Jan 6, 2019 at 3:41 PM Deen, Glenn (NBCUniversal) < Glenn.Deen@nbcuni.com> 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 > >
- IETF 104 Registration and Hotel Reservations Openo IETF Secretariat
- Re: IETF 104 Registration and Hotel Reservations … Paul Wouters
- Re: IETF 104 Registration and Hotel Reservations … Alexa Morris
- RE: IETF 104 Registration and Hotel Reservations … Jeffrey (Zhaohui) Zhang
- Re: IETF 104 Registration and Hotel Reservations … Chown T.
- Re: IETF 104 Registration and Hotel Reservations … Andrew G. Malis
- Re: IETF 104 Registration and Hotel Reservations … Chown T.
- Re: IETF 104 Registration and Hotel Reservations … John Levine
- Re: IETF 104 Registration and Hotel Reservations … Giovane Moura
- Re: IETF 104 Registration and Hotel Reservations … Chown T.
- Re: IETF 104 Registration and Hotel Reservations … Andrew G. Malis
- Re: IETF 104 Registration and Hotel Reservations … John R Levine
- Re: IETF 104 Registration and Hotel Reservations … Carsten Bormann
- Re: IETF 104 Registration and Hotel Reservations … Alexa Morris
- Re: IETF 104 Registration and Hotel Reservations … Lou Berger
- Re: IETF 104 Registration and Hotel Reservations … Alexa Morris
- Re: IETF 104 Registration and Hotel Reservations … Udeme Ukutt
- Re: IETF 104 Registration and Hotel Reservations … Lou Berger
- Re: IETF 104 Registration and Hotel Reservations … John C Klensin
- Re: IETF 104 Registration and Hotel Reservations … Lou Berger
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Deen, Glenn (NBCUniversal)
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Lou Berger
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Mary B
- Re: [EXTERNAL] IETF 104 Registration and Hotel Re… Eric Burger
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Christian Hopps
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Ted Lemon
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Christian Hopps
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Ted Lemon
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Michael Richardson
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Andrew G. Malis
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Ted Lemon
- Re: [EXTERNAL] Re: IETF 104 Registration and Hote… Mary B
- RE: [EXTERNAL] Re: IETF 104 Registration and Hote… Belotti, Sergio (Nokia - IT/Vimercate)
- Re: [EXTERNAL] IETF 104 Registration and Hotel Re… Yoav Nir