Receiving Applications

For the RSVP SP to invoke RSVP processing and signaling, the receiving application is required to provide the following information:

• QOS parameters, through the use of the ReceivingFlowspec member of the QOS structure. Receiving applications generally provide such QOS parameters in a call to the WSAConnect or WSAJoinLeaf functions, or in a call to the WSAIoctl(SIO_SET_QOS) function/opcode pair.

For receiving applications, the RSVP SP must create a session object, and in certain cases must create a filterspec object (filterspec selects a subset of the senders by specifying their address) for placement into its RESV messages. These objects are generally matched to the PATH state (which itself is derived from corresponding PATH messages). In order to limit matching of the PATH state, the RSVP SP needs the following information:

• Peer address or addresses (the source address). This enables RSVP to limit RSVP sessions for which RESV messages are sent.
• Local address. The RSVP SP uses the local address to match received PATH messages and to select the interface on which to send out the RESV message.

Transmission of RESV messages begins as soon as the RSVP service has sufficient information.

Details of each of these receiver types are outlined individually in the following reference pages:

• UDP unicast receivers
• UDP multicast receivers
• TCP unicast receivers