Re: [93attendees] Hilton Guest Room Internet Update

"George, Wes" <wesley.george@twcable.com> Thu, 23 July 2015 14:33 UTC

Return-Path: <wesley.george@twcable.com>
X-Original-To: 93attendees@ietfa.amsl.com
Delivered-To: 93attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D4EE1A6FF1 for <93attendees@ietfa.amsl.com>; Thu, 23 Jul 2015 07:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.064
X-Spam-Level: ***
X-Spam-Status: No, score=3.064 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FH_RELAY_NODNS=1.451, HELO_EQ_MODEMCABLE=0.768, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=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 G0AosRA-MzKl for <93attendees@ietfa.amsl.com>; Thu, 23 Jul 2015 07:33:20 -0700 (PDT)
Received: from cdcipgw01.twcable.com (unknown [165.237.91.110]) by ietfa.amsl.com (Postfix) with ESMTP id B72261A87A6 for <93attendees@ietf.org>; Thu, 23 Jul 2015 07:32:53 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="5.15,531,1432612800"; d="scan'208";a="335647357"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdcipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 23 Jul 2015 10:29:48 -0400
Received: from PRVPEXVS10.corp.twcable.com ([10.136.163.41]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Thu, 23 Jul 2015 10:32:52 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Jim Martin <jrmii@isc.org>, "93attendees@ietf.org" <93attendees@ietf.org>
Date: Thu, 23 Jul 2015 10:32:50 -0400
Thread-Topic: [93attendees] Hilton Guest Room Internet Update
Thread-Index: AdDFVHSBJFzl+tS2RS++UNTsk3un+g==
Message-ID: <D1D66BA2.5DDE1%wesley.george@twcable.com>
References: <FB562679-F7EC-4BC5-A66D-8F10300248F4@isc.org>
In-Reply-To: <FB562679-F7EC-4BC5-A66D-8F10300248F4@isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.3.150624
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/gQwdsHY6BOokYxRC7YpunF_do7U>
Subject: Re: [93attendees] Hilton Guest Room Internet Update
X-BeenThere: 93attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 93 attendees that have opted in on this list. " <93attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/93attendees>, <mailto:93attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/93attendees/>
List-Post: <mailto:93attendees@ietf.org>
List-Help: <mailto:93attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/93attendees>, <mailto:93attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2015 14:33:22 -0000

Jim, NOC folks current and past, first let me express how much I
appreciate all of the work you do at making the best of what is often a
very bad situation, in front of a demanding audience.

We were talking the other day in the Captive Portal BoF about ways to make
WiFi suck less for your average user, and it occurred to me that while
captive portals certainly contribute to this, the larger issue is the way
that WiFi networks are built and "maintained", especially when they are at
the limits of their scale. We've all had numerous experiences with really
awful "managed" infrastructure WiFi in public places, airports, hotels,
other conferences, etc. where the system was simply overwhelmed by the
demand or unable to overcome the implementation flaws, so we know that
this is a common problem.
I think that there would be real value in you and some of your fellow
AP-wranglers writing an informational Internet Draft discussing some of
the challenges you've faced and best practices you have learned while
beating wifi into submission for a high-density installation and intensive
user base over multiple years. I don't have much applicable experience to
turn into useful text myself, so I can only offer to get raw text from
other folks squashed into I-D format as an editor, if that would be
helpful. Are there other folks who think that this would be useful or are
willing to contribute?

Thanks,

Wes



On 7/23/15, 9:03 AM, "93attendees on behalf of Jim Martin"
<93attendees-bounces@ietf.org on behalf of jrmii@isc.org> wrote:

>Gentlepeople,
>       First of all, I apologize for the delay in getting everyone an update on
>this. We know the guestroom Internet here in the Hilton has been
>problematic at best, and we have been working to try to improve it for
>the last week. As you probably know, the IETF network provides the IP
>layer and above for the guestrooms and public space, but the physical
>layer, both for the wired and wireless uses the existing hotel
>infrastructure. In the case here in Prague, we’ve been working closely
>with the hotel’s vendor, Mikenopa to deliver this service. They’ve been
>very willing and happy to work with us on this.
>
>       For the wireless, we’ve lit up the “ietf-hotel” ssid on the existing
>APs, both in the public space and guestrooms. These are the same APs that
>provide the “hhonors” SSID. While the APs seem to have been originally
>deployed reasonably, there has been hotel building changes (mostly
>regarding new sprinkler systems) which has had them moved around in the
>hallways to very suboptimal locations. This has led to many areas having
>low to no signal. Additionally, their 2.4G channel assignment and power
>levels weren’t optimal. Mikenopa has been trying to move APs and
>reconfigure the channels.
>
>       Additionally, due to our desire to use public IPv4 space, we’ve seen
>very high broadcast loads. This is based in the fact that we’ve got a
>large block that is sparsely used, and thus when we get scanned (as
>happens constantly from the greater Internet) we get a large amount of
>ARP traffic which can overload the wireless system. We’ve been working on
>various techniques to reduce this load.
>
>       On the wired front, we’ve had reasonably good luck (other than about 45
>minutes of downtime last night with a self inflicted wound while trying
>to reduce the ARP load). Please do use the wired connection in each
>guestroom if at all possible. If you need a cable, it’s usually in a
>cloth bag with a “@“ symbol on it in the desk. If you don’t have one,
>please feel free to come to the NOC.
>
>       Overall, we’ve seen the ietf-hotel work reasonably well in the
>restaurant, lobby and hallways, but poorly (but slowly improving) in the
>guestrooms. We continue to work on this, but using the wired connection
>in your room is probably your best bet.
>
>       - Jim


This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.