Partager via

3.1.4.3 Using the Negotiated Protocol Version

  • Article

Once a protocol version is negotiated, the session partners SHOULD use in their communication only the protocol elements that are either required or optional for that version (see section 2.2.1 for a definition of version-required and version-optional elements), as follows:

  • When a partner makes a connection request, it SHOULD use only a connection type that is either required or optional for the negotiated protocol version. If the connection type is optional for the negotiated protocol version, it MUST handle the MTAG_CONNECTION_REQ_DENIED ([MS-CMP] section 2.2.5) response and return the failure result to the higher business layer.<18>

  • When a partner receives a connection request, it MUST accept as valid only a connection type that is either required or optional for the negotiated protocol version. Invalid connections MUST be rejected, as specified in [MS-CMP] section 2.2.5.

  • When a partner sends a message over an established connection, it SHOULD use only message types and formats that are supported by the negotiated protocol version in the context of the connection type of the respective connection.<19>

  • When a partner receives a message over an established connection, it SHOULD accept as valid only message types and formats that are supported by the negotiated protocol version in the context of the connection type of the respective connection. An invalid message MUST be rejected, as specified in section 3.1.6.