1.3 Overview

The .Net Message Framing MSMQ Binding Protocol specifies how the mechanism described in [MC-NMF] for framing messages over any transport protocol can be applied over Message Queue (MSMQ). This protocol specification also includes how to indicate the use of .NET Message Framing over MSMQ as a SOAP transport in Web Services Description Language (WSDL). Finally, the protocol details how the protocol behavior changes if any of the set of policy assertions (as defined in section 1.1 of [MS-WSPOL]) are set on an endpoint. This document specifies the following policy assertions:

  • MSMQ Best-Effort

    The MSMQ Best-Effort policy assertion indicates that a Web service endpoint requires messages to be delivered in a best-effort manner, which does not guarantee that the message will be delivered only one time.

  • MSMQ Session

    The MSMQ Session policy assertion indicates that a Web service endpoint requires multiple envelope records to be sent within a single message.

  • MSMQ Volatile

    The MSMQ Volatile policy assertion indicates that a Web service endpoint requires the use of express messages; otherwise, recoverable messages are required.

  • MSMQ Authenticated

    The MSMQ Authenticated policy assertion indicates that a Web service endpoint requires MSMQ messages to be authenticated, as described in section 3.1.5.8.3 of [MS-MQQB].

  • MSMQ Windows Domain

    The MSMQ Windows Domain policy assertion indicates that a Web service endpoint requires authentication to be performed using the sender's security identifier (SID), as defined in [MS-DTYP] section 2.4.2. If this policy assertion is not set, the service endpoint requires authentication to be performed using X.509 certificates [RFC3280].

These assertions are used to ensure the client is using the Web service through the binding as intended.

The .Net Message Framing MSMQ Binding Protocol makes use of MSMQ protocols to set the proper message attributes in order to conform with policy assertions set by the Web service.