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

Ole Jacobsen <ole@cisco.com> Wed, 03 August 2011 18:45 UTC

Return-Path: <ole@cisco.com>
X-Original-To: 81attendees@ietfa.amsl.com
Delivered-To: 81attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A9211E8090 for <81attendees@ietfa.amsl.com>; Wed, 3 Aug 2011 11:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.722
X-Spam-Level:
X-Spam-Status: No, score=-102.722 tagged_above=-999 required=5 tests=[AWL=-0.123, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EJPqQGF3XNs6 for <81attendees@ietfa.amsl.com>; Wed, 3 Aug 2011 11:45:16 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 5526D11E80B0 for <81attendees@ietf.org>; Wed, 3 Aug 2011 11:45:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=2978; q=dns/txt; s=iport; t=1312397128; x=1313606728; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=KUwqJZjNyPcp1Zt/xr/5Zkz/Psmx+KlA4oSkgGcfUMA=; b=eFe4Ai1C/iLfi8KQLIX/2/4+t3yOSUBtH0bz0Zkv2kBIeKIBQwTkzSMd H40Wk33FIO4F6aHTPneOgPmxqSR6nibj+bEdEbDKHiryg4mKX0tz+lHgo NJc+uT5S2AHpm8MOAalO01fUh7C/J1YmUctGPTarnzHaaPF+mGfUhE45c E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJGWOU6rRDoG/2dsb2JhbAA8Bqdgd4FAAQEBAQIBEgECASQ/BQsLGC5XBjWHSqI2AYMcDwGKOpEDgy+DEwSHWpwl
X-IronPort-AV: E=Sophos;i="4.67,311,1309737600"; d="scan'208";a="9360842"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-2.cisco.com with ESMTP; 03 Aug 2011 18:45:27 +0000
Received: from sjc-vpn7-506.cisco.com (sjc-vpn7-506.cisco.com [10.21.145.250]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p73IjQEp017408; Wed, 3 Aug 2011 18:45:27 GMT
Date: Wed, 03 Aug 2011 11:45:26 -0700
From: Ole Jacobsen <ole@cisco.com>
To: John C Klensin <john@jck.com>
In-Reply-To: <A4571C8ADA291991207AA961@PST.JCK.COM>
Message-ID: <alpine.OSX.2.01.1108031136240.2965@sjc-vpn7-506.cisco.com>
References: <4E2CC532.3090209@sunet.se> <4E2CCE72.3010500@sunet.se> <4E2E2236.2060808@sunet.se> <87EC2139-C7C2-4113-97E2-9EB9DA2406EA@juniper.net> <alpine.BSF.2.00.1107262259400.80739@joyce.lan> <9D00CDB7-2C04-446E-8D53-0552BAEE22EE@juniper.net> <633EAF31-607E-4FEF-B502-5FFAD89BF01A@juniper.net> <4E371370.40804@freedesktop.org> <00E8AAF99E25FF49A1F55E9A0CD19EBCB93DF4E65B@SGSINSXCHMBSA2.sg.alcatel-lucent.com> <CE4DBD9C-E366-400B-9B39-F86D591F25AB@juniper.net> <98F2DACCFC679BFB8A8E3592@PST.JCK.COM> <alpine.OSX.2.01.1108011457500.20499@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E397AC2.1010906@dcrocker.net> <alpine.OSX.2.01.1108031009120.2965@sjc-vpn7-506.cisco.com> <A4571C8ADA291991207AA961@PST.JCK.COM>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: dcrocker@bbiw.net, 81attendees@ietf.org
Subject: Re: [81attendees] sucky Delta hotel network (and bufferbloat)
X-BeenThere: 81attendees@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF 81 Attendee List <81attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/81attendees>, <mailto:81attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/81attendees>
List-Post: <mailto:81attendees@ietf.org>
List-Help: <mailto:81attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/81attendees>, <mailto:81attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:45:16 -0000

On Wed, 3 Aug 2011, John C Klensin wrote:
>
> Ole,
> 
> Sure, but...
> 
> First of all, while I think it is sensible and prudent for 
> IETF-related guests to avoid, e.g., extensive movie downloads on 
> already-overloaded hotel networks, I don't think we should be 
> spending energy worrying about or casting blame on IETF participants 
> as network abusers.  If, e.g., some movie downloaders are going to 
> cause poor network performance, almost any guest with a laptop can 
> induce the same problem.

I wasn't suggesting otherwise. All I am saying is that we have some 
actual data on typical useage of IETF guests (whether reasonable or
not) and we could maybe use this data to judge if an overflow hotel
is likely or not going to be able to deal with such a load. Again,
nothing scientific and, yes, other "abusers" may exist -- not that
I am calling them that.

> 
> In my experience, many, if not most, hotel networks are woefully
> underprovisioned.  Sometimes that is just cutting costs,
> sometimes it it having installed network arrangements when one
> guest in 20 (or one in 50) used them, only to see that number
> rise to one in five (or, with an IETF group, 49 of 50).
> Sometimes it is just ignorance and/or stupidity.  But the effect
> is the same.  

I agree.

> 
> In addition, while the problems are often with the available
> bandwidth on the hotel's connections to the outside world,
> underprovisioned or congested hotel LANs aren't unusual either.
> I don't think any estimate or report of total available
> bandwidth is going to help.   

Well, it may be a starting point, that's all. And since the underlying 
thread here is "you should have known/told us that the Delta network
was going to suck" we can either try give some indication of this or
we can simply say "you're on your own".

> 
> That brings me back to three things as being potentially useful:
> 
> -- When a block of rooms is negotiated with a particular hotel,
> especially if "free Internet" is part of the negotiation, we
> should exert reasonable efforts to be sure that the hotel
> understands that we tend to all arrive with computers, than we
> tend to be heavy and demanding network users, and that poor or
> sucky Internet service is likely to result in a lot of irritated
> (and probably irritating) customers.

That is already being done.

> 
> -- Independent of how well or poorly a hotel responds to advice
> of that type, we should all understand --with reminder warnings
> as appropriate-- that random-hotel Internet service is often
> going to suck when a much larger-than-usual  percentage of the
> guests are intense Internet users, or Internet users at all.

I agree.

> 
> -- And all of us should be courteous enough to each other, and
> adult enough, to cut back on any bandwidth-hogging activities at
> the first sign of hotel network problems.

Absolutely. 

>    john
> 
> 

Ole