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

Roland Bless <roland.bless@kit.edu> Thu, 04 August 2011 20:35 UTC

Return-Path: <roland.bless@kit.edu>
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 0E87D11E8077 for <81attendees@ietfa.amsl.com>; Thu, 4 Aug 2011 13:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.018
X-Spam-Level:
X-Spam-Status: No, score=-6.018 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 7LUOFOEqvuPs for <81attendees@ietfa.amsl.com>; Thu, 4 Aug 2011 13:35:24 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 335AE21F8B0F for <81attendees@ietf.org>; Thu, 4 Aug 2011 13:35:24 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25 id 1Qp4df-0002Cd-HR; Thu, 04 Aug 2011 22:35:38 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 02D67A80025; Thu, 4 Aug 2011 22:35:28 +0200 (CEST)
Message-ID: <4E3B028F.1050603@kit.edu>
Date: Thu, 04 Aug 2011 22:35:27 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: "Carlos M. Martinez" <carlos@lacnic.net>
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> <4E39A542.7040801@freedesktop.org> <4E39A709.4030001@lacnic.net> <4E39AA95.7060601@freedesktop.org> <m21ux2qa01.wl%randy@psg.com> <4E3A9D97.1040509@dcrocker.net> <B819AC736B2D3745ADEA0C285E020CEB0761112F@SV-EXDB-PROD1.infinera.com> <4E3ABFBF.5040101@lacnic.net>
In-Reply-To: <4E3ABFBF.5040101@lacnic.net>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1312490138.266877000
Cc: "81attendees@ietf.org" <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
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: Thu, 04 Aug 2011 20:35:25 -0000

Hi Carlos,

On 04.08.2011 17:50, Carlos M. Martinez wrote:
> I fail to see a better argument for implementing QoS than what happened
> to the Delta Hotel in QC. I agree that QoS has been somewhat bastardized

QoS is there for differentiation of packet/flow treatment,
i.e., managed unfairness, while congestion management tries
to provide fairness between users/flows in a best-effort class.
QoS still doesn't solve the problem of trying to share the capacity
between users in the same QoS class.

> Arguing that every network should always be overprovisioned encourages
> wasteful behaviour on all parts and puts many players in an impossible
> position. It might be not so impossible in the US/Canada (although even

Yes, indeed, DDoS flooding, misbehaving flows and unbalanced traffic
matrices may still cause problems for overprovisioned networks.

> Dropping packets is a bad thing. However, dropping packets blindly (as
> in pretending congestion does not exist) is much worse. The network
> should avoid dropping packets at all costs, but if it has to drop, then
> it should do it smartly and avoid making the situation worse.

Yes, but this is also true for more clever congestion management schemes.

> I do believe there is a management problem in the same sense as there is
> with CGNs and port forwarding, which has lead to the creation of PCP. It
> is basically a remote management protocol allowing customer-provider
> interaction (ATM UNI anyone ??? :-)))) ). Well, maybe we could do
> something for QoS. Phoning your ISP each time you need to forward a port
> is every bit as impracticable as phoning the ISP to create a QoS queue.

There are signaling solutions out there for this, e.g., NSIS
http://tools.ietf.org/wg/nsis/ provided solutions for both
Port management for NAT/Firewalls as well as for QoS signaling.
Giving a tool into the users' hand so that they can actually
decide what is more important and should be treated with better
QoS would be a good thing also from the perspective of net neutrality.
But the complexity of providing everything (control plane + DiffServ
etc.) for QoS support is obviously still a too high effort.

Regards,
 Roland