Re: IETF 104 Registration and Hotel Reservations Openo
Lou Berger <lberger@labn.net> Fri, 21 December 2018 20:09 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 2EB01130E9C for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2018 12:09:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no 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 xc1mNnHioZF1 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2018 12:09:32 -0800 (PST)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) (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 16A68130E94 for <ietf@ietf.org>; Fri, 21 Dec 2018 12:09:32 -0800 (PST)
Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy9.mail.unifiedlayer.com (Postfix) with ESMTP id 7FE011E0845 for <ietf@ietf.org>; Fri, 21 Dec 2018 13:09:20 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id aR6mggzlDqZYcaR6mgp8Yu; Fri, 21 Dec 2018 13:09:20 -0700
X-Authority-Reason: nr=8
X-Authority-Analysis: $(_cmae_reason
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:MIME-Version:Subject:References:In-Reply-To: Message-ID:Date:CC:To:From:Sender:Reply-To:Content-Transfer-Encoding: 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=grpuM+IV26c1K4r/jtm07Gw69IW2gnUgucZqs9C1bzE=; b=ye8sc/8r01y/QRTWNNdWhaxldg nRtqrWF/cX5fEfX1SYBe8sPcQuhsuzbMKmf+51r+oXXgSR1XjAb33K5avxFJb9y7PAgRSNNS8meog PoVxLqTYB4qfKdoUBURz2ppsT;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:48322 helo=[11.4.0.65]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1gaR6l-004JoQ-U5; Fri, 21 Dec 2018 13:09:20 -0700
From: Lou Berger <lberger@labn.net>
To: Alexa Morris <amorris@amsl.com>, Carsten Bormann <cabo@tzi.org>
CC: "Chown T." <tjc@ecs.soton.ac.uk>, John R Levine <johnl@taugh.com>, ietf@ietf.org
Date: Fri, 21 Dec 2018 15:09:17 -0500
Message-ID: <167d262e9c8.27ce.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <E73FC76E-6CD5-4543-A189-D51ACC7EAEBE@amsl.com>
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>
User-Agent: AquaMail/1.18.0-1396 (build: 101800004)
Subject: Re: IETF 104 Registration and Hotel Reservations Openo
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------167d262eaa73aeb27ceef5c3e5"
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: 1gaR6l-004JoQ-U5
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net ([11.4.0.65]) [72.66.11.201]:48322
X-Source-Auth: lberger@labn.net
X-Email-Count: 1
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9sjGVMd5viZ9GwpzDMjlWTEXFUg>
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: Fri, 21 Dec 2018 20:09:34 -0000
Hi Alexa, Thanks for this mail, see below for a couple of responses. ---------- On December 21, 2018 2:02:06 PM Alexa Morris <amorris@amsl.com> wrote: > Hi Everyone, > > It’s clear that there is some confusion about IETF 104 guest rooms rates > and the cancelation policy, so let me attempt to clarify. > > The Secretariat performs weekly audits to verify that the IETF has the > lowest rate offered to anyone; per the terms of our contract, no other > individual or group holding a meeting at the venue during our dates can > secure lower rates, even through discount travel websites (e.g., > Travelocity, Expedia). Please note that corporate rates are an exception, > as large companies may have their own contractual relationships with > specific hotel chains. > > During this week's audit, we discovered several instances where our room > rate guarantee was not being honored. This has since been corrected and we > will continue to perform weekly audits. > if this is corrected by lowering the right to the ietf, I think this is a fantastic thing. If this is corrected by removing that alternate source for lower rates, I have no idea why this would be in our interest or why we would expend resources trying to enforce that. I really hope it's the former not the latter. > Some of you have also expressed confusion about the Hilton’s cancellation > policy for IETF 104. We will work with the Hilton to clarify the language > on their reservation site, but it’s not possible to make changes until > 2019. In the meantime, the cancellation policy is stated on the IETF > website (make sure you select the “In Depth” tab from > https://www.ietf.org/how/meetings/104/hotel/) and explained below: > > * You may cancel your reservation without penalty up to 21 days prior to > arrival date. I'm a bit surprised to see this 21-day cancellation clause. Of course if this allowed us to get a lower rate or some other major concession, it seems well worth it. Also thank you for clarifying the other points below. Lou > * All reservations must be accompanied by a valid credit card which shall > be charged on the cut-off date (10 March 2019) for three nights room and tax. > * If you decide to cancel your room reservation less than 14 days prior to > your arrival date, the hotel reserves the right to charge you for your full > length of stay. > > If you have any other questions about your hotel reservation and/or if you > discover a rate advertised online that is lower than the IETF guest room > rate of Kč 3,850, please send a message to ietf-registrar@ietf.org and we > will follow up. > > Regards, > > Alexa Morris > Managing Director, IETF Secretariat > > >> On Dec 21, 2018, at 8:58 AM, Carsten Bormann <cabo@tzi.org> wrote: >> >> On Dec 21, 2018, at 17:48, John R Levine <johnl@taugh.com> wrote: >>> >>>> "This reservation requires a credit card deposit of 3,850.00 Kč CZK for 3 >>>> nights which will be charged to your card." >>> >>> It may say that, but there's nothing charged to my card. Did they charge >>> yours? >> >> None of my credit card providers shows me the deposits I have made using >> their cards. >> Does yours? >> >> Grüße, Carsten >> >
- 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