Re: TTL etc
Vadim Antonov <avg@titan.sprintlink.net> Thu, 13 January 1994 21:29 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13267; 13 Jan 94 16:29 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13263; 13 Jan 94 16:29 EST
Received: from world.std.com by CNRI.Reston.VA.US id aa18134; 13 Jan 94 16:29 EST
Received: by world.std.com (5.65c/Spike-2.0) id AA24111; Thu, 13 Jan 1994 14:52:50 -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: <avg@titan.sprintlink.net>
Received: from titan.sprintlink.net by world.std.com (5.65c/Spike-2.0) id AA24087; Thu, 13 Jan 1994 14:52:48 -0500
Received: from localhost by titan.sprintlink.net (8.6.4/1.34) id OAA20446; Thu, 13 Jan 1994 14:52:46 -0500
Date: Thu, 13 Jan 1994 14:52:46 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Vadim Antonov <avg@titan.sprintlink.net>
Message-Id: <199401131952.OAA20446@titan.sprintlink.net>
To: catnip@world.std.com
Subject: Re: TTL etc
Jim, >Your idea of hop decrements based on some nominal time is a great idea. >It might be good to have an option to not implement the nominal time if >for some reason time was not the issue but just delivery? Transport protocols rely on the knowledge that packets will be destroyed after some pre-defined *physical* time to generate unique ids and detect duplicates. Thus, some time constraints are necessary and implementation should be obligatory. (I would also like to propose including upper bound on link latency in the TTL time decrement -- with satellites you can get 300 ms delay no matter what bandwidth the link is). Two satellite hops will yield 1200 ms of roundtrip time even on absolutely free links. Actually, it may make sense to separate two things: hop count (used in loop prevention) and TTL (which is the upper limit for physical lifetime assumed by transport protocols). On fast hop TTL may be not decremented at all (so it's possible simply to ignore TTL on things like FDDI or Ethernet). Unfortunately it also means that at least 2 bytes are necessary (6 bits for up to 63 hops and 10 bits for 102 secs max lifetime with 100 ms decrements). --vadim
- TTL etc Robert L Ullmann
- Re: TTL etc bound
- Re: TTL etc bound
- Re: TTL etc Vadim Antonov
- Re: TTL etc bound
- Re: TTL etc Robert L Ullmann
- Re: TTL etc Robert L Ullmann
- Re: TTL etc Vadim Antonov