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.

Initialization<br />

During initialization, the LE layer (workstation) establishes the default VC with<br />

the LE server. It also discovers its own ATM address, which is needed if it is to<br />

later set up direct VCs.<br />

Registration<br />

In this phase, the LE layer (workstation) registers its MAC addresses with the LE<br />

server. Other things, such as filtering requirements (optional), can be provided.<br />

Management <strong>and</strong> resolution<br />

This is the method used by ATM endstations to set up direct VCs with other<br />

endstations (LE layers). This function includes mechanisms for learning the ATM<br />

address of a target station, mapping the MAC address to an ATM address,<br />

storing the mapping in a table, <strong>and</strong> managing the table.<br />

For the server, this function provides the means for supporting the use of direct<br />

VCs by endstations. This includes a mechanism for mapping the MAC address of<br />

an end system to its ATM address, storing the information, <strong>and</strong> providing it to a<br />

requesting endstation.<br />

This structure maintains full LAN function <strong>and</strong> can support most higher layer LAN<br />

protocols. Reliance on the server for data transfer is minimized by using switched<br />

VCs for the transport of most bulk data.<br />

2.10.4 Classical <strong>IP</strong> over ATM versus LAN emulation<br />

These two approaches to providing an easier way to migrate to ATM were made<br />

with different goals in mind.<br />

Classical <strong>IP</strong> over ATM defines an encapsulation <strong>and</strong> address resolution method.<br />

The definitions are made for <strong>IP</strong> only <strong>and</strong> not for use with other protocols. So if<br />

you have applications requiring other protocol stacks (such as <strong>IP</strong>X or SNA), <strong>IP</strong><br />

over ATM will not provide a complete solution. However, if you only have <strong>TCP</strong> or<br />

UDP-based applications, this might be the better solution, because this<br />

specialized adaptation of the <strong>IP</strong> protocol to the ATM architecture is likely to<br />

produce fewer inefficiencies than a more global solution. Another advantage of<br />

this implementation is the use of some ATM-specific functions, such as large<br />

MTU sizes.<br />

The major goal of the ATM Forum's approach is to run layer 3 <strong>and</strong> higher<br />

protocols unchanged over the ATM network. This means that existing protocols,<br />

for example, <strong>TCP</strong>/<strong>IP</strong>, <strong>IP</strong>X, NetBIOS, <strong>and</strong> SNA, <strong>and</strong> their applications can use the<br />

benefits of the fast ATM network without any changes. The mapping for all<br />

protocols is already defined. The LAN emulation (LANE) layer provides all the<br />

Chapter 2. Network interfaces 59

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

Saved successfully!

Ooh no, something went wrong!