3.5.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.
Target server name: A string of Unicode characters. The server name applies to the machine that the RDG server connects to.<55>
Client Machine name: A string of Unicode characters that cannot exceed 513 bytes,<56> including the terminating null character. The Client Machine name refers to the machine that runs the RDG client. It is possible for the Client Machine name to be the same as the server name (in value) if the client and the server run on the same physical machine.<57>
Tunnel id: An unsigned long representing the tunnel identifier for tracking purposes on the RDG server. It MAY be used by the RDG client to help the RDG server administrator troubleshoot connection issues.
Channel id: An unsigned long representing the channel identifier for tracking purposes on the RDG server. It MAY be used by the RDG client to help the RDG server administrator troubleshoot connection issues.
CertChainData: A string of variable data returned by the RDG server representing the certificate chain used by the RDG server for the HTTPS communication between RDG client and RDG server. The RDG client MAY use this data to verify the identity of the RDG server before sending sensitive data, such as the health information of the RDG client machine.
Nonce: A unique GUID returned by the RDG server to identify the current connection. The RDG client sends this GUID to the RDG server if it sends the statement of health (SoH), as specified in section 2.2.9.2.1.4.
Idle Timeout Value: An unsigned long value that specifies connection idle time in minutes before the connection is torn down.
DeviceRedirection: A TSG_REDIRECTION_FLAGS (section 2.2.9.2.1.5.2) structure that specifies the device redirection settings that MUST be enforced by the client.
UDPAuthCookie: A signed and encoded byte BLOB containing an AUTHN_COOKIE_DATA structure.
Negotiated Capabilities: A ULONG bitmask value representing the negotiated capabilities between the RDG client and the RDG server. It contains zero or more of the following values:
-
NAP Capability Value