Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!nrl-cmf!mailrus!tut.cis.ohio-state.edu!bloom-beacon!husc6!spdcc!kaos!romkey
From: romkey@kaos.UUCP (John Romkey)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Proxy ARP (was Re: Dumb vs. smart host routing)
Message-ID: <887@kaos.UUCP>
Date: 18 May 88 17:42:04 GMT
References: <8805170444.AA20271@Larry.McRCIM.McGill.EDU>
Reply-To: romkey@kaos.UUCP (John Romkey)
Organization: Chaos; Somerville, MA
Lines: 18

In article <8805170444.AA20271@Larry.McRCIM.McGill.EDU> philipp@LARRY.MCRCIM.MCGILL.EDU (Philip A. Prindeville) writes:
>But you should be able to configure a router to not know about a
>network, and therefore not answer requests about it (to `unknow'
>the network, as it were).  If you can't do this, it reflects a
>flaw in the implementation, not the protocol.
>
>-Philip


Suppose I don't own and run all the routers. Suppose the university or
corporate telecommunications office does, or suppose BBN runs one of
them, or the company down the street. I don't necessarily have control
over all the computers on my network, and the level of effort needed
to go through to get the necessary changes done to some of them for 15
minutes of testing may be prohibitive.
-- 
			- john romkey
UUCP: romkey@kaos.uucp			ARPA: romkey@xx.lcs.mit.edu
 ...harvard!spdcc!kaos!romkey		Telephone: (617) 776-3121