Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!QUABBIN.SCRC.Symbolics.COM!DCP
From: DCP@QUABBIN.SCRC.Symbolics.COM (David C. Plummer)
Newsgroups: mod.protocols.tcp-ip
Subject: How to IP & ARP on 802 Nets
Message-ID: <860902094524.9.DCP@KOYAANISQATSI.S4CC.Symbolics.COM>
Date: Tue, 2-Sep-86 09:45:00 EDT
Article-I.D.: KOYAANIS.860902094524.9.DCP
Posted: Tue Sep  2 09:45:00 1986
Date-Received: Tue, 2-Sep-86 21:03:41 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 32
Approved: tcp-ip@sri-nic.arpa


    Date: 29 Aug 1986 19:27:12 PDT
    From: POSTEL@B.ISI.EDU

    Hello. 
Hi.

    At an ad hoc special session on "IEEE 802 Networks and ARP" held
    during the recent TCP Vendors Workshop, an approach to a consistent
    way to sent DOD-IP datagrams and other IP related protocols on 802
    networks was developed.

    [...]

A very quick reading of this and a small amount of knowledge about 802.x
leads me to believe this looks reasonable.  The problem I see is "What
happens if ISO blesses DoD IP and then there are two different ways to
talk it?"

    The total length of the SAP Header and the SNAP header is 8-octets,
    making the 802.2 protocol overhead come out on a nice octet boundary.

Good.

    If we can not quickly resolve the issue of the values for K1 and K2,
    we will push for the assignment of a sap value (a K1 value) to
    indicate "IP related protocols" and do our own multiplexing (much like
    that proposed above).

Please don't say "IP related protocols."  Only one protocol is IP
related and that is IP.  Instead say "Ethernet'1980 related protocols"
which includes Chaos, PUP, XNS, DECnet, etc.