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.

If the path message reaches the first RSVP router, the router stores the <strong>IP</strong><br />

address from the last hop field in the message, which is the address of the<br />

sender. Then the router inserts its own <strong>IP</strong> address into the last hop field, sends<br />

the path message to the next router, <strong>and</strong> the process repeats until the message<br />

has reached the receiver. At the end of this process, each router will know the<br />

address from the previous router <strong>and</strong> the path can be accessed backwards.<br />

Figure 8-4 shows the process of the path definition.<br />

Sender<br />

Path<br />

Router 1<br />

Address of<br />

Sender<br />

Figure 8-4 RSVP path definition process<br />

Routers that have received a path message are prepared to process resource<br />

reservations for a flow. All packets that belongs to this flow will take the same<br />

way through the routers (the way that was defined with the path messages).<br />

The status in a system after sending the path messages is as follows: All<br />

receivers know that a sender can provide a special QoS for a flow <strong>and</strong> all routers<br />

know about the possible resource reservation for this flow.<br />

Now if a receiver wants to reserve QoS for this flow, it sends a reservation (Resv)<br />

message. The reservation message contains the QoS requested from this<br />

receiver for a specific flow <strong>and</strong> is represented by the filterspec <strong>and</strong> flowspec that<br />

form the flow descriptor. The receiver sends the Resv message to the last router<br />

in the path with the address it received from the path message. Because every<br />

RSVP-capable device knows the address of the previous device on the path,<br />

reservation messages travel the path in reverse direction toward the sender <strong>and</strong><br />

298 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong><br />

Router 2<br />

Address of<br />

Router 1<br />

Router 3<br />

Address of<br />

Router 2<br />

Router 4<br />

Path<br />

Router 5<br />

Address of<br />

Router 3<br />

Path<br />

Receiver<br />

Address of<br />

Router 5

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

Saved successfully!

Ooh no, something went wrong!