Re: [homenet] homenet: what now? ... next?
Toke Høiland-Jørgensen <toke@toke.dk> Thu, 14 March 2019 11:58 UTC
Return-Path: <toke@toke.dk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B3B12F1AB for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2019 04:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 gf3HLGaAEH49 for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2019 04:58:50 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [IPv6:2a00:7660:6da:2001::664]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0A1112DF71 for <homenet@ietf.org>; Thu, 14 Mar 2019 04:58:50 -0700 (PDT)
From: Toke Høiland-Jørgensen <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1552564728; bh=A9JkX0j6AdFngSz88JtKUCd/69V1x20gmjab7Re8K6E=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ocDg7UIew8sD/obxDoa0mZYfc6yJ4XdqbXitgzaGnKIv9VY1+2EgulQEC36phDqAo klDgF0/HT2LtSORtGguNQGluflDsPRTaAZ6kI3Qe+z2Cp9FfQLBXQGXswr2U26+zXM +6zKPAeFf8CR0M5KPhDvQ4bHI6L9BJO713KjMFXvYIXg5oVJ5bA5aR7LeslDXQzI/+ SUr8kT5EQoipE/8IT/RgJmGY6ro+9ywDeyPGqsb06bPduCJiVGRaAgaRyyHUBYd4wf ee2jMgF15M3ktDMtwv+GXiZMrP+2hlqNvayaJ6H/FW9r9MGld0n4WbbkVW/zFYOAsP O+3WsTh9Hrnfg==
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet@ietf.org
In-Reply-To: <alpine.DEB.2.20.1903140759060.3161@uplift.swm.pp.se>
References: <894b4181-c4ca-5cf1-adba-1c5fcab0d355@cs.tcd.ie> <90A48EC1-C13D-4B9B-9F04-252C0CC87084@fugue.com> <dbe6e19f-84c2-f2eb-b9ab-d085de7c299c@mtcc.com> <4803.1551485670@localhost> <alpine.DEB.2.20.1903132150430.3161@uplift.swm.pp.se> <87d0mu1nrm.fsf@toke.dk> <alpine.DEB.2.20.1903140759060.3161@uplift.swm.pp.se>
Date: Thu, 14 Mar 2019 11:40:15 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87pnqtzqls.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/aVeGKKT9UnJPKTQbj1HRoy61Hl4>
Subject: Re: [homenet] homenet: what now? ... next?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2019 11:58:53 -0000
Mikael Abrahamsson <swmike@swm.pp.se> writes: > On Wed, 13 Mar 2019, Toke Høiland-Jørgensen wrote: > >> Since you seem to be pretty up to date on the ISP-level CPE offerings, >> just out of curiosity: Do any of these fancy ARM boxes include actual >> fixes for bufferbloat? :) > > Short answer, no. > > Bufferbloat isn't on the radar of any product managers I have talked > to. Cable Labs is the only organisation that seems to do anything > about this that I have seen. Right, yeah, that's what I thought. :/ > I have made statements previously in that context of most newer higer > end devices having packet accelerators which doesn't lend itself to > FQ_CODEL and the rest of the mechanisms the bufferbloat movement has > gravitated towards, but I still feel what I said wasn't really > accepted and "taken in". Well, for my part I have mentally filed this under "vendors don't care", which has been my impression the whole time (with a few exceptions). It's terribly frustrating, but it's not like there's anything I can really do about it, so I've more or less resigned myself to this. You're right that packet accelerators complicate things a bit. I'm not entirely convinced that the "doesn't lend itself to FQ-CoDel and the rest of the mechanisms the bufferbloat movement has gravitated towards" actually *has* to be true, but it's harder to do a proof of concept since the barrier to entry for hardware development is higher. So I doubt anything is likely to happen here unless someone with the resources to do hardware development steps up. But anyway, thanks for confirming by suspicions :) -Toke
- [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? Michael Richardson
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? Ralf Weber
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? Michael Richardson
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- [homenet] -CoDel David R. Oran
- Re: [homenet] -CoDel Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Michael Richardson
- Re: [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Michael Richardson