Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!panda!genrad!decvax!decwrl!ucbvax!BRUBECK.PROTEON.COM!jas
From: jas@BRUBECK.PROTEON.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: re: How to IP & ARP on 802 nets
Message-ID: <8609090623.AA18262@ucbvax.Berkeley.EDU>
Date: Sun, 7-Sep-86 18:12:56 EDT
Article-I.D.: ucbvax.8609090623.AA18262
Posted: Sun Sep  7 18:12:56 1986
Date-Received: Tue, 9-Sep-86 20:41:59 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jas@proteon.com
Organization: The ARPA Internet
Lines: 19
Approved: tcp-ip@sri-nic.arpa

SNAP is not 'our' protocol, any more than 802.2 is ours. We don't
have any contorl over it. If we had wanted to avoid this mess, we (sigh)
should have been on 802.2. AS I noted, vendors are already using
SNAP.

The reason that the code is 3 bytes of owner, and two of protocol
number, is that they can then use the already-allocated 24-bit
prefixes that define 48-bit address blocks. Hey, 48-bits is absurdly
long, also.

I think that running a datagram network protocol like IP over class 2 802.2
is a non-sequitor, so we don't need to worry about it. I will admit that
I can't see how SNAP would work with class 2 at all. In the ISO world,
class 1 is used with connectionless internet at the network level, and
class 2 with a null network layer.

					john shriver
					proteon
-------