Browse Prior Art Database

Ability to Send/Receive any Format Frame on Ethernet using the IBM 802.2

IP.com Disclosure Number: IPCOM000115950D
Original Publication Date: 1995-Jul-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 84K

Publishing Venue

IBM

Related People

Heimsoth, DD: AUTHOR [+2]

Abstract

Currently, network application developers that would like to use the IBM* IEEE 802.2 protocol to handle the Logical Link Control (LLC) function for their application have to use the frame format specified by 802.5 for Token Ring or if they are coding for Ethernet they have to use either the frame format specified by IEEE 802.3 or IBM DIX (IBM's version of the Digital Intel Xerox protocol. There are OEM developers that have their own "homemade" frame formats that they use. These developers are not able to use the IBM IEEE 802.2 interface product because there currently is no mechanism by which their "homemade" frame formats could be supported.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Ability to Send/Receive any Format Frame on Ethernet using the IBM
802.2

      Currently, network application developers that would like to
use the IBM* IEEE 802.2 protocol to handle the Logical Link Control
(LLC) function for their application have to use the frame format
specified by 802.5 for Token Ring or if they are coding for Ethernet
they have to use either the frame format specified by IEEE 802.3 or
IBM DIX (IBM's version of the Digital Intel Xerox protocol.  There
are OEM developers that have their own "homemade" frame formats that
they use.  These developers are not able to use the IBM IEEE 802.2
interface product because there currently is no mechanism by which
their "homemade" frame formats could be supported.

      The solution to the problem of IBM 802.2 not transmitting or
receiving frames other than IBM DIX or IEEE 802.3 format is to
introduce
an enhancement to the IBM IEEE 802.2 Application Program Interface
(API).

      Currently, there is a DIRECT interface as part of IBM 802.2
interface that allows transmission and reception of Media Access
Control (MAC) frames from direct station number 1 and transmit and
receive non-MAC frames from direct station number 2.  These direct
stations are opened implicitly when the programmer executes a
DIR.OPEN.DIRECT verb.  The enhancement to the IBM 802.2 API is to
create a 3rd direct station that is  used to transmit and receive
frames that are not IBM DIX or IEEE 802.3.  This 3rd direct station
would also be opened implicitly when the DIR.OPEN.DIRECT verb is
issued.  Also, frames inbound and outbound would be directed to this
station after not passing the criteria for the first two direct
stations.

      From a programmer's point of reference, a new command code
representing the new command is introduced as x'3a'.  The programmer
uses this new command exactly as they would use a regular TRANSMIT
command API.

      This idea has been prototyped using IBM's Network Transport
Services product, (NTS/2)* 802.2 code as a base and given to a few
IBM customers to try out.  They have been satisfied with this
prototype.  A description of the...