walsh@apollo.uucp (Wendy Walsh) (07/06/88)
Is there an official method of running XNS over 802.2 (LLC)? Is a SNAP protocol
used like with DoD IP over 802.2? Is a vendor ID used? Is there an official
LSAP for XNS?
Please email responses and I will summarize to the net if interest warrants it.
Wendy G. Walsh
Apollo Computer Inc.
ARPA: walsh@apollo.com
UUCP: {decwrl!decvax, mit-eddie, attunix}!apollo!walshrpw3@amdcad.AMD.COM (Rob Warnock) (07/10/88)
In article <3d16a4c5.17aea@apollo.uucp> walsh@apollo.uucp (Wendy Walsh) writes: +--------------- | Is there an official method of running XNS over 802.2 (LLC)? Is a SNAP | protocol used like with DoD IP over 802.2? Is a vendor ID used? +--------------- Yes, yes, and yes. In fact, the DoD IP SNAP uses the Xerox method, and the vendor ID for both is "Xerox" (the value of which is 0x000000?). Xerox told the world that the last two bytes of "their" SNAP (vendor ID == "Xerox") would always be the "Ethernet" type field, which made the DoD IP folk very happy and was a major factor in the switch to SNAP for IP, since though IP had an "official IEEE" LSAP, the IEEE wouldn't give out more LSAPs for ARP, BOOTP, etc. As it stands now, everybody who wants to convert "Ethernet" (D/I/X "blue book") to 802.3/802.2 is using the "SNAPpy Xerox" method. Another way of saying it: Take the last two bytes of the DoD IP SNAP header and change the 0x0800 to 0x600, and you've got XNS. +--------------- | Is there an official LSAP for XNS? +--------------- Not that I know of. That's why SNAP was invented, to give vendors a way to embed their proprietary protocols (non-ISO) in 802.2. It's just that Xerox and DoD IP (and others) are using "SNAPpy Xerox" to embed a "proprietary protocol" named "Ethernet" in 802.3/802.2. Rob Warnock Systems Architecture Consultant UUCP: {amdcad,fortune,sun,attmail}!redwood!rpw3 ATTmail: !rpw3 DDD: (415)572-2607 USPS: 627 26th Ave, San Mateo, CA 94403