From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <swmike@swm.pp.se>
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id D07A03B29E;
 Mon, 11 Mar 2019 04:23:15 -0400 (EDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501)
 id 6425EB2; Mon, 11 Mar 2019 09:23:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail;
 t=1552292594; bh=IbNzl/Z3Wi0fUeUrc5oKDfrflQXQ8Sfmn5mwg5zlOOU=;
 h=Date:From:To:cc:Subject:In-Reply-To:References:From;
 b=C7hiQNc7zOlvTj612A8YOVGF9ecMOm4vx606R2poKL/T6UAja21BopGudBvz+HuZQ
 nPu69SxBbzsnyB5oVuBKPGuVIf+y3NdoS8FyLA0LMV2TWT310987gX6/X4L5sh4+xr
 ZNAEJ5HUN6KT6swAwv+9zTNuX51B+Q/uFoQcvOWY=
Received: from localhost (localhost [127.0.0.1])
 by uplift.swm.pp.se (Postfix) with ESMTP id 61B78B0;
 Mon, 11 Mar 2019 09:23:14 +0100 (CET)
Date: Mon, 11 Mar 2019 09:23:14 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Sebastian Moeller <moeller0@gmx.de>
cc: Jonathan Morton <chromatix99@gmail.com>, 
 Cake List <cake@lists.bufferbloat.net>, 
 "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>, 
 "Holland, Jake" <jholland@akamai.com>, 
 "ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>, 
 bloat <bloat@lists.bufferbloat.net>
In-Reply-To: <CC550FC8-6025-4063-BD72-1704F54D40FD@gmx.de>
Message-ID: <alpine.DEB.2.20.1903110920550.3161@uplift.swm.pp.se>
References: <CAA93jw5VWSz67znZq_FKt01D89uaTSHL3xb9SzLPZwdpshe0TA@mail.gmail.com>
 <550C0248-1704-49DA-ABDC-49A91E0AC6F3@akamai.com>
 <1EE25778-8571-4506-A334-38C544470ACE@gmail.com>
 <alpine.DEB.2.20.1903110800310.3161@uplift.swm.pp.se>
 <CC550FC8-6025-4063-BD72-1704F54D40FD@gmx.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Re: [Cake] [Bloat] The "Some Congestion Experienced" ECN codepoint
 - a new internet draft -
X-BeenThere: cake@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Cake - FQ_codel the next generation <cake.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cake>,
 <mailto:cake-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cake>
List-Post: <mailto:cake@lists.bufferbloat.net>
List-Help: <mailto:cake-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cake>,
 <mailto:cake-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2019 08:23:16 -0000

On Mon, 11 Mar 2019, Sebastian Moeller wrote:

> 	How is packet reordering for anybody but the folks responsible for 
> operating the "conduits" in any way attractive?

For instance QUIC uses muxing of streams within the same 5 tuple, so it 
has use of the transport not holding up information just to preserve 
ordering within the 5 tuple stream.

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