Академический Документы
Профессиональный Документы
Культура Документы
McLaughlin III
Request for Comments: 1132 The Wollongong Group
November 1989
Introduction
Description
McLaughlin [Page 1]
RFC 1132 802.2 Packets over IPX Networks November 1989
Address Mappings
Byte Order
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.
Checksum
Like most IPX applications, this specification does not use IPX
checksum.
Reserved values
The IPX socket 0x8060 has been reserved by Novell for the
implementation of this protocol.
Implementation
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
below:
--------------------
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 |
--------------------
References
[1] IEEE, "IEEE Standards for Local Area Networks: Logical Link
Control", IEEE, New York, 1985.
McLaughlin [Page 3]
RFC 1132 802.2 Packets over IPX Networks November 1989
1986.
[7] Postel, J., and J. Reynolds, "A Standard for the Transmission of
IP Datagrams over IEEE 802 Networks", RFC-1042, USC/Information
Sciences Institute, February 1988.
[8] Cohen, D., "On Holy Wars and a Plea for Peace", Computer, IEEE,
October 1981.
Security Considerations
Author's Address:
EMail: ljm@TWG.COM
McLaughlin [Page 4]