Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!swrinde!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: <9009241641.AA02473@asylum.sf.ca.us>
Date: 24 Sep 90 23:41:30 GMT
References: <9009242042.AA20936@hogg.cc.uoregon.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 15

Well, I speak only for myself and say only me perception of the
matter. I don't speak for the Hosts Requirements group.

I believe that the reason for all hosts to be able to hear Ethernet
packets is that very few vendors supported (and even now, support)
RFC 1042 encapsulation, and the group wanted to ensure
interoperability. In practical terms, if you want to interoperate with
TCP/IP on ethernet/IEEE 802.3 networks, you must support RFC 894
encapsulation. I think that requirement is just a reflection of the
practical situation we're living with now.

If you want the voice of Host Requirements on the matter, Bob Braden
will have to speak up.
			- john romkey
USENET/UUCP: romkey@asylum.sf.ca.us	Internet: romkey@ftp.com