3.2.3.1 Abstract Data Model

This section describes a conceptual model of possible data organization that an implementation might maintain to participate in this protocol. The described organization explains how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

An inbound proxy maintains several abstract protocol variables and data structures:

• A Virtual Connection Cookie Table as described in the common virtual connection elements in the preceding paragraphs.

• For each Virtual Connection in the Virtual Connection Cookie Table, the common Virtual Connection elements as described in the preceding paragraphs.

• For each Virtual Connection, an IN Channel which consists of the ReceivingChannel elements as described in the common section.

• For each Virtual Connection, an OUT Channel which consists of the SendingChannel elements as described in the common section.

• A set of Inbound Proxy-specific data elements as described in the following list.

  • KeepAlive interval (section 3.2.3.1.4)

  • Resource type UUID (section 3.2.3.1.5)

  • Session UUID (section 3.2.3.1.6)