25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

► Introduced in 1985, RFC 948 – Two Methods for the Transmission of <strong>IP</strong><br />

Datagrams over IEEE 802.3 Networks specifies two possibilities:<br />

– The Ethernet compatible method: The frames are sent on a real IEEE<br />

802.3 network in the same fashion as on an Ethernet network, that is,<br />

using the IEEE 802.3 data-length field as the Ethernet type field, thereby<br />

violating the IEEE 802.3 rules, but compatible with an Ethernet network.<br />

– IEEE 802.2/802.3 LLC type 1 format: Using 802.2 LSAP header with <strong>IP</strong><br />

using the value 6 for the SSAP <strong>and</strong> DSAP fields.<br />

The RFC indicates clearly that the IEEE 802.2/802.3 method is the preferred<br />

method, that is, that all future <strong>IP</strong> implementations on IEEE 802.3 networks are<br />

supposed to use the second method.<br />

► Introduced in 1987, RFC 1010 – Assigned Numbers (now obsoleted by RFC<br />

3232, dated 2002) notes that as a result of IEEE 802.2 evolution <strong>and</strong> the need<br />

for more Internet protocol numbers, a new approach was developed based on<br />

practical experiences exchanged during the August 1986 <strong>TCP</strong> Vendors<br />

Workshop. It states, in an almost completely overlooked part of this RFC, that<br />

all IEEE 802.3, 802.4, <strong>and</strong> 802.5 implementations should use the Subnetwork<br />

Access Protocol (SNAP) form of the IEEE 802.2 LLC, with the DSAP <strong>and</strong><br />

SSAP fields set to 170 (indicating the use of SNAP), with SNAP assigned as<br />

follows:<br />

– 0 (zero) as organization code<br />

– EtherType field:<br />

2048 (hex 0800), for <strong>IP</strong> datagrams<br />

2054 (hex 0806), for ARP datagrams<br />

32821 (hex 8035), for RARP datagrams<br />

These are the same values used in the Ethernet type field.<br />

► In1988, RFC 1042 – St<strong>and</strong>ard for the Transmission of <strong>IP</strong> Datagrams over<br />

IEEE 802 Networks was introduced. Because this new approach (very<br />

important for implementations) passed almost unnoticed in a little note of an<br />

unrelated RFC, it became quite confusing. As such, in February of 1988 it<br />

was repeated in an RFC on its own, RFC 1042, which now obsoletes RFC<br />

948.<br />

► In 1998, RFC 2464 – Transmission of <strong>IP</strong>v6 Packets over Ethernet Networks<br />

was introduced. This extended Ethernet’s frame format to allow <strong>IP</strong>v6 packets<br />

to traverse Ethernet networks.<br />

The relevant <strong>IBM</strong> <strong>TCP</strong>/<strong>IP</strong> products implement RFC 894 for DIX Ethernet <strong>and</strong><br />

RFC 3232 for IEEE 802.3 networks. However, in practical situations, there are<br />

still <strong>TCP</strong>/<strong>IP</strong> implementations that use the older LSAP method (RFC 948 or 1042).<br />

32 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!