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

Toke Høiland-Jørgensen <toke@toke.dk> Thu, 14 March 2019 13:48 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 E53FC130E2B for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2019 06:48:37 -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 Z0D9G9WUTtBn for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2019 06:48:36 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (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 D8000130E11 for <homenet@ietf.org>; Thu, 14 Mar 2019 06:48:35 -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=1552571313; bh=SKQGh7J1f9W5xE3UqC+DWs3G0dO20DgBZOtifYDbeYQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=h6jv1GLp2ETLM/wT28JYuwIA933AG+xVT9EEF5hubXD0iwBHDANcoGO63es1IpSHN Km7abOQva0bgAhPvIemfoEpfoTjFOHQA/0Mq3pSLFH+dRPNxnj8kFLSan6jToU5LUx wUmhMLmpI+36kDQxvSBimPYAKElb4y+SNpZcdCS5GaLf38i7qTy2SjgvOC+IJsQ8rV WHUhLhAeT+AyW4vWcZU8W2Dj1xfrNcKrqslKem60E4Tm0G9srCnR05T8DvHuQTcXxG 8UtzqluWBy+oai1Sf80+hw79IfvwzfY59y+lv8CjQl5u5f5q2fRNKBraP39cZLfch7 YVWertvzg1yzQ==
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: homenet@ietf.org
In-Reply-To: <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> <alpine.DEB.2.20.1903141318260.3161@uplift.swm.pp.se>
Date: Thu, 14 Mar 2019 14:48:30 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87bm2dzhw1.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/F6Rx8RJ8A5gUKHd5M77WBNsxnP8>
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 13:48:38 -0000

Mikael Abrahamsson <swmike@swm.pp.se> writes:

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

Absolutely, I'm all for that. But even something that is as
retrofitable[0] as PIE is not getting implemented... So then what to do?
This makes it difficult to motivate spending more resources on doing
more work in this area... :/

-Toke

[0] "Retrofitable" is totally a word...