From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 484F53BA8E for ; Sun, 26 Nov 2017 07:20:30 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1511698827; bh=0FaJbVc6T0suhvTbiH6EA1RuQVLz/zwdwJi/Eu4zGW0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=I7xWvAwHRx0wAvBth84CFF7eYZ+bhl/opthsVp7o7IQEFlPOFUN2D58Y9/Acs3OZl VFryvncks2oMgBwnYdzhP6JoT1FUe9pLAhWl8Q3Ia884IlLIf6KZZAhzxmiQ7ehHkG DthMomCfO+xRxjHsqkKAIGNg1Dv/cqxzfsMk1lb/rM1tNasVaU5slWSNd4otMNTOir Zx6A6lL9wn42saKhyaGpq4QQ0bPEVKDt2ELpbgbuz2b5JG75CSNlojx9DSLGb33hIh Un33+qsrZu23VNsSEjCUNq1uyaIs4vVzTAFDKdUmBBizoJyTdHwI12XQ+3NT2IHJzG 9zcXNNgkjVEgw== To: Martin Geddes , Dave Taht Cc: bloat In-Reply-To: References: Date: Sun, 26 Nov 2017 13:20:26 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87shd18c51.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Bloat] Bufferbloat in high resolution + non-stationarity X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2017 12:20:30 -0000 Martin Geddes writes: > It doesn't matter what scheduling algorithm you build if it creates > arbitrage or denial-of-service attacks that can arm a systemic > collapse hazard. The good news is we have a new class of scheduling > technology (that works on a different paradigm) that can fully address > all of the requirements. We are currently deploying it to enable the > world's first commercial quality-assured broadband service. Could you point to any research papers describing this technology? Would be interesting to read up on... -Toke