Re: TTL etc

Robert L Ullmann <ariel@world.std.com> Fri, 14 January 1994 01:00 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa15999; 13 Jan 94 20:00 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa15995; 13 Jan 94 20:00 EST
Received: from world.std.com by CNRI.Reston.VA.US id aa22481; 13 Jan 94 20:00 EST
Received: by world.std.com (5.65c/Spike-2.0) id AA03134; Thu, 13 Jan 1994 19:19:41 -0500
Errors-To: catnip-request@world.std.com
X-Orig-Sender: catnip-request@world.std.com
Reply-To: catnip@world.std.com
Precedence: bulk
Return-Path: <ariel>
Received: by world.std.com (5.65c/Spike-2.0) id AA03125; Thu, 13 Jan 1994 19:19:40 -0500
Date: Thu, 13 Jan 1994 19:19:40 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Robert L Ullmann <ariel@world.std.com>
Message-Id: <199401140019.AA03125@world.std.com>
To: catnip@world.std.com
Subject: Re: TTL etc

(private reply) the reason a late datagram causes a problem is
that every 360 degrees in the TCP space, the connection arrives
back at the SAME state (360=0 in phase space, remember? :-)

Rob