| Previous | Next |
| WSA_QOS_ESERVICETYPE | WSA_QOS_EPROVSPECBUF |
WSA_QOS_EFLOWSPEC
A FLOWSPEC is a related parameter set, not independent limits
WSA_QOS_EFLOWSPEC indicates that one of the two standard FLOWSPEC structures in QOS violates field relationships or direction-specific requirements. Typical inconsistencies include a peak bandwidth below the token rate, an invalid service type, a zero minimum policed size in RSVP usage, or required receiver parameters left unspecified.
Log every field in both SendingFlowspec and ReceivingFlowspec; a valid sending request can coexist with an invalid receiving request. Recalculate rate units, latency, delay variation, token bucket size, and maximum packet size using unsigned 32-bit boundaries. Do not inspect only the field named by the application configuration because the provider may derive RSVP Tspec and Rspec values from several members together.
FLOWSPEC validation order
- ServiceType and direction.
- TokenRate, TokenBucketSize, and PeakBandwidth.
- Latency and DelayVariation.
- MinimumPolicedSize and MaxSduSize.
References
- Microsoft: sending and receiving FLOWSPEC members
- Microsoft: complete FLOWSPEC constraints
- IETF RFC 2210: mapping Integrated Services into RSVP
Looking for a different code? Search another status or error code.