Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!tcp-ip
From: tcp-ip@ucbvax.ARPA
Newsgroups: fa.tcp-ip
Subject: Re: tftp for bootstrap
Message-ID: <9014@ucbvax.ARPA>
Date: Fri, 12-Jul-85 16:32:20 EDT
Article-I.D.: ucbvax.9014
Posted: Fri Jul 12 16:32:20 1985
Date-Received: Sat, 13-Jul-85 12:47:42 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 11

From: Bill Croft 

Dave,

That is a good point, if the server sending the 'bootreply' packet
has the kernel hooks to allow him to fill in an ARP table entry
'by hand', then the server CAN send the packet to the client's
new IP address.  I will mention this point in the RFC I am preparing.
However if such kernel hooks are missing from a particular operating
system, broadcasting the bootreply (as I mentioned earlier) is the
only way to get the packet out the door.