Re: [88attendees] Fwd: Your recent stay at Hyatt Regency Vancouver

Randell Jesup <rjesup@mozilla.com> Sat, 16 November 2013 13:58 UTC

Return-Path: <rjesup@mozilla.com>
X-Original-To: 88attendees@ietfa.amsl.com
Delivered-To: 88attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3E1711E819D for <88attendees@ietfa.amsl.com>; Sat, 16 Nov 2013 05:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fgomLkO-H4Us for <88attendees@ietfa.amsl.com>; Sat, 16 Nov 2013 05:58:28 -0800 (PST)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id 0D4EB11E80EC for <88attendees@ietf.org>; Sat, 16 Nov 2013 05:58:27 -0800 (PST)
Received: from [192.168.1.12] (pool-173-49-144-199.phlapa.fios.verizon.net [173.49.144.199]) (Authenticated sender: rjesup@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id A4050F208D for <88attendees@ietf.org>; Sat, 16 Nov 2013 05:58:20 -0800 (PST)
Message-ID: <528779B5.9030703@mozilla.com>
Date: Sat, 16 Nov 2013 08:57:09 -0500
From: Randell Jesup <rjesup@mozilla.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: 88attendees@ietf.org
References: <ho26bf7o.8t9ohlwxci3u@login5-be.medallia.com> <9CC8BA35-DAAF-4090-AD9E-69117B775B53@fugue.com> <D87B5E7F-C452-47F8-8681-DFA14BD3723B@gmail.com> <alpine.BSF.2.00.1311152217280.30947@joyce.lan> <5286EE5D.50604@redhat.com>
In-Reply-To: <5286EE5D.50604@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [88attendees] Fwd: Your recent stay at Hyatt Regency Vancouver
X-BeenThere: 88attendees@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list of IETF 88 attendees that have opted in to the list." <88attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/88attendees>, <mailto:88attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/88attendees>
List-Post: <mailto:88attendees@ietf.org>
List-Help: <mailto:88attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/88attendees>, <mailto:88attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Nov 2013 13:58:33 -0000

On 11/15/2013 11:02 PM, Paul Wouters wrote:
> On 11/15/2013 10:19 PM, John R Levine wrote:
>
>> The Fairmont across the street has nice a pool long enough to swim laps, where I never saw anyone else swimming, just using the hot tub,
>>
>> And the elevators have a button in the elevator for each floor, as God intended.
>>
>> Oh. and the coffee from the in-room Keurig machines wasn't bad, particularly considering that they didn't charge for it.
> However, the wifi was mostly unusable and I was lucky to be Canadian and fell back to LTE. I stayed two more days after the IETF, and the wifi worked fine. We
> clearly overloaded it with the IETF, which I hope is fixable for next time.

The Fairmont was wonderful and the staff did a great job, and the hotel, 
while older, is very nice and well-run.  The WiFi there was horrible 
except when the IETF people were away (I'd guess); wired was better.  
Signal levels were pretty poor as well.  I was amused by the "Free 
Viruses" access point....  I was bummed I didn't drop a personal WAP in 
my case to hook to the wired connection.

The MOST annoying thing other than overload (it *is* the IETF after all) 
was the insertion of banner-iframes on http connections.  Tsk tsk (and a 
pain as well).  If I hadn't been busy I'd have gotten someone in the 
Hyatt networking group to set up a proxy we could tunnel through just to 
avoid that.   Hmmmm.  I imagine there are some things that could be done 
to proxy IETF traffic from overflow hotels to the primary (and its 
upstream link).

   Randell Jesup