3.1.1.1 Connection Object

A Connection object MUST contain the following data elements:

  • Connection ID: An unsigned 32-bit integer that identifies the connection. The Connection ID MUST be unique within a table. Note that a given Connection object is allowed to have the same Connection ID as another Connection object (related to the same Session object), so long as the other Connection object is in the other connection table. For example, the first connection is in the Incoming Connection Table and the second connection is in the Outgoing Connection Table, or vice versa.

  • Accepted: A Boolean value, indicating whether the connection was accepted or rejected by the higher-layer protocol. This value is initially false.

ยง Connection Type: An unsigned 32-bit integer that identifies the set of messages defined by a higher-level protocol sent over the connection. Higher-level messages are grouped based on the specific set of state changes they produce, and that grouping is identified by connection type.

  • Incoming Message Notification Interface: The local event of a higher-layer that is used by this protocol to notify a higher-layer protocol of incoming message events, as specified in section 3.1.7.4.

Note It is possible to implement the conceptual data by using a variety of techniques. An implementation is at liberty to implement such data in any way it pleases.