3.6.1 Abstract Data Model

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of 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.

Firewall State: The set of firewall rules currently configured and enabled on the server. A firewall rule can be associated with a group of firewall rules that is identifiable by name. There can be multiple groups of firewall rules configured in the Firewall State of a server. A firewall rule is also associated with a network adapter such that for each network adapter on the server, it can be determined which firewall rules and/or groups of firewall rules are associated with that adapter. The data type of a firewall rule and the initialization of a firewall rule are implementation-specific. A server typically defines and initializes a firewall rule as specified for FW_RULE in [MS-FASP].

Network Adapter Configuration: Information about the set of network adapters on the server and their associated settings and configuration. In this protocol, the Network Adapter Configuration is defined as the data type ADAPTERLIST2 (section 2.2.16) <20>. The initialization and manipulation of Network Adapter Configuration is implementation-specific.

Initialization State: Indicates whether the server has been initialized and can fulfill methods in the interface. The value can be set to either TRUE or FALSE and is initially set to False.

Route: A Route<21> represents a potential communication path from the server to a different network host. How the communication is manifested in actual network traffic is implementation-specific. A Route contains of the following data elements:

LocalVirtualIP: Corresponds to the localVirtualIP field of an ADD_ROUTES_REQUEST structure as specified in section 2.2.19.

RemoteVirtualIP: Corresponds to the remoteVirtualIP field of a NODE_ROUTE_INFO (section 2.2.18) structure as specified in section 2.2.18.

LocalUnicastIP: Corresponds to a single element of the localUnicastIPs field of a NODE_ROUTE_INFO structure.

RemoteUnicastIP: Corresponds to a single element of the remoteUnicastIPs field of a NODE_ROUTE_INFO structure.

LossAndState: A ROUTE_LOSS_AND_STATE data structure, as specified in section 2.2.21.

Index: Corresponds to a single element of the indices field of a NODE_ROUTE_INFO structure.

Route Collection: A collection of Routes. The initial contents of Route Collection is empty.

Route Monitoring State: Indicates whether the server is monitoring Route elements in Route Collection.