Re: [tsvwg] Robustness to packet reordering

Bill Gage <billgage.ietf@gmail.com> Fri, 14 February 2025 02:03 UTC

Return-Path: <billgage.ietf@gmail.com>
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 6B2AFC1E6419 for <quic@ietfa.amsl.com>; Thu, 13 Feb 2025 18:03:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 U94X4_Grz_rP for <quic@ietfa.amsl.com>; Thu, 13 Feb 2025 18:03:52 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7FFBC1E6439 for <quic@ietf.org>; Thu, 13 Feb 2025 18:03:52 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-7c05dc87ad9so185751485a.3 for <quic@ietf.org>; Thu, 13 Feb 2025 18:03:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739498632; x=1740103432; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=Jmn9+QMs+/BCLAiWjZuMiEcW51HSt3IaVf3mmAeK3lU=; b=LyawGFtiHJwVlK+u36QIlCHOdeTRJxvzgvB6nHTYUOv15Pzoh9H6GrsiaLjykA334Y k1SiN7FjCL27wT446x6ioH/UndH3MU/uU4qZ20MMGCaj6wgc88OlPdWpXIk2/iI9t6gv BcWqcrIAouKzzv/TfQ1Q8ACalA05cVU8kUzReFvMN5sypUkuJfYkYXrrfyEjizBevF6D GtPBII8qg+Rrdaex17MziQE2zFyspVseOLgh87eD4rTf4AlKbjIhlQ9JAkNGxlB4qZvW rq7VkxI2Jlkf9IMengGeDRQt7y76XXdozU9apnp05Ctz9rle9NzgPe3BwoVB9z6lLpUh 8ofQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739498632; x=1740103432; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Jmn9+QMs+/BCLAiWjZuMiEcW51HSt3IaVf3mmAeK3lU=; b=pDDyE+KeEaqT17M5Nj4K9lCe2Rfe0RRbbrTrF9gaan8fcJRlZFHs4sWkJ8ci4l9ncu rbaFx60pGPCu7Vaf9Yxl0iZMm670LbSmqu3CS++5+iY2b/9e0oAGRbd/lJW6GnMppg4E 5aTkU6/ZqlqjT+0MBLMYqLBftAEHYi8VoYB+f9DVY+9n9T8cymz7PR8TNMFmnbKieVnA y+jT5i54G/1nHPzl8JsJ0B+OfPDW/lVYWhau4Y0B0UK2Pn9pT6wYyXeVGj7vkrBiUq2M G+cD820ne7PetiJM2k9YUMaXoRqleYLnAmn27iCaLS2Kj+MmXCQBMMXvmJ0vQ4RvrqBV qt7A==
X-Gm-Message-State: AOJu0Yznvh4LPTi1l7Sn0y1N51MxEmyvbdbYt6B3Dm29RDk+RpT9xcbM uzzjDgRh3ZocyLafuIrt2o77XeqKP/bwKsFMbYARpvLq1lCrRdEyOBdJUA==
X-Gm-Gg: ASbGnctl4V90n9KUC2Qs3TfKCiDfTHWfcnlvJrE7E+IS4cr6q6XbC9IkF1XLeQ/ljyj v7MKAoSCxqxDU7FPF8pEQUpvHzIz06A3xckF0n1Kix2NRliJ4KMLOBoWz+V6ecorcARIESpYOhh AQT/bdQMm3v5o7EGEvYK4GXPUyH2xStFkRufXUtq/SqZo8GzdPYl2Ik/4FFd8Zs+iQtKh/9Jtsb iys5k5DLzLUcmJWXgzZlcyGbK0n3j+1nqKJZKC2Yz2HTrtYywsr0clWcnWiKSOxDvnmdWR3N2S5 bD2OyijQdTI/fziUlxywv9T07qhRp1sA
X-Google-Smtp-Source: AGHT+IHnL67dmQB0atMPhLiKofDwkcE5HRBTH8vJzqI/FgCwg6RdY6CRY2XDlmMkQEvbq/uFqOzGDw==
X-Received: by 2002:a05:620a:8004:b0:7be:7f76:18cd with SMTP id af79cd13be357-7c06fce2433mr1743422285a.49.1739498631745; Thu, 13 Feb 2025 18:03:51 -0800 (PST)
Received: from [192.168.2.57] ([50.101.71.62]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7c07c60890fsm156314285a.30.2025.02.13.18.03.50 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Feb 2025 18:03:50 -0800 (PST)
Message-ID: <f7555dad-d016-480d-a47b-5625a6b06c26@gmail.com>
Date: Thu, 13 Feb 2025 21:03:42 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [tsvwg] Robustness to packet reordering
To: quic@ietf.org
References: <CAJ_4DfQjNRd2k+JBFoR+=Y9D-Nvh4-Kw29nQP=tEYS4BY0B-BQ@mail.gmail.com> <FB1FD652-08EB-41BE-ADC0-C4704349DD5E@strayalpha.com> <43E6C2EC-F99E-4744-98E4-9A9239EAF86F@CableLabs.com> <1116DED7-2068-4566-A947-AC5B57A68FAB@strayalpha.com> <8ACD1AFA-CE02-4886-AC4D-5EA7AA0134E9@CableLabs.com> <AM8PR07MB8137A7C5A9DD4D1F3A38E622C2FC2@AM8PR07MB8137.eurprd07.prod.outlook.com>
Content-Language: en-GB
From: Bill Gage <billgage.ietf@gmail.com>
In-Reply-To: <AM8PR07MB8137A7C5A9DD4D1F3A38E622C2FC2@AM8PR07MB8137.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: 4KZC64HEIH4SVAZVOPKZVRIHUIKJVMZG
X-Message-ID-Hash: 4KZC64HEIH4SVAZVOPKZVRIHUIKJVMZG
X-MailFrom: billgage.ietf@gmail.com
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
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/IaseDIlnRkMR__NEG-VTkgZwb4Q>
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>

I think there is a bit of confusion about reordering by the 5G radio 
link protocol (RLP). The RLP encapsulates an IP packet inside an RLP 
protocol data unit (PDU) for transmission over the radio link between a 
wireless device (UE) and a base station. The RLP encompasses a number of 
functions including PDU segmentation and reassembly, PDU segment loss 
recovery (ARQ), RLP encryption and authentication, IP header compression 
(RoHC), and user data compression. Each PDU includes an RLP sequence 
number so that reassembled PDUs can be reordered for functions (like 
decompression) that require PDUs to be processed in a certain order. 
This reordering is transparent to the IP endpoints.

Once an IP packet has been successfully reconstructed by RLP, it becomes 
a candidate for forwarding to the destination IP endpoint. The RLP can 
be configured either to forward an IP packet as soon as it becomes 
available or to forward the IP packet in-order (according to the RLP 
sequence number). If in-order delivery is enabled, the RLP will buffer 
an out-of-order IP packet until either the missing packets become 
available or a re-ordering timer expires. Packet reordering is typically 
enabled for TCP sessions and disabled for UDP streams.

So, I think 5G RLP already has the necessary hooks to deal with 
reordering caused by radio link impairments and to cater to end-to-end 
needs of the application.

/bill

On 2025-02-12 3:30 a.m., Ingemar Johansson S wrote:

> I think a draft would be good. I can definitely help and add the 5G 
> specifics.
> There is a cost aspect with large reordering buffers in UEs (terminals) 
> and  network nodes for 5G as well and given that link throughput 
> increases so will also memory. But I think the main driver behind my 
> interest is to limit head of line blocking.
> Historically, reordering buffers in 5G (and before) has been to improve 
> TCP performance. Now that TCP and other protocols have potential to be 
> more robust against packet reordering then I think that it is time to 
> reconsider how things are done.
> 
> And with address to Sebasians and Joes discussion, yes, these are 
> relevant arguments and there is probably no “one shoe fits all”. I am 
> for instance not that keen to allow packets to go completely out of 
> sequence from 5G access as retransmissions on the MAC layer are quite 
> common, but that is perhaps more of concern for a number of transport 
> protocol stacks that do not work well when subject out of sequence 
> delivery.
> 
> There is concern about performance for RoHC, RoHC is to day mainly used 
> for VoLTE and VoNR which has its own data radio bearer. I see little 
> utility with RoHC otherwise.
>