Resource Reservation Protocol
| RSVP (Resource Reservation Protocol) | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Family: | Internet protocol family | ||||||||||||||||||||
| Operation area: | Signaling protocol in the internet protocol stack | ||||||||||||||||||||
|
|||||||||||||||||||||
| Standards: | RFC 2205 (1997) | ||||||||||||||||||||
The Resource reSerVation Protocol ( RSVP ) is a signaling protocol in the Internet Protocol stack. It allows recipients outside of a multicast group to define their service requirements. This means that certain transmission rates can be reserved for individual connections for certain applications , for example for the transmission of video streams . In version 4 of the Internet Protocol ( IPv4 ), such guarantees are not actually provided, which in the example of the video streams can lead to buffering pauses .
RSVP can also reserving the QoS ( Quality of Service with QoS) unicast transmissions are used. Such a reservation is structured as follows:
- The sender sends a special message to the recipient, the RSVP Path message (German RSVP path message). This determines a possible path from the transmitter to the receiver. The routers passed through are logged as RSVP hop objects in the RSVP path message and are thus communicated to the recipient.
- Along the logged path, the recipient sends another message, the RSVP reservation message (German RSVP reservation message ) back (to the sender of the RSVP path message ). The RSVP reservation message contains a so-called flow specification which describes the requirements for the reservation.
- The routers on the way reserve the resources according to this flow specification or send back an error message. If the RSVP reservation message arrives at the sender, it can rely on the reservations and send it according to the specification.
- This reservation must be confirmed periodically by the sender at fixed intervals and will otherwise be deleted. It is therefore a soft state .
Possible levels of QoS are rate-sensitive (inquires about a certain transmission rate), delay-sensitive (maximum permissible delay), and best effort .
See also
- Quality of service procedure:
- Common Open Policy Service (communication between routers)
Web links
- RFC 2205 specifies the Resource Reservation Protocol .