1.1 Glossary

This document uses the following terms:

200 OK: A response to indicate that the request has succeeded.

403 Forbidden: A response that indicates that a protocol server understood but denies a request.

access control list (ACL): A list of access control entries (ACEs) that collectively describe the security rules for authorizing access to some resource; for example, an object or set of objects.

Active Directory: The Windows implementation of a general-purpose directory service, which uses LDAP as its primary access protocol. Active Directory stores information about a variety of objects in the network such as user accounts, computer accounts, groups, and all related credential information used by Kerberos [MS-KILE]. Active Directory is either deployed as Active Directory Domain Services (AD DS) or Active Directory Lightweight Directory Services (AD LDS), which are both described in [MS-ADOD]: Active Directory Protocols Overview.

activity: A type of event, such as "In a meeting," that provides information about the availability and status of a presentity.

aggregation: An operation in which multiple instances of one or more dependent categories, which are typically published by different Session Initiation Protocol (SIP) clients of the same user, are processed to produce an instance of a category. After this category instance is created, it can be published to multiple containers and notified to subscribers in the same way as any other category.

availability: A numerical value that indicates whether a user can be interrupted for communication. The higher the number, the less available the user.

base64 encoding: A binary-to-text encoding scheme whereby an arbitrary sequence of bytes is converted to a sequence of printable ASCII characters, as described in [RFC4648].

Best Effort NOTIFY (BENOTIFY): A Session Initiation Protocol (SIP) method that is used to send notifications to a subscriber, as described in [MS-SIP]. Unlike the NOTIFY method, the BENOTIFY method does not require the recipient of the request to send a SIP response.

bot: A structured HTML comment that is processed by a front-end web server when the containing document is opened by or saved to the server. Also referred to as web bot.

category: An enhanced presence concept that is used by a Session Initiation Protocol (SIP) client to publish or subscribe to presence information. A category enables basic identification of the data that is being published; it implies an agreed-upon schema for interpreting the data. A category name identifies a contract between a publisher and a subscriber.

category subscriber: A SIP protocol client that sent a category SUBSCRIBE request.

child element: In an XML document, an element that is subordinate to and is contained by another element, which is referred to as the parent element.

conference: A Real-Time Transport Protocol (RTP) session that includes more than one participant.

container: A data model that is used to store published presence information and a list of subscribers who are permitted to view that information. It enables a publisher to publish different data values of the same category and instance, which enables different subscribers to see different values.

content type: A named and uniquely identifiable collection of settings and fields that store metadata for individual items in a SharePoint list. One or more content types can be associated with a list, which restricts the contents to items of those types.

Content-Type header: A message header field whose value describes the type of data that is in the body of the message.

Coordinated Universal Time (UTC): A high-precision atomic time standard that approximately tracks Universal Time (UT). It is the basis for legal, civil time all over the Earth. Time zones around the world are expressed as positive and negative offsets from UTC. In this role, it is also referred to as Zulu time (Z) and Greenwich Mean Time (GMT). In these specifications, all references to UTC refer to the time at UTC-0 (or GMT).

cyclic redundancy check (CRC): An algorithm used to produce a checksum (a small, fixed number of bits) against a block of data, such as a packet of network traffic or a block of a computer file. The CRC is a broad class of functions used to detect errors after transmission or storage. A CRC is designed to catch random errors, as opposed to intentional errors. If errors might be introduced by a motivated and intelligent adversary, a cryptographic hash function has to be used instead.

delegate: A user or resource that has permissions to act on behalf of another user or resource.

delegator: A user or resource for which another user or resource has permission to act on its behalf.

deployment: A collection of protocol clients and protocol servers that belong to the same enterprise.

dialog: A peer-to-peer Session Initiation Protocol (SIP) relationship that exists between two user agents and persists for a period of time. A dialog is established by SIP messages, such as a 2xx response to an INVITE request, and is identified by a call identifier, a local tag, and a remote tag.

directory service (DS): A service that stores and organizes information about a computer network's users and network shares, and that allows network administrators to manage users' access to the shares. See also Active Directory.

