Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!ucbvax!GATEWAY.MITRE.ORG!gross
From: gross@GATEWAY.MITRE.ORG (Phill Gross)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  ICMP echo
Message-ID: <8704281427.AA09957@gateway.mitre.org>
Date: Tue, 28-Apr-87 10:27:55 EDT
Article-I.D.: gateway.8704281427.AA09957
Posted: Tue Apr 28 10:27:55 1987
Date-Received: Thu, 30-Apr-87 03:20:43 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 13


> A final tid: Should the TTL be reset at the echo server? If not, the
> sender would have a non-ambiguous way to measure the number of hops.
> He could, of course, also use record-route.

Have we really given up on the original meaning of TTL?  The Braden/Postel
RFC985-update still talks about TTL in seconds, possibly decremented by
more than one second at any gateway hop.  If vendors take this as seriously
as they are supposed to, then TTL will no longer be an unambiguous hop count.
In either case, I would argue on principle that the TTL should be reset in 
the echo reply.

Phill