From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id AF1A93CB37 for ; Wed, 7 Aug 2019 08:03:23 -0400 (EDT) Received: by uplift.swm.pp.se (Postfix, from userid 501) id 703C0B4; Wed, 7 Aug 2019 14:03:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1565179402; bh=y7yifnavSc8xKm/Zr8HW/L8f/89YSKtym8283j2ww0E=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=oJgdg3iD23vsVxY5BLGdmUAhr3+ModWumexRLTgamFXVPzim0C8RldP+flvOL7xHO pG/ZYQcJPh+C71e2OvXYYyqZ6rf5xF0iwIgYbIMYGBr+4ZF8iDufdK8BQ4dcUco5/c +2G6p32tUjoyg6JVafhbliDkkK1awusyu0FBeCPI= Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6DBB2AF; Wed, 7 Aug 2019 14:03:22 +0200 (CEST) Date: Wed, 7 Aug 2019 14:03:22 +0200 (CEST) From: Mikael Abrahamsson To: Jeremy Harris cc: ecn-sane@lists.bufferbloat.net In-Reply-To: Message-ID: References: <364514D5-07F2-4388-A2CD-35ED1AE38405@akamai.com> <4B02593C-E67F-4587-8B7E-9127D029AED9@gmx.de> <34e3b1b0-3c4c-bb6a-82c1-89ac14d5fd2c@bobbriscoe.net> <77522c07-6f2e-2491-ba0e-cbef62aad194@bobbriscoe.net> <619092c0-640f-56c2-19c9-1cc486180c8b@bobbriscoe.net> <3A454B00-AEBC-48B6-9A8A-922C66E884A7@gmx.de> <21E40F44-2151-4565-970E-E1CEBE975036@gmx.de> <58F8052E-A56B-4E1F-8E1D-CBE75A0F7332@akamai.com> <9C42D7E8-734A-4620-B95B-5FFDDF1D3D95@gmail.com> 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: [Ecn-sane] [tsvwg] Compatibility with singlw queue RFC3168 AQMs X-BeenThere: ecn-sane@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of explicit congestion notification's impact on the Internet List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 12:03:23 -0000 On Wed, 7 Aug 2019, Jeremy Harris wrote: > (assuming TCP SACK in use). But the socket interface would need > to present sequencing information along with the segments; it being > no longer implied by the sequence of satisfied reads. Yes, the socket stream interface guarantees ordered delivery of that stream. That doesn't mean other 5 tuple connections running over the same media need to be held up just because a packet is missing from this first stream. A lot of medias guarantees complete ordering, even between flows/streams. If we loosen this requirement then muxed transports or other stream can continue even if there is a packet missing and being ARQed on the media. -- Mikael Abrahamsson email: swmike@swm.pp.se