Standard for the transmission of 802.2 packets over IPX networks
RFC 1132

Document Type RFC - Internet Standard (November 1989; No errata)
Also known as STD 49
Author Leo McLaughlin 
Last updated 2013-03-02
Stream Legacy stream
Formats plain text html pdf htmlized (tools) htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1132 (Internet Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                  L. McLaughlin III
Request for Comments: 1132                          The Wollongong Group
                                                           November 1989

   A Standard for the Transmission of 802.2 Packets over IPX Networks

Status of this Memo

   This document specifies a standard method of encapsulating 802.2 [1]
   packets on networks supporting Novell's Internet Packet Exchange
   Protocol [2] (IPX).  It obsoletes earlier documents detailing the
   transmission of Internet packets over IPX networks.  It differs from
   these earlier documents in that it allows for the transmission of
   multiple network protocols over IPX and for the transmission of
   packets through IPX bridges.  Distribution of this memo is unlimited.


   The goal of this specification is to allow compatible and
   interoperable implementations for transmitting Internet packets such
   as the Internet Protocol [3] (IP) and Address Resolution Protocol [4]
   (ARP) as well as the Connectionless-mode Network Protocol [5] (CLNP)
   over IPX networks.

   IPX is a proprietary standard developed by Novell derived from
   Xerox's Internet Datagram Protocol [6] (IDP). Defining the
   encapsulation of the IEEE 802.2 Data Link Layer Standard over IPX in
   terms of yet another 802.X Physical Layer standard allows for the
   transmission of IP Datagrams as described in RFC 1042 [7].  This
   document will focus on the implementation of that RFC over IPX


   In general, this specification allows IPX networks to be used to
   support any network protocol which can use the IEEE 802.2 Data Link
   Layer specification.

   More specifically, IPX networks may be used to support IP networks
   and subnetworks of any class.  By encapsulating IP datagrams within
   IPX datagrams and assigning IP numbers to the hosts on a IPX network,
   IP-based applications are supported on these hosts.  The addition of
   an IP Gateway capable of encapsulating IP packets within 802.IPX
   datagrams would allow those hosts on an IPX network to communicate
   with the Internet.

McLaughlin                                                      [Page 1]
RFC 1132            802.2 Packets over IPX Networks        November 1989

Maximum Transmission Unit

   The maximum data size of a IPX datagram is 546 bytes.  As the
   combined size of the 802.2 LLC and SNAP headers is 8 bytes, this
   results in a Maximum Transmission Unit (MTU) of 538 bytes.

Address Mappings

   The mapping of Internet Protocol addresses to 802.IPX addresses is
   done using the Address Resolution Protocol in the same fashion as
   with other IEEE 802.X physical addresses.  However, the length of an
   802.IPX physical address is 10 bytes rather than 2 or 6.  This 10
   byte physical address consists of the 4 bytes of the IPX network
   address followed by the 6 bytes of the IPX node address.

Byte Order

   The byte transmission order is "big-endian" [8].

Broadcast Addresses

   IPX packets may be broadcast by setting the IPX header Packet Type
   field to 0x14, the Destination Network field to the local network
   number, the the Destination Node field to 0xffffff, and the Immediate
   Address field of the IPX Event Control Block to 0xffffff.

Unicast Addresses

   IPX packets may be unicast by setting the IPX header Packet Type
   field to 0x04, the Destination Network field and Destination Node
   field to those values found by address resolution, and the Immediate
   Address field of the IPX Event Control Block to the physical address
   of the destination node or the appropriate IPX bridge.


   Like most IPX applications, this specification does not use IPX

Reserved values

   The IPX socket 0x8060 has been reserved by Novell for the
   implementation of this protocol.


   The encapsulation of Internet packets within IPX networks has proved
   to be quite useful.  Because the IPX interface insulates knowledge of

McLaughlin                                                      [Page 2]
RFC 1132            802.2 Packets over IPX Networks        November 1989

   the physical layer from an application, 802.2 over IPX networks work
   over any physical medium.  A typical IP over IPX packet is shown

                    N bytes   |  physical header |
                   30 bytes   |    IPX header    |
                    8 bytes   |   802.2 header   |
           usually 20 bytes   |     IP header    |
           usually 20 bytes   |    TCP header    |
            up to 498 bytes   |    TCP data      |
Show full document text