Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!rutgers!sri-spam!mordor!lll-tis!ames!sdcsvax!ucbvax!GATEWAY.MITRE.ORG!lazear
From: lazear@GATEWAY.MITRE.ORG
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Automatic IP address assignment
Message-ID: <8706121831.AA05760@saturn.mitre.org>
Date: Fri, 12-Jun-87 14:31:36 EDT
Article-I.D.: saturn.8706121831.AA05760
Posted: Fri Jun 12 14:31:36 1987
Date-Received: Sun, 21-Jun-87 00:40:55 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 19

Geoff,
	I am surprised nobody has mentioned the issue of how does
someone off-net ever address anything to the PC-host?  There has
been no notion of updating a name server to be able to tell remote
systems the PC's address (what if the remote system caches it?).
I think this impacts the duration of the IP/PC binding, since re-
using an IP address means former associations are now void implicitly.

	Maybe I don't understand the environment enough.  I guess the
highly transient association of PC and IP address is OK if the PC
always initiates the communication.  Perhaps this is to download files
for local work, perhaps just to act as a terminal emulator (where the
user logs in at the mainframe across the net).  The issue of positively
identifying that this PC is who it says it is gets lost if IP address
is floating each time the PC is turned on.  Perhaps the mainframe (as
I characterize non-PC hosts) has no need to contact the PC or try to
deliver datagrams to it until the PC comes up and announces itself?

	Walt Lazear