domain: A set of users and computers sharing a common namespace and management infrastructure. At least one computer member of the set has to 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].

endpoint: A device that is connected to a computer network.

enhanced presence: A presence model that uses categories to specify presence information and uses containers to authorize subscribers. This model includes Session Initiation Protocol (SIP) extensions for publishing and subscribing to presence information and for specifying access control lists for subscribers. It uses the msrtc-event-categories presence document format.

event package: A specification that defines a set of state information to be reported by a notifying Session Initiation Protocol (SIP) client to a subscriber. An event package also defines further syntax and semantics based on the framework that is required to convey such state information.

federated user: An external user who possesses valid credentials with a federated partner and who therefore is treated as authenticated by a protocol server.

Globally Routable User Agent URI (GRUU): A URI that identifies a user agent and is globally routable. A URI possesses a GRUU property if it is useable by any user agent client (UAC) that is connected to the Internet, routable to a specific user agent instance, and long-lived.

hash: A fixed-size result that is obtained by applying a one-way mathematical function, which is sometimes referred to as a hash algorithm, to an arbitrary amount of data. If the input data changes, the hash also changes. The hash can be used in many operations, including authentication and digital signing.

instance: A unique publication of data for a category. It enables a publisher to publish data for the same category multiple times. An example is a publisher who uses two different endpoints to publish data. These endpoints can publish the same category. However, each endpoint requires a different instance number to be considered a distinct publication by the server. An instance number is provided by the publishing client.

Lightweight Directory Access Protocol (LDAP): The primary access protocol for Active Directory. Lightweight Directory Access Protocol (LDAP) is an industry-standard protocol, established by the Internet Engineering Task Force (IETF), which allows users to query and update information in a directory service (DS), as described in [MS-ADTS]. The Lightweight Directory Access Protocol can be either version 2 [RFC1777] or version 3 [RFC3377].

ms-diagnostics header: A header that is added to a Session Initiation Protocol (SIP) response, BYE request, or CANCEL request to convey troubleshooting information.

MSRTC: An abbreviation for Microsoft Real-Time Communications.

Multipurpose Internet Mail Extensions (MIME): A set of extensions that redefines and expands support for various types of content in email messages, as described in [RFC2045], [RFC2046], and [RFC2047].

notification: A process in which a subscribing Session Initiation Protocol (SIP) client is notified of the state of a subscribed resource by sending a NOTIFY message to the subscriber.

notify: The process of sharing presence information with subscribed client devices by using the Wide Area Network Device Presence Protocol (WAN DPP).

participant: A user who is participating in a conference or peer-to-peer call, or the object that is used to represent that user.

persistent SUBSCRIBE: A SUBSCRIBE request that is used to obtain updates when presence information changes for a presentity. The subscription does not expire until the subscribing client endpoint registration on a Session Initiation Protocol (SIP) server expires. See also polling SUBSCRIBE.

polling SUBSCRIBE: A SUBSCRIBE request that is used to obtain a one-time snapshot of presence information for a presentity. It has a value of "0" (zero) in the Expires header field and does not have any tag in the To header field.

Presence Information Data Format (PIDF): A common data format defined in [RFC3863] to exchange presence information.

presentity: An entity that provides presence information to a presence service.

public cloud (publicCloud) user: An external user who possesses valid credentials with a public, federated service, such as AOL, MSN, or Yahoo, and therefore is treated as authenticated by a server.

public switched telephone network (PSTN): Public switched telephone network is the voice-oriented public switched telephone network. It is circuit-switched, as opposed to the packet-switched networks.

publish: A SERVICE request that specifies which category instances to publish for a presentity.

publisher: A SIP protocol client that is making a publish request.

REGISTER: A Session Initiation Protocol (SIP) method that is used by an SIP client to register the client address with an SIP server.

same enterprise (sameEnterprise) user: An internal user who belongs to the same organization as another user who is sharing a communication session and is authenticated within that organization.

self SUBSCRIBE: A SUBSCRIBE request that is used by a publisher to be notified of changes to its own data. It is possible to subscribe to three different sets of data: categories, containers, and subscribers.

