IETF Logo Mail Archive

Re: Handling Packet Misordering?

"Poh Tze Ven" <tvpoh@essex.ac.uk> Mon, 09 September 2002 16:46 UTC

Message-ID: <003801c25820$7b824d50$b629f59b@essex.ac.uk>
From: "Poh Tze Ven" <tvpoh@essex.ac.uk>
To: "Fred Baker" <fred@cisco.com>
Cc: <tcp-impl@grc.nasa.gov>
References: <5.1.1.6.2.20020906181142.02c09348@mira-sjcm-4.cisco.com>
Subject: Re: Handling Packet Misordering?
Date: Mon, 9 Sep 2002 17:46:44 +0100
Organization: University of Essex
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner: Found to be clean
Sender: owner-tcp-impl@grc.nasa.gov
Precedence: bulk
Status: RO
Content-Length: 570
Lines: 15

Hi Fred,

> At 02:39 AM 7/26/2002 +0100, Poh Tze Ven wrote:
> >I believe packet misordering is not
> >a pathological behaviour anymore
>
> packet reordering has never been a pathological behavior. Any time IP

That was what many people believed, I suppose. I think this is the reason why it
was not taken into consideration when designing the fast retransmit mechanism.

> routing comes up with a multipath route, or changes the route that it is
> using for a session, reordering can happen, and TCP should not break.

 TCP does not break, but the performance degrades.

v2.8.7 | Report a Bug | By Email