Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!ASYLUM.SF.CA.US!romkey
From: romkey@ASYLUM.SF.CA.US (John Romkey)
Newsgroups: comp.protocols.tcp-ip
Subject: choosing ethernet packet type automatically
Message-ID: <9009241126.AA00500@asylum.sf.ca.us>
Date: 24 Sep 90 18:26:06 GMT
References: <9009241320.AA23877@decwrl.dec.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 10

The ARP scheme you suggested is what I and other people suggested.
When we talked about it in the Host Requirements group, problem after
problem surfaced until someone finally said, "Look, why don't we do it
the right way? They're different encapsulations; put a router between
them." And we were enlightened.

The router solution can be made to work now, and I really think it's
the right one.
			- john romkey
USENET/UUCP: romkey@asylum.sf.ca.us	Internet: romkey@ftp.com