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

Create successful ePaper yourself

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

You should also keep in mind that <strong>the</strong> Layer 3 IP source and destination addresses<br />

have not changed; only <strong>the</strong> Layer 2 addresses changed as <strong>the</strong> IP datagram moved<br />

from <strong>network</strong> <strong>to</strong> <strong>network</strong>.<br />

This example walks you through <strong>the</strong> Layer 2/Layer 3 forwarding process. The same<br />

process is performed by every router that forwards IP datagrams. Also in this<br />

example, you see <strong>the</strong> use of redundant paths <strong>to</strong> deliver datagrams. If <strong>the</strong> link<br />

between Router A and Router D went down, <strong>the</strong> datagram could have been<br />

delivered over <strong>the</strong> Router A <strong>to</strong> Router C, Router C <strong>to</strong> Router D link.<br />

The Internet Routing Process<br />

Most people's experience with IP routing started with <strong>the</strong>ir involvement with <strong>the</strong><br />

Internet. The Internet is <strong>the</strong> common name of <strong>the</strong> global inter<strong>network</strong> of tens of<br />

thousands of distinct inter/intra<strong>network</strong>s. The Internet was <strong>the</strong> driving force behind<br />

<strong>the</strong> development of various dynamic IP routing pro<strong>to</strong>cols. Although <strong>the</strong> intricacies of<br />

<strong>the</strong>se pro<strong>to</strong>cols are covered in Chapter 8, an introduction on <strong>the</strong> use of dynamic<br />

routing pro<strong>to</strong>cols is needed in <strong>the</strong> context of a chapter on TCP/IP.<br />

When large enterprise and regional <strong>network</strong>s use centralized routing pro<strong>to</strong>cols <strong>to</strong><br />

manage <strong>the</strong>ir routers, an intradomain routing policy is followed. In instances where<br />

multiple routing pro<strong>to</strong>cols are being used <strong>to</strong> cross-pollinate routing information, an<br />

interdomain routing policy is followed because more than one routing domain is<br />

being used <strong>to</strong> manage <strong>the</strong> route discovery across <strong>the</strong> entire <strong>network</strong>.<br />

The distinctions between intradomain and interdomain make more sense when you<br />

examine how large and extremely large IP <strong>network</strong>s are structured. Intradomain<br />

routing is generally used in intra<strong>network</strong>s. Most company-wide <strong>network</strong>s can be<br />

considered intra<strong>network</strong>s. An intra<strong>network</strong> can be a single LAN or a collection of<br />

LANs connected by private data links. What defines an intra<strong>network</strong> is its usage.<br />

Intranets have an exclusive set of users, and access is restricted only <strong>to</strong> that user<br />

community. Most intranets pursue an intradomain routing policy. The term<br />

"intra<strong>network</strong>" is relatively new. The distinction arose as more and more office LANs<br />

and company-wide private data <strong>network</strong>s began installing access points <strong>to</strong> <strong>the</strong><br />

global Internet.<br />

Intra<strong>network</strong>s use Regional Internet Service Providers (RISPs) and/or National<br />

Internet Service Providers (NISPs) <strong>to</strong> gain access <strong>to</strong> <strong>the</strong> Internet. RISPs and NISPs<br />

operate inter<strong>network</strong>s, which are <strong>network</strong>s made up of multiple distinct <strong>network</strong>s<br />

that operate as separate routing domains. These <strong>network</strong>s connect <strong>to</strong> a common<br />

inter<strong>network</strong> backbone that exists as a routing domain apart from <strong>the</strong> distinct

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

Saved successfully!

Ooh no, something went wrong!