Re: [homenet] homenet: what now? ... next?

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 14 March 2019 12:53 UTC

Return-Path: <swmike@swm.pp.se>
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 51BBA130DC2 for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2019 05:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 S1K4o4Jlpm5a for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2019 05:53:52 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 BFED4130E2E for <homenet@ietf.org>; Thu, 14 Mar 2019 05:53:52 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 811AEB3; Thu, 14 Mar 2019 13:53:49 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1552568029; bh=Kx9DxOrhfYCFHX6MnYTMZbnlcdrYGjQLZ1eHYTIptUo=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WsHpMSvTF1ooH3ur9LkpJ6Kco4S6IEroJ1lwH4RrgEL3Jv9NGJLjf09rbK9Mq3mbN 95KicSmxG2bpUNXvCvHLL+xR7mqrBfy9OBZ0cQjowcNEw6vTkpyS34cUpP6AymPQ5/ PJEInT0bKeUBF4ZenlEKu/xCXgi00/GbKpdjMXCo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7D614B2; Thu, 14 Mar 2019 13:53:49 +0100 (CET)
Date: Thu, 14 Mar 2019 13:53:49 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toke Høiland-Jørgensen <toke@toke.dk>
cc: homenet@ietf.org
In-Reply-To: <87pnqtzqls.fsf@toke.dk>
Message-ID: <alpine.DEB.2.20.1903141318260.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> <87pnqtzqls.fsf@toke.dk>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="-137064504-444094545-1552568029=:3161"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/WtYPCVv82kFOUUcI5X9-BJRZXTQ>
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 12:54:09 -0000

On Thu, 14 Mar 2019, Toke Høiland-Jørgensen wrote:

> 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.

The people with hardware experience want to do PIE, because it lends 
itself better for implementation in existing hardware, or hardware with 
small modification.

Sometimes it's better to accept non-perfect more easily implementable 
solutions that solves most of the problem space, instead of aiming for the 
"perfect one" and getting nothing.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se