共用方式為

3.3.1.1.2 Connection

  • 發行項

Connection: A connection is an RPC-level abstraction that denotes the data structures associated with a given RPC transport connection. There is a 1:1 relationship between an RPC transport connection and an RPC connection. The RPC runtime on both the client and server maintains an abstract data handle that is a reference for each TCP/IP connection if the RPC transport is TCP/IP. Each connection MUST belong to exactly one association. Once a connection is tied to an association, a connection cannot change the association that it belongs to. If the transport is NCACN_NP the server maintains a reference to an RPCServerGenericNamedPipeOpen (see [MS-CIFS] section 3.5.4.1)

[C706] uses the term association for what this document refers to as a connection.

The connection ADM element contains the following properties:

  • A list of associated Server Call or Client Call elements.

  • Table of Security Context Handles: A table that contains all of the security context handles  that have been negotiated with the remote client or server and indexed by the security context identifiers currently in use. Lookups in the table are permitted using the auth_context_id field in the sec_trailer (section 2.2.2.11) data structure of the incoming PDU. If Security Context Multiplexing has not been negotiated, as described in section 3.3.1.5.4, the list will contain only a single security context handle.

    Packet integrity verification and/or encryption/decryption is performed, as described in section 3.3.1.5.2.2, using the security context handle value that is contained in each security context row.

    A new row is added to the table when a new security context is built.

  • Connection Multiplex Flag

  • Supports Header Signing Flag: Both the client and server maintain a Boolean value flag that indicates whether the remote party supports header signing as described in section 3.3.1.5.2.2. The default value is FALSE.

  • Transport Handle: The client and server MUST maintain an abstract reference to an underlying transport mechanism instance.

  • Association: The client and server MUST maintain a reference to the association to which the connection is tied.

  • List of Negotiated Presentation Contexts: The list of presentation contexts that have been negotiated for this connection. See sections 3.3.1.5.6 and 3.3.2.4.1.3 for how elements are added to this list.

  • NamedPipe: An RPCServerGenericNamedPipeOpen structure, see [MS-CIFS] section 3.5.4.1.