Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!SCORE.STANFORD.EDU!VAF
From: VAF@SCORE.STANFORD.EDU (Vince Fuller)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Your router's behaviour
Message-ID: <12460472338.31.VAF@Score.Stanford.EDU>
Date: 6 Jan 89 22:18:51 GMT
References: <8901061621.AA08225@uunet.UU.NET>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 8

I'm surprised that no one has made the obvious observation: this behavior is
completely broken for the simple reason that it is a gross violation of the
layering of the TCP/IP suite. ARP and IP are fundamentally independant - IP
can exist without ARP as can ARP without IP. This behavior adds cross-protocol
dependancies which do not belong there.

	Vince Fuller, Stanford Networking
-------