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.

A.1 MPLS: An introduction<br />

The idea behind MPLS was to emulate some property of circuit-switching<br />

network over a packet network, <strong>and</strong> to strike a happy middleground between<br />

extreme connection-oriented switching <strong>and</strong> pure connectionless routing service.<br />

The theory for the idea of “mixing types to meet in the middle” was based on the<br />

observation that a sequence of correlated packets exist for stream <strong>and</strong><br />

multimedia applications. We wanted to process them in the same routing path in<br />

a uniform fashion in order to guarantee quality of service (QoS). And we did not<br />

want to repeatedly examine <strong>and</strong> process those packet headers. The idea is<br />

feasible because we note that the headers in those related packets are the same<br />

or similar because those related packets in a stream desire consistent <strong>and</strong><br />

similar processing treatment.<br />

Multiprotocol Label Switching (MPLS) follows the same idea <strong>and</strong> comes up with<br />

new techniques to make a pseudo (<strong>and</strong> short-term) connection in a path (or<br />

subpath) for a sequence of correlated <strong>IP</strong> packets. The technology was proposed<br />

in RFC 3031. The Multiprotocol Label Switching (MPLS) st<strong>and</strong>ard represents<br />

the effort in the continued evolution of multilayer switching.<br />

Generalized MPLS or GMPLS extends MPLS to encompass time-division (for<br />

example, SONET/SDH), wavelength (lambdas), <strong>and</strong> spatial switching (for<br />

example, incoming port or fiber to outgoing port or fiber). The focus of GMPLS is<br />

on the control plane of these various layers to dynamically provision resources<br />

<strong>and</strong> to provide network survivability using protection <strong>and</strong> restoration techniques.<br />

A.1.1 Conventional routing versus MPLS forwarding mode<br />

First, let us describe how the new paradigm shift might help in improving QoS<br />

performance by comparing conventional routing to the MPLS forwarding mode.<br />

In an MPLS environment, conventional layer-3 or network-layer routing (that is,<br />

<strong>IP</strong> routing) is used to determine a path through the network. After the path is<br />

determined, data packets are then switched through each node as they traverse<br />

the network.<br />

Conventional routing mode<br />

In a traditional, connectionless network, every router runs a layer-3 routing<br />

algorithm. As a packet traverses through the network, each router along the path<br />

makes an independent forwarding decision for that packet. Using information<br />

contained in the packet header, as well as information obtained from the routing<br />

algorithm, the router chooses a “next hop” destination for the packet. In an <strong>IP</strong><br />

network, this process involves matching the destination address stored in the <strong>IP</strong><br />

header of each packet with the most specific route obtained from the <strong>IP</strong> routing<br />

926 <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!