Re: Robustness to packet reordering
Martin Thomson <mt@lowentropy.net> Thu, 06 February 2025 20:56 UTC
Return-Path: <mt@lowentropy.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49500C18DBBA; Thu, 6 Feb 2025 12:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b="eabcVIYI"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="N2owLsSv"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPeCguddDgl6; Thu, 6 Feb 2025 12:56:10 -0800 (PST)
Received: from fout-a6-smtp.messagingengine.com (fout-a6-smtp.messagingengine.com [103.168.172.149]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0863C26F26D; Thu, 6 Feb 2025 12:55:44 -0800 (PST)
Received: from phl-compute-05.internal (phl-compute-05.phl.internal [10.202.2.45]) by mailfout.phl.internal (Postfix) with ESMTP id 0A840138025C; Thu, 6 Feb 2025 15:55:44 -0500 (EST)
Received: from phl-imap-08 ([10.202.2.84]) by phl-compute-05.internal (MEProxy); Thu, 06 Feb 2025 15:55:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm1; t=1738875344; x=1738961744; bh=zgm8kbh3anEhjvgBDaq0lVnf/+UtKoOg eqp/uAjkSNA=; b=eabcVIYIdEBr6o87PdKwMDZSwjy2ovnLFLZwE3XbCDuVk3X1 +kWQH+79fa1l4yHqbToeJxTJ30KlA/+WXS4fmWHGgCIwhV0/pdtd6As0m9shQ2XD e+99Rojxef1EKbrf/0jH4oosX4eJk5DXJt3wdz5mqen6gsiqyesOXVp2RzjmpcJc +hcXHAJXq/pkGbBxcAaa1hGd9+WM38OgnE/TmmRIDNM86reK34/FdBFvCJPpwhjB PBdGXAvkjnqyu9IGm90lepHH3e1p3+yeqbRK7RybZkpKTwa8JNSYUq5gCgr8fU+A 2b9KKYY+Koths1908loYaqG9iInxCou8JqaoQw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1738875344; x= 1738961744; bh=zgm8kbh3anEhjvgBDaq0lVnf/+UtKoOgeqp/uAjkSNA=; b=N 2owLsSvxIEUheTKv2ZS8XmLcgkfYwOH8rarQzEjStdTXqXedK1mvfOR12BQaSziE k1W32u80DPsW7eV8p7hln+gikIix9+UcuKgDi1th0KiUzFcfA0z6uodjCiBmgA78 eMGLUE5Xui0E42LHd0NYW1wIbukrbBGbAt4eQWEN/3Kn5VrZibqOribSNRlB9bGW ZTzC7SP5WBodV87bP3C2m/r0YLAn2wVF9Qi2LxzOtN8EIh3s/OUNJfPKbKQmJBRD 7K+oAH/7hKQf8/fzCQRsMMArE5M5e0lFiuclSHZsDGnqROVhV8vpEdU2P6nszpep 2VwIrUk0pJiHWSVoln4CQ==
X-ME-Sender: <xms:zyGlZ4WluWV9ImjPQ3zGcwEkrDzt86uX5FcKLbVwotdo-ilG_rnfkA> <xme:zyGlZ8kTU095REPI3XzO03swaGfLQB0Pth6pBxIykGYw2XnKaZDg6YbME3KUCAWPl 0GgQbt6DVrAzcU79mI>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvjeeflecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefoggffhffvvefkjghfufgtgfesthejredtredt tdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnth hrohhphidrnhgvtheqnecuggftrfgrthhtvghrnheptddvteejkeegleelleetkeejhfet iedvkefgueejvdevudffhedvfedtveegffdtnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvthdpnhgs pghrtghpthhtohepiedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepghdrfihhih htvgepgedttggrsghlvghlrggsshdrtghomhesughmrghrtgdrihgvthhfrdhorhhgpdhr tghpthhtohepihhnghgvmhgrrhdrshdrjhhohhgrnhhsshhonhepgedtvghrihgtshhsoh hnrdgtohhmsegumhgrrhgtrdhivghtfhdrohhrghdprhgtphhtthhopehinhhgvghmrghr rdhsrdhjohhhrghnshhsohhnsegvrhhitghsshhonhdrtghomhdprhgtphhtthhopehhuh hithgvmhgrsehhuhhithgvmhgrrdhnvghtpdhrtghpthhtohepqhhuihgtsehivghtfhdr ohhrghdprhgtphhtthhopehtshhvfihgsehivghtfhdrohhrgh
X-ME-Proxy: <xmx:zyGlZ8Za0uzS3wO6591fKwCDEesKDnr8hBOOaVuIsNH6Y5hgyVLaIg> <xmx:zyGlZ3X2iXpUjzc236kv-nNGEYna0pOfOsAmd5rkOeWLZBIkHyBZNg> <xmx:zyGlZynSSgabWqc4Vze7DQWnDWEDX3hPpKCJzOCLDN2VCSL9shcY0g> <xmx:zyGlZ8ftXrOTgFIuePCUdJeuL0jY2sY0GIPANLtUC7cd9nsh5okzBg> <xmx:0CGlZ5ut1gdziRiF7LgtCjlUyVooIG55mJBZ3HZiYS8zad_RDX-ewG7e>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.phl.internal (Postfix, from userid 501) id 800C918A006B; Thu, 6 Feb 2025 15:55:43 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
MIME-Version: 1.0
X-ThreadId: T578a387fb5cb0867
Date: Fri, 07 Feb 2025 07:55:23 +1100
From: Martin Thomson <mt@lowentropy.net>
To: Greg White <g.white=40CableLabs.com@dmarc.ietf.org>, Ingemar Johansson S <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org>, Christian Huitema <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Message-Id: <df289f06-2e00-463c-b9f5-bb67a34d9b43@betaapp.fastmail.com>
In-Reply-To: <5C5E0FCB-1725-4775-9421-F4F5F687D051@CableLabs.com>
References: <AM8PR07MB81375E2D3CA840AEDA0F7E63C2F72@AM8PR07MB8137.eurprd07.prod.outlook.com> <38891fa7-b188-4767-8364-ae0a10c318b2@huitema.net> <AM8PR07MB81370760A8293580DDDB386BC2F62@AM8PR07MB8137.eurprd07.prod.outlook.com> <537f0095-68a3-43d5-a2f0-f91b4499017d@huitema.net> <AM8PR07MB81377C0A967260302A687113C2F62@AM8PR07MB8137.eurprd07.prod.outlook.com> <5C5E0FCB-1725-4775-9421-F4F5F687D051@CableLabs.com>
Subject: Re: Robustness to packet reordering
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-ID-Hash: W4LSTZO2HRYH2SAM4FTPD4Q3E7WC5J7Y
X-Message-ID-Hash: W4LSTZO2HRYH2SAM4FTPD4Q3E7WC5J7Y
X-MailFrom: mt@lowentropy.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-quic.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/IC1lrz9KtF2BulQ_uqMXMqguGd0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>
On Fri, Feb 7, 2025, at 04:59, Greg White wrote: > This is an important topic relating to the expectations and > requirements that transport protocols place on layer 2 protocols. In > layer 2 standards bodies that I've been involved in, it has been > understood that "the upper layers" expect in-order delivery, As far as QUIC goes, it is sensitive to reordering in the network. Some reordering will be interpreted as damage (Christian cited the relevant parts) and performance suffers in a few minor way when things arrive out of order (ACKs are less efficient, data needs to be held, memory accesses are less likely to be contiguous, etc...). However, the idea that the network might seek to "fix" these problems, when doing so necessarily involves extra work and delays, is not a good trade. Stuff that is delayed to "fix" a reordering that happened might delay signals that the QUIC stack could use, even if some data needs to be held at the endpoint. QUIC packets contain many things, some of which don't need to be strictly ordered to be useful. That's QUIC though. As you note, L2 isn't necessarily aware of what the upper layers are getting up to. But I understand that TCP is getting better too.
- Robustness to packet reordering Ingemar Johansson S
- Re: Robustness to packet reordering Christian Huitema
- RE: Robustness to packet reordering Ingemar Johansson S
- Re: Robustness to packet reordering Christian Huitema
- RE: Robustness to packet reordering Ingemar Johansson S
- RE: Robustness to packet reordering Floris Bruynooghe
- Re: Robustness to packet reordering Christian Huitema
- Re: Robustness to packet reordering Greg White
- Re: [tsvwg] Re: Robustness to packet reordering Joe Touch
- Re: [tsvwg] Re: Robustness to packet reordering Tom Herbert
- Re: Robustness to packet reordering Martin Thomson
- Re: Robustness to packet reordering Christian Huitema
- Re: [tsvwg] Re: Robustness to packet reordering David Schinazi
- Re: [tsvwg] Re: Robustness to packet reordering Neal Cardwell
- Re: [tsvwg] Re: Robustness to packet reordering Martin Thomson
- Re: [tsvwg] Re: Robustness to packet reordering Christian Huitema
- RE: [tsvwg] Re: Robustness to packet reordering Ingemar Johansson S
- RE: [tsvwg] Re: Robustness to packet reordering Koen De Schepper (Nokia)
- Re: [tsvwg] Re: Robustness to packet reordering Neal Cardwell
- Re: [tsvwg] Re: Robustness to packet reordering David Schinazi
- RE: [EXTERNAL] [tsvwg] Re: Robustness to packet r… Overcash, Michael (CCI-Atlanta)
- Re: [tsvwg] Re: Robustness to packet reordering Ryan Hamilton
- Re: [tsvwg] Re: Robustness to packet reordering Joe Touch
- RE: [tsvwg] Re: Robustness to packet reordering Vasilenko Eduard
- Re: [tsvwg] Re: Robustness to packet reordering Greg White
- Re: [tsvwg] Robustness to packet reordering touch@strayalpha.com
- Re: [tsvwg] Robustness to packet reordering Roland Zink
- Re: [tsvwg] Robustness to packet reordering Greg White
- Re: [tsvwg] Robustness to packet reordering touch@strayalpha.com
- Re: [tsvwg] Re: Robustness to packet reordering Sebastian Moeller
- Re: [tsvwg] Robustness to packet reordering touch@strayalpha.com
- RE: [tsvwg] Robustness to packet reordering Ingemar Johansson S
- Re: [tsvwg] Robustness to packet reordering Sebastian Moeller
- Re: [tsvwg] Re: Robustness to packet reordering Michael Eriksson
- Re: [tsvwg] Robustness to packet reordering touch@strayalpha.com
- Re: [tsvwg] Robustness to packet reordering touch@strayalpha.com
- Re: [tsvwg] Re: Robustness to packet reordering Christian Huitema
- Re: [tsvwg] Robustness to packet reordering Sebastian Moeller
- AW: [tsvwg] Re: Robustness to packet reordering Ruediger.Geib
- Re: [tsvwg] Robustness to packet reordering Bill Gage
- Re: [tsvwg] Robustness to packet reordering Greg White
- draft-smith-quic-receive-ts and packet reordering Chris Box
- Re: draft-smith-quic-receive-ts and packet reorde… Ian Swett
- Re: [tsvwg] Robustness to packet reordering Sebastian Moeller