09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

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.

eassembled before being handed <strong>to</strong> <strong>the</strong> ULP. Additionally, IP does not guarantee<br />

datagram delivery. The Layer 2 transmission devices involved in <strong>the</strong> transport of<br />

datagrams can discard <strong>the</strong> Layer 2 frames containing IP datagrams if <strong>the</strong> adequate<br />

resources needed for transmission are unavailable. In <strong>the</strong> event that IP datagrams<br />

are lost, it is <strong>the</strong> responsibility of <strong>the</strong> ULP of <strong>the</strong> transmitting host <strong>to</strong> resend <strong>the</strong> lost<br />

data.<br />

The following section explains <strong>the</strong> many components of <strong>the</strong> IP pro<strong>to</strong>col and its<br />

operation, such as its interaction with <strong>the</strong> Layer 2 pro<strong>to</strong>cols that provide <strong>network</strong><br />

address <strong>to</strong> transmission address translation, <strong>the</strong> structure of <strong>the</strong> IP datagram, and<br />

<strong>the</strong> various elements of <strong>network</strong> addressing, including IP datagram delivery.<br />

IP Interactions with Layer 2 (ARP, Proxy ARP, and<br />

RARP)<br />

All Layer 3 delivery is dependent upon Layer 2 for actual transport. This being <strong>the</strong><br />

case, a mechanism needs <strong>to</strong> exist for translating Layer 3 <strong>network</strong> addresses <strong>to</strong><br />

Layer 2 transport addresses. The ARP pro<strong>to</strong>col was developed <strong>to</strong> perform <strong>the</strong>se<br />

translations for IP.<br />

When IP assembles a datagram, it takes <strong>the</strong> destination address provided by <strong>the</strong><br />

ULP and performs a lookup in <strong>the</strong> host's route table <strong>to</strong> determine if <strong>the</strong> destination<br />

is local or remote <strong>to</strong> itself. If <strong>the</strong> destination is local, <strong>the</strong> datagram is delivered<br />

directly <strong>to</strong> <strong>the</strong> local host. If <strong>the</strong> datagram is not local, <strong>the</strong> datagram is sent <strong>to</strong> a<br />

<strong>network</strong> gateway, which takes responsibility <strong>to</strong> ensure that it is delivered correctly.<br />

In ei<strong>the</strong>r case, <strong>the</strong> IP datagram needs <strong>to</strong> be placed inside a Layer 2 packet for<br />

delivery.<br />

In order <strong>to</strong> determine <strong>the</strong> correct Layer 2 destination address, <strong>the</strong> sending host<br />

must have a mechanism for translating <strong>the</strong> Layer 2 <strong>to</strong> Layer 3 address map. It uses<br />

Address Resolution Pro<strong>to</strong>col (ARP), which is a dynamic process, and Reverse<br />

Address Resolution Pro<strong>to</strong>col (RARP), which is an application service, <strong>to</strong> assist it in<br />

finding <strong>the</strong> locally connected hosts. ARP and RARP map <strong>the</strong> different Layer 2<br />

pro<strong>to</strong>col addresses (for example, E<strong>the</strong>rnet/and Token Ring) <strong>to</strong> <strong>the</strong> 32-bit addresses<br />

used by IP <strong>to</strong> identify <strong>the</strong> different hosts on <strong>the</strong> <strong>network</strong>. Technically, both <strong>the</strong> Layer<br />

2 and Layer 3 IP addresses both provide <strong>the</strong> same basic function of host<br />

identification in terms of <strong>the</strong> data delivery process, but never<strong>the</strong>less, <strong>the</strong> addresses<br />

are incompatible. So, in order for data <strong>to</strong> be delivered between locally connected<br />

hosts, a remapping service is needed.<br />

ARP runs as a local process on a host (computer or o<strong>the</strong>r <strong>network</strong> device) connected<br />

<strong>to</strong> <strong>the</strong> <strong>network</strong>. ARP accomplishes two tasks:

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

Saved successfully!

Ooh no, something went wrong!