[Tsvwg] overlapping TCP segments during reassembly
Murali Bashyam <mbashyam@cisco.com> Tue, 26 August 2003 19:40 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00297 for <tsvwg-archive@odin.ietf.org>; Tue, 26 Aug 2003 15:40:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rjfq-0002IC-CK for tsvwg-archive@odin.ietf.org; Tue, 26 Aug 2003 15:40:14 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7QJeCKL008764 for tsvwg-archive@odin.ietf.org; Tue, 26 Aug 2003 15:40:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rjfS-0002DQ-Jg; Tue, 26 Aug 2003 15:39:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rT5I-0008HY-HM for tsvwg@optimus.ietf.org; Mon, 25 Aug 2003 21:57:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27301 for <tsvwg@ietf.org>; Mon, 25 Aug 2003 21:57:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rT5F-0002HS-00 for tsvwg@ietf.org; Mon, 25 Aug 2003 21:57:21 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19rT5E-0002HE-00 for tsvwg@ietf.org; Mon, 25 Aug 2003 21:57:21 -0400
Received: from cisco.com (171.68.223.137) by sj-iport-2.cisco.com with ESMTP; 25 Aug 2003 19:06:29 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h7Q1un7b011433; Mon, 25 Aug 2003 18:56:49 -0700 (PDT)
Received: from cisco.com (mbashyam-u10.cisco.com [10.34.36.39]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AKT91916; Mon, 25 Aug 2003 18:48:00 -0700 (PDT)
Message-ID: <3F4ABE60.B4D3572E@cisco.com>
Date: Mon, 25 Aug 2003 18:56:48 -0700
From: Murali Bashyam <mbashyam@cisco.com>
Organization: Cisco Systems Inc
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] overlapping TCP segments during reassembly
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Hi Is there any guidelines outlined by any TCP RFC's for determining what data in the sequence space to keep and what to drop during TCP out of order packet reassembly when there are overlaps? The BSD code tries to trim the incoming segment when there is an overlap with a previous segment in sequence space, and trims the already queued segments when there is an overlap with succeeding segments in sequence space. I was curious abt the motivation behind this strategy. Murali _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg
- [Tsvwg] overlapping TCP segments during reassembly Murali Bashyam
- Re: [Tsvwg] overlapping TCP segments during reass… Caitlin Bestler
- Re: [Tsvwg] overlapping TCP segments during reass… David Borman
- Re: [Tsvwg] overlapping TCP segments during reass… Murali Bashyam