Re: [81attendees] sucky Delta hotel network (and bufferbloat)

[John C Klensin <[e-mail]>]

--On Monday, August 01, 2011 22:18 +0100 Maciek Konstantynowicz
<[e-mail]> wrote:

> Thanks for the pointers, will digest.
> 
> The hotel manager I spoke to, didn't even know what IETF is
> about, and didn't expect any excessive WiFi demands breaking
> hotel's Internet access service. Maybe as a community, going
> forward we could provide more candid feedback re Internet/WiFi
> performance during IETF gatherings. Or better give hotel mgmt
> heads-up about coming tsunami of Internet users... so that
> hotel could address it pro-actively..
> 
> The business incentive for the hotel would be to avoid giving
> 20% discounts if things don't work out as per my case :) +
> customer satisfaction.

Sigh.
I used the network in the Delta quite a lot and didn't
experience much of a problem, but kept my expectations set for
"hotel" rather than "IETF".  I also mostly used the wired
Ethernet -- it may be just anecdotal, but I've generally found
that wired Ethernet is much less likely to be problematic than
WiFi if neither is set up by experts.

While warning hotels that we are a collection of heavy Internet
users and that it is a good idea to make sure that their IP
vendors know that they need to tune things up to avoid
embarrassment, the bottom line is that the only times folks seem
to have zero complaints about hotel networks are where the hotel
infrastructure starts out above average and is then hooked into
the IETF network.  It simply isn't plausible to believe that
interconnection will occur with other than the primary hotel.
It would be good to know in advance how likely it is even with
the primary hotel but those opting for other hotels should
arrive with the assumption that they will be dealing with a
generic hotel network and What You Get is What You Get quality
(whether it is free and worth what one pays for it or not).

   john