Knowledge Base

BUG: Guaranteed Service Type Not Set Correctly in RESV Message

Article ID: 195275

Article Last Modified on 7/11/2005

APPLIES TO

This article was previously published under Q195275

SYMPTOMS

A Generic Quality of Service (GQoS) application that specifies Guaranteed Service in the flowspec structure results in the QOS service provider on the receiving side to emit a malformed RESV RSVP message on the wire. In particular the RSPEC portion of the flowspec object (please see RFC 2205, section 1.2) will be incorrect. In addition to the RSPEC being erroneous, some RSVP-enabled routers might have difficulty handling this erroneous data.

RESOLUTION

To work around this problem, do not specify Guaranteed Service (that is, SERVICETYPE_GUARANTEED) in the ServiceType member of the flowspec structure. To obtain better than Best-effort service, you should specify Controlled Load (that is, SERVICETYPE_CONTROLLEDLOAD) in the ServiceType member of the flowspec structure.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

REFERENCES

RFC 2205, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"

Keywords: kbbug kbfix kbgqos kbwinsock kbapi kbnetwork KB195275


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.