Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!proteon.arpa!jas From: jas@PROTEON.ARPA Newsgroups: mod.protocols.tcp-ip Subject: 802.2 SAP's Message-ID: <8510252218.AA07509@ucb-vax.berkeley.edu> Date: Fri, 25-Oct-85 17:41:16 EDT Article-I.D.: ucb-vax.8510252218.AA07509 Posted: Fri Oct 25 17:41:16 1985 Date-Received: Sat, 26-Oct-85 08:24:23 EDT Sender: usenet@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 23 Approved: tcp-ip@ucbvax.berkeley.edu Given as IBM has annouced their 802.5 network, those of us who use IP are starting to think about running IP over it. I've looked at RFC 948 (Two methods for IP over 802.3), and it mentions the issue of using 802.2 SAP's. With 802.5, we don't have any choice but to use SAPs. There is no type field in the header like there was in Ethernet. There is a SAP for IP, as well as ones for ISO and SNA. However we don't have a SAP for ARP, or anything like it. All three of the 802.[345] networks use 48-bit addresses, so all of them will need ARP to map from 32 bits to 48. (Now is not the time to start using translation tables.) Has anybody seen any efforts in this direction from standards bodies? Who beat up the IEEE 802.2 committee to get the IP SAP in the first place? It would be really nice if there were a good RFC as to how IP runs over 802.2/802.5 before a line of code gets written. Let's not have incompatible IP's. (Of course, maybe all this is solved by 802.1, but I doubt it.) -------