Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!SACMGR.UUCP!HENRYM
From: HENRYM@SACMGR.UUCP
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: RE: Rarp, anyone?
Message-ID: <9002210220.AA01272@sanj>
Date: 20 Feb 90 23:21:37 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29


	I'd like to thank those who responded to me concerning the use of
RARP for our local PC network.  However, I don't think I made my intention
really clear.

	The use of a hardwired number or even a generated number in CONFIG.TEL
or any other file that the user can modify or even know about is unacceptable.
We must have a method, i.e., RARP of associating the IP number with the
ENET address of the PC in question, otherwise our internal security and
auditing procedures fall apart.  That is why we need RARP, or something
similar.

-HWM

----------
Henry W. Miller
Assistant Systems Manager, Mid Pacific Region
U.S. Bureau of Reclamation
2800 Cottage Way MP1100
Sacramento, CA 95825
(916) 978-5108 / FTS 460-5108
Inet:	"sanj!sacwms!henrym@caldwr.water.ca.gov"	(Vaxcluster)
	"sanj!sacusr!henrym@caldwr.water.ca.gov"
	"sanj!sacmgr!henrym@caldwr.water.ca.gov"
BITNET:	"hmiller@scu"	!Warning: This is NOT the same machine
			as the above cluster.
UUCP:	"...caldwr!sanj!henrym"

"Bad guys abuse public land, good guys save it."