Subject: Re: kernel ip_randomid() and libc randomid(3) still "broken"
To: None <tech-net@NetBSD.org>
From: E.B. Dreger <eddy+public+spam@noc.everquick.net>
List: tech-net
Date: 11/27/2003 21:35:56
JiH> Date: Thu, 27 Nov 2003 06:09:55 +0900 (JST)
JiH> From: Jun-ichiro itojun Hagino
[ CC list trimmed ]
[ somewhat snipped, but lines not rewrapped ]
JiH> where in RFC791 can i find statement that TTL field has to be used for
JiH> reassembly buffer management? i don't see any, therefore i understand
"Some higher level reliable connection protocols are based on
assumptions that old duplicate datagrams will not arrive after a
certain time elapses. The TTL is a way for such protocols to
have an assurance that their assumption is met."
JiH> TTL field as the lifetime during transit (defined as "seconds" in the
JiH> past, used as "hop count" in reality). "internet system" in the
JiH> following statement does not include the reass buffer in the
JiH> destination node, i assume.
As others have stated, TTL _still_ means time to live. Each hop
rounds TTL up to the next second; what you observe is a special
case for when all hops are < 1 sec, _not_ the strict definition.
Please show RFCs updating or obsoleting 791.
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 785 865 5885 Lawrence and [inter]national
Phone: +1 316 794 8922 Wichita
_________________________________________________________________
DO NOT send mail to the following addresses :
blacklist@brics.com -or- alfra@intc.net -or- curbjmp@intc.net
Sending mail to spambait addresses is a great way to get blocked.