The reservation styles

One can specify different options for a reservation:

Treatment of a reservation for different senders

If there are several senders within a session, either a distinct reservation for each sender or a single shared reservation for all the senders can be established.

Sender selection

It can be done either by an explicit list of senders or by a wildcard.

The specification on version 1 [#!RFC2205!#] defines three different reservation styles described in table .

Table: Reservation styles

Sender	Reservations

The WF style creates a single reservation for all the upstream senders. The SE style creates reservations for a set of upstream senders. The FF style is used to make distinct reservations for each particular sender. It is noticeable that those styles are important only for sessions with multiple senders. As far as unicast sessions are concerned, the FF is used since it is the simplest one.

RSVP has to merge different reservations if possible (figure ): the effective reservation on a node is the ``largest'' of all the reservations requested. The merging process depends on the reservation style, and two reservations with different styles cannot be merged.

Figure: Example of merging of reservation (WF style)