[tcpm] Re: comments on draft-mazilu-tcpm-packet-trimming-00
"Flavius-Romeo MAZILU (123666)" <flavius.mazilu@stud.acs.upb.ro> Tue, 28 July 2026 10:08 UTC
Return-Path: <flavius.mazilu@stud.acs.upb.ro>
X-Original-To: tcpm@mail2.ietf.org
Delivered-To: tcpm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F245E11FB8582 for <tcpm@mail2.ietf.org>; Tue, 28 Jul 2026 03:08:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785233316; bh=nG9QJuW4gK1ODvdBPrnMr0iMANEA5bDMV/lfai5io3k=; h=From:To:Subject:Date:References:In-Reply-To; b=WqJPQ0mvis/EWj4IGUODaHUERC7edcgeSq9Mu4r4dOWRNqfJQR2uMhdvf+U++2bX7 pTNRB83SBqFlrJgz2DhvMvcPrx7mVGSvsaRCvILwpsBci0aqttarBbpI7gMmQ9g9x7 zhdx8qq2SRBZ6/rPpbqtmc5PrFaLHI0vyEQ6kUSc=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNqCJQBlc6-n for <tcpm@mail2.ietf.org>; Tue, 28 Jul 2026 03:08:36 -0700 (PDT)
Received: from DUZPR83CU001.outbound.protection.outlook.com (mail-northeuropeazon11022086.outbound.protection.outlook.com [52.101.66.86]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0B78711FB8577 for <tcpm@ietf.org>; Tue, 28 Jul 2026 03:08:36 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=l1OJVeYr7mTaM4n+w1mECFlBrJ/Q4+yz1k83/V4/xo+FBMttfHQwdmCzbdsUSEZBn4YPYIKr1Iu1uf3QrSlzhYLzFTTXix3xu3QYw5Zy/APN7hyQN6uiOHizPvrzgUqF5ai5/i/iuKUYXQdNU+iFwwXYtx6Qtv0mFOxiy+HXtbd1cPu/xFkpvKUxE+h/V4+dOiAlR5TD0rqwQD2kcPAz3LcfE6PswCqBOKUMkhT1yTYOsh9rqLSKXu4DoeGLMtPDoE8ZYs9xoSW2ijQtWGf/QFmNAyFxsS203RNcx6TazlLpBV85cIoVOXAszHpEej8xYVrdSzpNPjVD0g/fssp5Cg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=nG9QJuW4gK1ODvdBPrnMr0iMANEA5bDMV/lfai5io3k=; b=ThFIQsF+ioC45mHBdCWQRJcAsMUjznwhpNuX8q8u36G46undsJ2uRazhfRDkvQ1vjvAeNEZ+lv05AE2ARGerFmty+0R6QKNHd2w1coW/aZ0JD5vdpfpB3oW8l85Vnn4N3TZQXmLnNctACTfLImV6FnrohDqtZvegqb5z5ZX2XGa/QCFvAzB1PxUQrh3VLsU5JiREnb8yGlnUboFVc5N+cPWh+Q+eej6IjvYizPCYtf/C4hKBZ7vWGGqKtxMOPKpRKBhWOvmqogy1evg9ASyUV/R/ukaeKrEHhnKoI+4hdsa7twlIXdDwVOxo+Oz44L3EHNKWFkc5fL8Hcf5VuAx+jA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=stud.acs.upb.ro; dmarc=pass action=none header.from=stud.acs.upb.ro; dkim=pass header.d=stud.acs.upb.ro; arc=none
Received: from AS8PR01MB7191.eurprd01.prod.exchangelabs.com (2603:10a6:20b:23a::21) by AS4PR01MB9584.eurprd01.prod.exchangelabs.com (2603:10a6:20b:4c9::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.270.12; Tue, 28 Jul 2026 10:08:27 +0000
Received: from AS8PR01MB7191.eurprd01.prod.exchangelabs.com ([fe80::ffe5:adde:efaf:f1b8]) by AS8PR01MB7191.eurprd01.prod.exchangelabs.com ([fe80::ffe5:adde:efaf:f1b8%6]) with mapi id 15.21.0245.012; Tue, 28 Jul 2026 10:08:27 +0000
From: "Flavius-Romeo MAZILU (123666)" <flavius.mazilu@stud.acs.upb.ro>
To: Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org>, "tcpm@ietf.org" <tcpm@ietf.org>, Michael Tuexen <tuexen@fh-muenster.de>
Thread-Topic: [tcpm] Re: comments on draft-mazilu-tcpm-packet-trimming-00
Thread-Index: AQHdG31bliBoG73bB0GjcLWkA9t1GraBaLJNgAADaYCAAT+lCA==
Date: Tue, 28 Jul 2026 10:08:26 +0000
Message-ID: <AS8PR01MB719181CB03B6385150F94F1093CB2@AS8PR01MB7191.eurprd01.prod.exchangelabs.com>
References: <CAAK044Q1VkybiX0SPoEAsyEpzww5+=9MeeT0VdQJ5wiDFroTJg@mail.gmail.com> <4014af7c-c85c-4bee-ac93-8c8f6ad7dcfd@erg.abdn.ac.uk> <AS8PR01MB7191E51E0FB6EE3B7B05EED293CC2@AS8PR01MB7191.eurprd01.prod.exchangelabs.com> <4acf7553-6ca9-4830-a42f-ed4bf40e2678@gmx.at>
In-Reply-To: <4acf7553-6ca9-4830-a42f-ed4bf40e2678@gmx.at>
Accept-Language: ro-RO, en-US
Content-Language: ro-RO
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=stud.acs.upb.ro;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: AS8PR01MB7191:EE_|AS4PR01MB9584:EE_
x-ms-office365-filtering-correlation-id: 6ab6caba-5f21-42d0-88d0-08deec902ac1
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|786006|376014|4022899009|366016|1800799024|23010399003|13003099007|6133799003|18002099003|22082099003|38070700021|8096899003|11063799006|56012099006|4143699003|10067099003;
x-microsoft-antispam-message-info: o3r+tcY89SZFVIKyKRV/+8pK7ybFpkgITSRj2BaDqjziJ7Lv13JazvhH2lOOtpBB1Mpi2uiHdTF/NMs4FHq2n+UkV4TlkXYGUksnJevkRJAuSU6kcg2CUHXKOLsNChZc2XtqPRV+rdeuThySNURJ0C2mtnPuZN/IYMl2vC6QA7gTJv2iCDg6sB0Iow7wjaRSEuYFf6VVbk/eToMO3cOH2PNf/CJQD2qag0azxGmxf9hKivdq7fi4UueNdG+Gv+YpKZXa/JX7/PVxfMn3ZLeQQ4CDZysSRic9r4mJ0c/dahlorwGzmc4OSFxDL4SU5aKL2zVOTnDoEGZ73DpnbjpGHtfDkDMCSbd5ZW6QHDHOiswlQxa1nJuqRNvE31UagUMN7KirBFBuulY+I3bCeWM/vMOmChAhdujMpX7RWr3Beo9lmppGFCKW5ppdKvIRWXOivxeAf9D49kJJYjgfvv8vRoosf0ZgUTPhrJF5y1SWSH71kVoVmqRiO6ADPXXj0qpCEkWBqyEvyC9XfnRs4ElGp3O4EbxMPsToSZMRnOyp1Xws2eoE71OeVjbFnfetmwhJHBl9fmdZyfFN4mTUxhoHqFi/aEsCHh+g8ATtZVxVjG6b2SKL2OwEE+kQhxaI/HL9t0Cl4Jx2fMpyOaZzVhY6wjEr5gTZSwWHWhmMuda4bXc=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:AS8PR01MB7191.eurprd01.prod.exchangelabs.com;PTR:;CAT:NONE;SFS:(13230040)(786006)(376014)(4022899009)(366016)(1800799024)(23010399003)(13003099007)(6133799003)(18002099003)(22082099003)(38070700021)(8096899003)(11063799006)(56012099006)(4143699003)(10067099003);DIR:OUT;SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: ph7Hre2dMqE0GMwCBTpzix2CPBsjzvQv8YWqLUgtTd0GGuNLkOzcTodPDsx6c//agIDDhTUDJYIFZdV/lctg/mbkh60IwiNOH7jj5hj+59/mdMu1KjFunKY5T1hFm/kDaGeZkWmCJoQmZZtsIqpkbNh30jxkUDd4sse/V1mjYZwRypT+y4AmW4eQOYVTNLjTw73fhyvu+IcOvU1Dgo3Gt7wMge9NDSNTHphMrvL5iPFKTAXxSRjGIAZpQQwQceE+fXmbfzt38IEDdHDG9N66HCyGdW3kZjku0GVmYLfn9pfTJBVXMLFJflSiszkED+5LlTqyi6P4yF611KouC4eiC5D7vI7fhEaOXaJGOykOfibrrdbVw887pADXU2i9qjiooSHBr6lplWczbnFeZHq872K7AiBjGP21pn7uepX8j+s7qQXuCFGas77k07NqwyrGtCeMUhi8Ymqs7LiSJUawetkKbU2vSQHomdo1a1nVlWYqS19qL1IGmuz75WjOjcz0+3pl35NsIhHOVqLhTQirKVKWvBw/R06JGUn9AA6Tb9SeIv6Z4YDZQxc1AD93ygxZD7VXiixicfcKKi3JwxFNicBYVQeYxMcZvh8M6+U67j0Y9M6+lpMo6OlDjcM+46NToTKizljf8pZ45tsnh6+cKW27nPA63sDfmHwGqRMAHHALCIF0nd02CARFeTztuszC/kK+aBk8F9gR3TERIpYKhEWEPA3RpKuAdyPY0iXSdvoIFRKkfC5aYDCZD3cQGq3tzTcw7LRnjozMZfMMahWqCOFX003CvrcnU5nXN773gflEPYx5Db6XAYiZ0LwHWnlmELHhUZwIQ3NZI3Xalz5PYzQ0sPVzdnu/QO0ytGAMZVZI7VH0Fc6Ckvl63ZpmZQblLSGPnauMO1IY0jNarQrbJZI5KZ3ENk2ZIpPr/qB8H8ZyM/J7k1vL3RJOx8numvLfwr//t48wwKZkoVBF3EJiXtKNez/WIEYX9I7apgwCKYjSeH4nD7irrEjpkk85fXOYX6bNcUndxqLmsllY6VXVb9g3RNaEZNU5fHFaeObtalCkx1Q4EA7ILuGinjIhT+4txg+3lTzWGyE9mO5cdqKvPtWrd7Wkf6QJoNMEnfZm/xbRPMigo7KzzOWQ3vujevIHFMcGBJfnbfHiI3HuJYxbypPbOyYnQCH8GBwc+DLIz+S5OZUTYfaMq5kjabKpYVftKASrhp758FIDLlxHLxLIHLMQdnQtJFxjW6og1R8ZZ16YPMZNc67dIGslLVgnBsvJQPQD+VPSHuhMlzO4+0oL/Bs+an4wQXs0k3k1evrsUWSaoU5uDLLab1I1P8YKhrB8yvbo9+LXBwp6z5c+J53wT6YgWtX/R7DrnUaHi7SCNrmyASXrzINUxZIrH+sxcNgD+WpfRKos6PKIg0CsFyNZUKQ0Utc9a07aNnQX68lRIjXgQ9oNZ03h3ZTB04IVdEUteDzSQMSUpffF2pt6y1VUdyGKHPCghu38k3wKGNnVM8DqVyrDywLJg6aoPMBrkxnvPQMKv7tksHZhCWilpQoo071Rv/OojzPQpCs2u7FZylqgd1ojfNDFqTzqLOj2lG2PDNpXkQyGGCi0004fngdR9OYnSdPHvgWaAspZuQaNssh401OnzH2s4KvIYuSQG/l7kzwIky5tPBYhjCGXD1UuqnTbtCQpRXG7IXpxSMuuAyBaYthHX8fxEjSjd8HEPf+BG4G4i3675M0Dlr9VYL/pWQ==
Content-Type: multipart/alternative; boundary="_000_AS8PR01MB719181CB03B6385150F94F1093CB2AS8PR01MB7191eurp_"
MIME-Version: 1.0
X-OriginatorOrg: stud.acs.upb.ro
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AS8PR01MB7191.eurprd01.prod.exchangelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6ab6caba-5f21-42d0-88d0-08deec902ac1
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jul 2026 10:08:26.9934 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2d8cc8ba-8dda-4334-9e5c-fac2092e9bac
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: wW67Zt3Y+n811h6+EUnUeQm44Ar/7WzSF/KzRNR1QOlq66fXgDMth9zVRmnQIDQbx/3fRyOwlH9bSRNbmqmah5ULVIDzUC5cfzVe/1hpRlU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS4PR01MB9584
Message-ID-Hash: Y66R3EZKX5WRY3WTNAPJKRLYIO63PP3W
X-Message-ID-Hash: Y66R3EZKX5WRY3WTNAPJKRLYIO63PP3W
X-MailFrom: flavius.mazilu@stud.acs.upb.ro
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tcpm.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
Subject: [tcpm] Re: comments on draft-mazilu-tcpm-packet-trimming-00
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/3vZo4QxWkUlJWglFHPuh3dIjE08>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Owner: <mailto:tcpm-owner@ietf.org>
List-Post: <mailto:tcpm@ietf.org>
List-Subscribe: <mailto:tcpm-join@ietf.org>
List-Unsubscribe: <mailto:tcpm-leave@ietf.org>
Richard Scheffenegger 27 Iul 2026 17:10 And for the dedicated marking in the header - I still think that the same DSCP + CE marking would address that need. CE-marked packets "should" be treaded preferrably (and are, DualQ / L4S) since they contained updated information about the network state, to which the original sender (after the RTT delayed feedback loop) should react as quickly as possible. As we briefly discussed, this is an interesting idea worth exploring. The main drawback is that ECN could no longer be used in the conventional way on connections with packet trimming enabled. Nevertheless, it is worth investigating whether ECN is still necessary for such connections. Richard Scheffenegger 27 Iul 2026 17:10 Well, the IP header already contains the "total length" field; a receiver can easily distinguish trimmed from non-trimmed packets by comparing the (eth) packet size recieved, vs. the (ip) packet size expected... As Michael noted, the I-D assumes that switches recompute the IP length and checksum fields. This assumption is based on the UEC specification [1], which ASIC manufacturers such as Broadcom are supposed to follow: “The IP length field is modified and the IP header checksum (for IPv4) is updated so that the trimmed packet is a valid IP datagram.” However, I could not find any documentation from specific ASIC manufacturers confirming whether these fields are updated. Using this behavior to determine whether a packet has been trimmed sounds like a good approach. The main potential issue I will look into is, as Michael mentioned, how switches might handle packets that are shorter than the length indicated in the IP header. Thanks, Flavius [1] https://ultraethernet.org/wp-content/uploads/sites/20/2026/07/UE-Specification-1.0.3.pdf ________________________________ De la: Richard Scheffenegger <rs.ietf=40gmx.at@dmarc.ietf.org> Trimis: luni, 27 iulie 2026 17:09 Către: tcpm@ietf.org <tcpm@ietf.org> Subiect: [tcpm] Re: comments on draft-mazilu-tcpm-packet-trimming-00 Well, the IP header already contains the "total length" field; a receiver can easily distinguish trimmed from non-trimmed packets by comparing the (eth) packet size recieved, vs. the (ip) packet size expected... And for the dedicated marking in the header - I still think that the same DSCP + CE marking would address that need. CE-marked packets "should" be treaded preferrably (and are, DualQ / L4S) since they contained updated information about the network state, to which the original sender (after the RTT delayed feedback loop) should react as quickly as possible. Am 27.07.2026 um 16:01 schrieb Flavius-Romeo MAZILU (123666): It is possible to trim a packet without changing its DSCP. However, the receiver still needs an explicit indication that trimming occurred so that it can recognize the packet as a loss notification and generate a NACK. Using DSCP for this purpose was not introduced by our proposal; it reflects functionality already exposed by switch vendors [1][2][3]. Placing the trimming indication in the IP header is advantageous because, like ECN, it is transport-independent and straightforward for switches to modify. No dedicated DSCP allocation is required: operators configure the values within their administrative domain, and TCP endpoints can be configured with the corresponding values. “The network would still forward a trimmed packet in the same way as a packet carrying any other DSCP value.” That is correct, but without a distinct marking the network switch could not classify the trimmed packet into a separate traffic class and transmit it through a higher-priority queue.The method proposed allows the receiver to minimaly process a packet with wrong tcp checksum only if it sees the packet being marked as trimmed(via DSCP), and only for the purpose of issuing a NACK. Any other action of handling a received TCP segment, like ack seq, payload or options will not be processed. A packet with an invalid TCP checksum that does not carry the 'trimmed' marking is discarded without further action, as usual. [1] SONiC https://github.com/sonic-net/SONiC/blob/master/doc/packet_trimming/packet-trimming-design.md [2] Juniper https://www.juniper.net/documentation/us/en/software/junos/traffic-mgmt-qfx/topics/topic-map/drop-congestion-notification.html [3] Nvidia https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-515/Layer-1-and-Switch-Ports/Quality-of-Service/Packet-Trimming/ Thanks, Flavius ________________________________ De la: Gorry Fairhurst <gorry@erg.abdn.ac.uk><mailto:gorry@erg.abdn.ac.uk> Trimis: vineri, 24 iulie 2026 18:01 Către: Yoshifumi Nishida <nsd.ietf@gmail.com><mailto:nsd.ietf@gmail.com>; tcpm@ietf.org<mailto:tcpm@ietf.org> Extensions <tcpm@ietf.org><mailto:tcpm@ietf.org> Subiect: [tcpm] Re: comments on draft-mazilu-tcpm-packet-trimming-00 On 24/07/2026 08:44, Yoshifumi Nishida wrote: > Hello folks, > Thanks for bringing up an interesting idea. I've missed a chance to > ask a couple of questions during the meeting, so I put them here. > > 1. Why can the trimming nack option carry only one sequence number? > I'm guessing situations like TCP incast can cause multiple trimmed > packets. Is the current format sufficient enough for this kind of > situations? > 2. I am curious how much this approach can be effective. Do we have > some data points? I am guessing major TCP traffic in DC is bulk > transfer where fast retransmit, sack based loss detection or RACK/TLP > can generally work well. It would be great if we can see some expected > performance improvements with this approach. > > Thanks, > -- > Yoshi > > _______________________________________________ > tcpm mailing list -- tcpm@ietf.org<mailto:tcpm@ietf.org> > To unsubscribe send an email to tcpm-leave@ietf.org<mailto:tcpm-leave@ietf.org> I was in the meeting yesterday and was intrigued by this presented idea. First, I suspect that overwriting the DSCP has many implications that should be considered if done within the IETF, but before considering that: is it not possible to trim the packet without CHANGING the DSCP (that would in reality require allocation of multiple DSCP values)? - the network would still forward a trimmed packet (in the same way as a packet with any DSCP value), and the method in the proposal allows a receiver to decide to further process the packet (with the caveat that the cksum provides no protection of the headers) and TCP *could* then perhaps still read this 'trimmed' packet? - so do we need the remarking to a different DSCP? Second (as above), if such a method was to continue development in the IETF, I agree we'd need to look carefully at the benefit this is expected to provide above RACK/TLP etc (as asked by Yoshi). Gorry Gorry _______________________________________________ tcpm mailing list -- tcpm@ietf.org<mailto:tcpm@ietf.org> To unsubscribe send an email to tcpm-leave@ietf.org<mailto:tcpm-leave@ietf.org> _______________________________________________ tcpm mailing list -- tcpm@ietf.org<mailto:tcpm@ietf.org> To unsubscribe send an email to tcpm-leave@ietf.org<mailto:tcpm-leave@ietf.org>
- [tcpm] comments on draft-mazilu-tcpm-packet-trimm… Yoshifumi Nishida
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Gorry Fairhurst
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Joe Touch
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Richard Scheffenegger
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Flavius-Romeo MAZILU (123666)
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Joseph Touch
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Flavius-Romeo MAZILU (123666)
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Gorry Fairhurst
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Flavius-Romeo MAZILU (123666)
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Richard Scheffenegger
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Michael Tuexen
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Flavius-Romeo MAZILU (123666)
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Richard Scheffenegger
- [tcpm] Re: comments on draft-mazilu-tcpm-packet-t… Flavius-Romeo MAZILU (123666)