| Previous | Next |
| WSA_QOS_NO_RECEIVERS | WSA_QOS_ADMISSION_FAILURE |
WSA_QOS_REQUEST_CONFIRMED
Confirmation acknowledges the reservation request, not future path permanence
WSA_QOS_REQUEST_CONFIRMED is generated when a requested RSVP reservation confirmation reaches the receiver. The request is made through the ConfirmRequest member of RSVP_RESERVE_INFO. Confirmation shows that the reservation was installed far enough along the path for a confirming node to respond; it does not make the soft state permanent or guarantee that routing will remain unchanged.
Store the confirmation with the exact session, flow descriptor, style, and requested FLOWSPEC. Later topology changes, preemption, policy changes, or missed refreshes can still remove the reservation. A missing confirmation is also not automatically a failed reservation because RSVP nodes are not required to generate confirmation messages in every case. Diagnose it together with the underlying reservation status and extended provider information.
Data that makes confirmation meaningful
- ConfirmRequest value used by the receiver.
- Flow descriptor and filter list sent with the request.
- Confirmed service type and bandwidth parameters.
- Subsequent refresh or preemption events.
References
- Microsoft: RSVP_RESERVE_INFO and ConfirmRequest
- Microsoft: RSVP status and extended fields
- IETF RFC 2205: reservation confirmation
Looking for a different code? Search another status or error code.