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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2.10 Asynchronous transfer mode (ATM)<br />

ATM-based networks are of increasing interest for both local <strong>and</strong> wide area<br />

applications. The ATM architecture is different from the st<strong>and</strong>ard LAN<br />

architectures <strong>and</strong>, for this reason, changes are required so that traditional LAN<br />

products will work in the ATM environment. In the case of <strong>TCP</strong>/<strong>IP</strong>, the main<br />

change required is in the network interface to provide support for ATM.<br />

There are several approaches already available, two of which are important to<br />

the transport of <strong>TCP</strong>/<strong>IP</strong> traffic. We describe these in 2.10.2, “Classical <strong>IP</strong> over<br />

ATM” on page 50 <strong>and</strong> 2.10.3, “ATM LAN emulation” on page 56. We also<br />

compare them in 2.10.4, “Classical <strong>IP</strong> over ATM versus LAN emulation” on<br />

page 59.<br />

2.10.1 Address resolution (ATMARP <strong>and</strong> InATMARP)<br />

The address resolution in an ATM logical <strong>IP</strong> subnet is done by the ATM Address<br />

Resolution Protocol (ATMARP), based on RFC 826 (also STD 37), <strong>and</strong> the<br />

Inverse ATM Address Resolution Protocol (InATMARP), based on RFC 2390.<br />

ATMARP is the same protocol as the ARP protocol, with extensions needed to<br />

support ARP in a unicast server ATM environment. InATMARP is the same<br />

protocol as the original InARP protocol, but applied to ATM networks. Use of<br />

these protocols differs depending on whether permanent virtual connections<br />

(PVCs) or switched virtual connections (SVCs) are used.<br />

Both ATMARP <strong>and</strong> InATMARP are defined in RFC 2225; a proposed st<strong>and</strong>ard<br />

with a state of elective. We describe the encapsulation of ATMARP <strong>and</strong><br />

InATMARP requests/replies in 2.10.2, “Classical <strong>IP</strong> over ATM” on page 50.<br />

InATMARP<br />

The ARP protocol resolves a host's hardware address for a known <strong>IP</strong> address.<br />

The InATMARP protocol resolves a host's <strong>IP</strong> address for a known hardware<br />

address. In a switched environment, you first establish a virtual connection (VC)<br />

of either a permanent virtual connection (PVC) or switched virtual connection<br />

(SVC) in order to communicate with another station. Therefore, you know the<br />

exact hardware address of the partner by administration, but the <strong>IP</strong> address is<br />

unknown. InATMARP provides dynamic address resolution. InARP uses the<br />

same frame format as the st<strong>and</strong>ard ARP, but defines two new operation codes:<br />

► InARP request=8<br />

► InARP reply=9<br />

See “ARP packet generation” on page 120 for more details.<br />

Chapter 2. Network interfaces 47

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

Saved successfully!

Ooh no, something went wrong!