1.1 Glossary
This document uses the following terms:
authenticated user: A built-in security group specified in [MS-WSO] whose members include all users that can be authenticated by a computer.
ClientVolumeTable: This table has an entry for each of the volumes of the computer on which it runs.
Distributed Link Tracking (DLT): A protocol that enables client applications to track sources that have been sent to remote locations using remote procedure call (RPC) interfaces, and to maintain links to files. It exposes methods that belong to two interfaces, one of which exists on the server (trksvr) and the other on a workstation (trkwks).
DLT: See Distributed Link Tracking (DLT).
domain: A set of users and computers sharing a common namespace and management infrastructure. At least one computer member of the set must act as a domain controller (DC) and host a member list that identifies all members of the domain, as well as optionally hosting the Active Directory service. The domain controller provides authentication of members, creating a unit of trust for its members. Each domain has an identifier that is shared among its members. For more information, see [MS-AUTHSOD] section 1.1.1.5 and [MS-ADTS].
domain controller (DC): The service, running on a server, that implements Active Directory, or the server hosting this service. The service hosts the data store for objects and interoperates with other DCs to ensure that a local change to an object replicates correctly across all DCs. When Active Directory is operating as Active Directory Domain Services (AD DS), the DC contains full NC replicas of the configuration naming context (config NC), schema naming context (schema NC), and one of the domain NCs in its forest. If the AD DS DC is a global catalog server (GC server), it contains partial NC replicas of the remaining domain NCs in its forest. For more information, see [MS-AUTHSOD] section 1.1.1.5.2 and [MS-ADTS]. When Active Directory is operating as Active Directory Lightweight Directory Services (AD LDS), several AD LDS DCs can run on one server. When Active Directory is operating as AD DS, only one AD DS DC can run on one server. However, several AD LDS DCs can coexist with one AD DS DC on one server. The AD LDS DC contains full NC replicas of the config NC and the schema NC in its forest. The domain controller is the server side of Authentication Protocol Domain Support [MS-APDS].
domain controller locator: A function within a domain that provides for location of a domain controller (DC) and the ability to determine certain properties of DCs. For more information, see [MS-ADTS].
dynamic endpoint: A network-specific server address that is requested and assigned at run time. For more information, see [C706].
FileId: The FileLocation of a file at the time it was originally created. A file's FileId never changes.
FileInformation: Information that is maintained about a file, such as its FileId and/or ObjectID.
FileLinkInformation: Information about a file that is necessary to identify and locate that file, including the file's last known Universal Naming Convention (UNC) name, the MachineID of the computer on which the file was last known to be located, the last known FileLocation of the file, and the file's permanent FileID.
FileLocation: A VolumeID with an appended ObjectID, which together represent the location of a file at some point in time, though the file might no longer be there. FileLocation values are stored in droid (CDomainRelativeObjId) data structures.
FileTable: A table (with rows uniquely identified by a FileLocation or FileID) that contains the following fields: [PreviousFileLocation, FileLocation, FileID, RefreshTime]. For more information [MS-DLTM] see section 3.1.1. Maps a FileLocation or FileID to a current FileLocation.
globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).
Interface Definition Language (IDL): The International Standards Organization (ISO) standard language for specifying the interface for remote procedure calls. For more information, see [C706] section 4.
MachineID: A unique identifier that represents the identity of a computer.
MoveNotificationCursor: A value that indicates the next entry in the MoveNotificationList that is to be sent to the server in a MOVE_NOTIFICATION message. See section 3.2.1 for more information.
MoveNotificationList: A list of records with information about files that have been moved from a volume on this machine. See section 3.2.1 for more information.
MoveNotificationVolumeCursor: A value that indicates that a sequence of MOVE_NOTIFICATION messages is in progress, and indicates the current volume (from the ClientVolumeTable) for which notifications are being sent. See section 3.2.5.6 for more information.
ObjectID: A unique identifier that represents the identity of a file within a file system volume. For more information, see [MS-DLTM].
PreviousFileLocation: The FileLocation of a file before it was moved.
principal name: The computer or user name that is maintained and authenticated by the Active Directory directory service.
remote procedure call (RPC): A communication protocol used primarily between client and server. The term has three definitions that are often used interchangeably: a runtime environment providing for communication facilities between computers (the RPC runtime); a set of request-and-response message exchanges between computers (the RPC exchange); and the single message from an RPC exchange (the RPC message). For more information, see [C706].
RequestMachine: The MachineID of the computer that is the client calling the LnkSvrMessage method.
RPC protocol sequence: A character string that represents a valid combination of a remote procedure call (RPC) protocol, a network layer protocol, and a transport layer protocol, as described in [C706] and [MS-RPCE].
security provider: A pluggable security module that is specified by the protocol layer above the remote procedure call (RPC) layer, and will cause the RPC layer to use this module to secure messages in a communication session with the server. The security provider is sometimes referred to as an authentication service. For more information, see [C706] and [MS-RPCE].
ServerVolumeTable: A table (with rows uniquely identified by a VolumeID) that contains the following fields: [VolumeID, VolumeSequenceNumber, VolumeSecret, VolumeOwner, RefreshTime]. For more information see section 3.1.1.
Subrequest: A request within a SYNC_VOLUMES request. For details on requests, see section 3.1.4.
Universal Naming Convention (UNC): A string format that specifies the location of a resource. For more information, see [MS-DTYP] section 2.2.57.
universally unique identifier (UUID): A 128-bit value. UUIDs can be used for multiple purposes, from tagging objects with an extremely short lifetime, to reliably identifying very persistent objects in cross-process communication such as client and server interfaces, manager entry-point vectors, and RPC objects. UUIDs are highly likely to be unique. UUIDs are also known as globally unique identifiers (GUIDs) and these terms are used interchangeably in the Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the UUID. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the UUID.
user principal name (UPN): A user account name (sometimes referred to as the user logon name) and a domain name that identifies the domain in which the user account is located. This is the standard usage for logging on to a Windows domain. The format is: someone@example.com (in the form of an email address). In Active Directory, the userPrincipalName attribute of the account object, as described in [MS-ADTS].
volume: A group of one or more partitions that forms a logical region of storage and the basis for a file system. A volume is an area on a storage device that is managed by the file system as a discrete logical storage unit. A partition contains at least one volume, and a volume can exist on one or more partitions.
VolumeFileTable: A table that contains FileInformation entries, and is maintained for each volume in the ClientVolumeTable. Like the ClientVolumeTable, this table MUST be stored on the volume itself. The VolumeFileTable has an entry for each file on the volume that is to be tracked with this protocol. Each entry has a CrossVolumeMoveFlag value, which MUST initially be set to zero. For more information see section 3.2.1.
VolumeID: A unique identifier that represents the identity of a file system volume.
VolumeInformation: A table that maintains volume information for each volume in the ClientVolumeTable.
VolumeOwner: A MachineID that is considered to be the owner of a VolumeID. A VolumeID can only have one VolumeOwner. For more information, see [MS-DLTM].
VolumeSecret: A value that is used to establish a VolumeOwner. For more information, see [MS-DLTM].
VolumeSequenceNumber: An integer value used to track the sequence of move notification messages received by the protocol server. See [MS-DLTM] section 2.2.2 for more information.
workstation: A terminal or desktop computer in a network that is used to run applications and is connected to a server from which it obtains data shared with other computers.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.