IETF Logo Mail Archive

Re: TCP Checksum Interoperability

Lloyd Wood <l.wood@eim.surrey.ac.uk> Fri, 05 April 2002 23:45 UTC

Date: Sat, 6 Apr 2002 00:45:07 +0100 (BST)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-X-Sender: eep1lw@phaestos.ee.surrey.ac.uk
Reply-To: Lloyd Wood <L.Wood@eim.surrey.ac.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matt Crawford <crawdad@fnal.gov>, <tcp-impl@grc.nasa.gov>
Subject: Re: TCP Checksum Interoperability
In-Reply-To: <E16tdNG-0000uh-00@the-village.bc.nu>
Message-ID: <Pine.SOL.4.43.0204060042310.5820-100000@phaestos.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanner: exiscan *16tdOI-00010p-00*GrNhcwzJmkU* (SECM, UniS)
Sender: owner-tcp-impl@grc.nasa.gov
Precedence: bulk
Status: RO
Content-Length: 839
Lines: 22

On Sat, 6 Apr 2002, Alan Cox wrote:

> > hop limit and have no connection to time.  A TCP riding on IPv6 may
> > receive old segments an unbounded time later without any other
> > network element breaking a spec.
>
> This was true with IPv4. A satellite link or a store and forward physical
> layer can have multi-second timings anyway. Take RFC1149 for an obvious extreme
> example. In the experimental study the packet dispatch time was a relatively low
> proportion and the flight time is not visible to the router nor was the
> large amount of flapping.
>
> But we know TCP is broken. The late Ian Heavans wrote a nice draft on the
> subject.

you mean RFC2525? Not all his work got lost...

http://watersprings.org/cgi-bin/namazu.cgi?query=heavens&idxname=id

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>

v2.8.7 | Report a Bug | By Email