3.3.2.4.1.3 Build Security/Presentation Context

A client cannot execute a remote procedure method call on a connection if there is no presentation context for the interface and transfer syntaxes used by the call in the List of Negotiated Presentation Contexts. If such a presentation context already exists, the client can use it. If not, the client follows the steps specified in section 3.3.1.5.6 and in [C706] sections 9, 11, and 12 to create a presentation context.

If the remote procedure method call uses security, the client MUST attempt to find or create a security context for that call. The steps to create a security context are specified in section 3.3.1.5.2.<111>

The client SHOULD try to reuse existing presentation contexts and security contexts that are present on the connection. If the client needs to negotiate both a new presentation context and a new security context on the connection, the client also SHOULD do so with a single exchange of bind/bind_ack or alter_context/alter_context_resp, which might take multiple PDUs, where the PDUs carry both information necessary for building the security context and information necessary for building the presentation context. The new presentation context SHOULD be added to the List of Negotiated Presentation Contexts in the connection, and, if not there already, to the Table of Presentation Contexts in the association to which the connection is bound.