self subscriber: A SIP protocol client that is making a subscribe request for self-published category information.

server: A replicating machine that sends replicated files to a partner (client). The term "server" refers to the machine acting in response to requests from partners that want to receive replicated files.

service: A process or agent that is available on the network, offering resources or services for clients. Examples of services include file servers, web servers, and so on.

Session Initiation Protocol (SIP): An application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. SIP is defined in [RFC3261].

Simple Mail Transfer Protocol (SMTP): A member of the TCP/IP suite of protocols that is used to transport Internet messages, as described in [RFC5321].

SIP message: The data that is exchanged between Session Initiation Protocol (SIP) elements as part of the protocol. An SIP message is either a request or a response.

SIP protocol client: A network client that sends Session Initiation Protocol (SIP) requests and receives SIP responses. An SIP client does not necessarily interact directly with a human user. User agent clients (UACs) and proxies are SIP clients.

SIP request: A Session Initiation Protocol (SIP) message that is sent from a user agent client (UAC) to a user agent server (UAS) to call a specific operation.

SIP response: A Session Initiation Protocol (SIP) message that is sent from a user agent server (UAS) to a user agent client (UAC) to indicate the status of a request from the UAC to the UAS.

SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].

subscribe: The process of registering to receive updates about presence information for client devices. The updates are delivered by using Wide Area Network Device Presence Protocol (WAN DPP).

subscriber: A Session Initiation Protocol (SIP) client that is making a SUBSCRIBE request.

subscription: The result of a SUBSCRIBE request from a Session Initiation Protocol (SIP) element.

survivable mode: A mode that enables a protocol client to access basic voice services if some server or network resources are unavailable.

token: A word in an item or a search query that translates into a meaningful word or number in written text. A token is the smallest textual unit that can be matched in a search query. Examples include "cat", "AB14", or "42".

Transport Layer Security (TLS): A security protocol that supports confidentiality and integrity of messages in client and server applications communicating over open networks. TLS supports server and, optionally, client authentication by using X.509 certificates (as specified in [X509]). TLS is standardized in the IETF TLS working group.

tuple: An ordered grouping of members from different dimensions or hierarchies. A single member is a special case of a tuple and can be used as an expression. Every hierarchy does not have to be represented in a tuple.

Unified Communications: A system that integrates platforms for communications including email, voice mail, telephony, instant messaging, and voice and video conferencing.

Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].

Uniform Resource Locator (URL): A string of characters in a standardized format that identifies a document or resource on the World Wide Web. The format is as specified in [RFC1738].

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] has to be used for generating the UUID.

user agent client (UAC): A logical entity that creates a new request, and then uses the client transaction state machinery to send it. The role of UAC lasts only for the duration of that transaction. In other words, if a piece of software initiates a request, it acts as a UAC for the duration of that transaction. If it receives a request later, it assumes the role of a user agent server (UAS) for the processing of that transaction.

user agent server (UAS): A logical entity that generates a response to a Session Initiation Protocol (SIP) request. The response either accepts, rejects, or redirects the request. The role of the UAS lasts only for the duration of that transaction. If a process responds to a request, it acts as a UAS for that transaction. If it initiates a request later, it assumes the role of a user agent client (UAC) for that transaction.

website: A group of related webpages that is hosted by a server on the World Wide Web or an intranet. Each website has its own entry points, metadata, administration settings, and workflows. Also referred to as site.

XML document: A document object that is well formed, as described in [XML10/5], and might be valid. An XML document has a logical structure that is composed of declarations, elements, comments, character references, and processing instructions. It also has a physical structure that is composed of entities, starting with the root, or document, entity.

XML element: An XML structure that typically consists of a start tag, an end tag, and the information between those tags. Elements can have attributes and can contain other elements.

XML schema: A description of a type of XML document that is typically expressed in terms of constraints on the structure and content of documents of that type, in addition to the basic syntax constraints that are imposed by XML itself. An XML schema provides a view of a document type at a relatively high level of abstraction.

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.