Resource Reservation Protocol (RSVP), specified in RFC 2205, is a signaling protocol for delivering guaranteed quality of service on a network. Clients use RSVP to request QoS guarantees (called reservations) from routers, and routers use RSVP to deliver requests and information about the reservations to other routers. An RSVP client might be embedded in a router instead of the typical workstation; for example, a router could be delivering voice from a private branch exchange (PBX) over the IP network and might use RSVP to request a reservation that guarantees successful delivery of the real-time traffic across the network.
An RSVP reservation guarantees QoS for an application flow, called a session. A session is equivalent to any TCP or UDP flow, such as a packetized video or audio stream or even a simple FTP transfer. A session might be a unicast transmission, such as a private audio stream from one client to another, or it might be a multicast transmission, such as a broadcast from a video server to an IP multicast address viewed by members of a multicast group. Again, the content of the session does not have to be multimedia in nature: It can be any TCP or UDP flow. However, RSVP was clearly created with real-time applications such as packetized video and audio in mind.
This section covers
• RSVP Admission Control
• RSVP Signaling Versus Bulk Data
• The RSVP Signaling Process
• RSVP and Weighted Fair Queuing
• Configuring RSVP
• Verifying RSVP Configuration
• Configuring IOS as a Proxy for Path and Resv Messages
• RSVP Scaling Considerations
Was this article helpful?