BUG: Optional ADSPEC required in PATH messages

ID: Q195276

The information in this article applies to:

• Microsoft Win32 Software Development Kit (SDK) on the following platform:

      - Windows 98
  

SYMPTOMS

The Generic Quality of Service (GQoS) service provider requires an RSVP PATH message to contain an ADSPEC in order to setup an RSVP session. If the QOS service provider on the receiver receives a PATH message without an ADSPEC, Rsvp.exe (that is, the RSVP engine used by the QOS service provider) hits an error and exits. As a result, no RESV message can be sent and an RSVP session is not established. The QOS service provider restarts Rsvp.exe as needed, and, therefore, a system restart is not required.

According to the RSVP specification (please see, RFC 2205, Section 3.1.3), an ADSPEC is an optional component of a PATH message and RSVP implementations (including those found on routers) are free not to include an ADSPEC. The Microsoft RSVP implementation always includes an ADSPEC in a PATH message.

As a result, a Generic Quality of Service (GQoS) enabled receiver on Windows 98 cannot able to setup an RSVP session with a RSVP enabled sender if one of the following is true:

• The sender relies on an implementation of RSVP that does not include an ADSPEC in a PATH message.
• A router between the sender and receiver does not include an ADSPEC in a PATH message.

RESOLUTION

To inter-operate with the Windows 98 RSVP implementation, you need to ensure that all RSVP implementations on your network include an ADSPEC in PATH messages.

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 Function Specification"

Additional query words:

Keywords          : kbnetwork kbAPI kbGQos kbSDKPlatform kbWinOS98bug kbGrpNet 
Issue type        : kbbug
Solution Type     : kbfix

Last Reviewed: November 6, 1998