Platform SDK: Quality of Service |
The cbpGetRsvpObjects function is a callback function for LPMs to asynchronously return results for LPM_GetRsvpObjects requests. LPMs call the cbpGetRsvpObjects function to asynchronously return policy data objects to the PCM for an LPM_GetRsvpObjects request. An LPM should only use the cbpGetRsvpObjects function if it returned LPM_RESULTS_DEFER to the PCM's LPM_GetRsvpObjects request.
ULONG cbpGetRsvpObjects ( LPM_HANDLE LpmHandle, RHANDLE RequestHandle, ULONG LpmError, int RsvpObjectsCount, POLICY_DATA *RsvpObjects[] );
If no policy data objects are being returned, LpmError must be set to LPM_OK, RsvpObjectsCount must be set to zero, and *RsvpObjects must be set to NULL. The LPM can force the SBM to stop sending out the RSVP message by setting the value of LpmError to LPV_DROP_MSG.
If no policy data objects are being returned, LpmError must be set to LPM_OK, RsvpObjectsCount must be set to zero, and *RsvpObjects must be set to NULL.
LPMs do not need to send policy data options if only default options are required. Since the content of policy data objects are opaque to the PCM, no host-to-network order conversion of policy element headers and contents will be done by the PCM; the PCM expects LPMs to generate policy elements in the network order such that the receiver of the policy elements can correctly parse them. However, the policy data object header must be in host order to allow the PCM to merge policy elements (if possible or applicable).
From LPMs that support all PE types, the PCM expects complete policy data objects and their required policy data options. Furthermore, the PCM expects the policy data object header to be in host order; it is the responsibility of the LPM to process the host-to-network order conversions of policy options and policy elements.
If any LPM returns LPV_DROP_MSG, the SBM will not send out an RSVP refresh message, but will free the policy data objects returned by other LPMs (those that did not return LPV_DROP_MSG, if any). By not sending out RSVP refresh messages, a flow's RSVP state both upstream and downstream will begin to age, and eventually get deleted.
Note The SBM will send out the RSVP refresh message even if some or all LPMs fail to return policy data objects in a timely fashion, even though such an outgoing RSVP message may not contain all policy data objects it should.
Windows NT/2000: Requires Windows 2000.
Windows 95/98: Unsupported.