Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!cuae2!ihnp4!ptsfa!lll-lcc!ames!ucbcad!ucbvax!BRL.ARPA!mike From: mike@BRL.ARPA.UUCP Newsgroups: mod.protocols.tcp-ip Subject: IP Record Route in core? Message-ID: <8702120751.aa29368@VGR.BRL.ARPA> Date: Thu, 12-Feb-87 07:51:40 EST Article-I.D.: VGR.8702120751.aa29368 Posted: Thu Feb 12 07:51:40 1987 Date-Received: Sat, 14-Feb-87 13:52:00 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 31 Approved: tcp-ip@sri-nic.arpa Phil Dykstra at BRL has just instrumented a version of my PING program for BSD UNIX to optionally issue the ICMP ECHO REQUEST packets with IP Record Route enabled. This has brought up several important issues: *) The core gateways do not record any route information, although they don't choke on the IP option. Is there any chance that they can be induced to store their address in the record route record, or is this another "wait for the Butterfly gateway" issue? In the BRL gateway, the IP Record Route code is about 20 lines of C... *) There is some ambiguity as to how to interpret the combination of ICMP ECHO REQUEST and IP Record Route together. The Mills Fuzzball software seems to regard the ICMP ECHO REPLY as a separate transaction, and resets the Record Route pointer to the beginning of the log area, while the BRL Gateway presently continues recording, so you see the full route, round trip. There is merit to both, is one considered "right"? *) 4.2 BSD UNIX, alas, can't handle the Record Route at all. *) 4.3 BSD UNIX answers, but strips off the Record Route when answering. (Actually, it strips all options except source routing). This is sub- optimal, and we will be working on a fix. *) Checksum fixes to the BRL Gateway IP Options code were needed too. If you want the code, (a) please wait a few weeks before asking, and (b) don't ask me, ask . Best, -Mike