1.1 Glossary

This document uses the following terms:

101 Progress Report: A response that indicates the progress of a SIP request.

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

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.

aggregation: A mechanism for reusing objects. The outer object exposes interfaces from one or more inner objects as if they were implemented on the outer object itself. 

Application Sharing Multipoint Control Unit (ASMCU): A Multipoint Control Unit (MCU) that supports application sharing conferencing.

Augmented Backus-Naur Form (ABNF): A modified version of Backus-Naur Form (BNF), commonly used by Internet specifications. ABNF notation balances compactness and simplicity with reasonable representational power. ABNF differs from standard BNF in its definitions and uses of naming rules, repetition, alternatives, order-independence, and value ranges. For more information, see [RFC5234].

call park service (CPS): A server endpoint that allows a user agent to make a call inactive without terminating that call. The call can then be reactivated by the same user agent, by using the same or a different endpoint, or a different user agent. See also parking lot.

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 header: A message header field whose value describes the type of data that is in the body of the message.

Edge Server: A server that is the entry point for all external traffic that both conforms to the Session Initiation Protocol (SIP) and that enters and exits an enterprise. It is typically installed on the perimeter network for an enterprise.

federated partner: An enterprise that is trusted for federation.

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

federation: The ability of a server deployment to interoperate with other servers that were deployed by other enterprises.

fully qualified domain name (FQDN): An unambiguous domain name that gives an absolute location in the Domain Name System's (DNS) hierarchy tree, as defined in [RFC1035] section 3.1 and [RFC2181] section 11.

Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.

INVITE: A Session Initiation Protocol (SIP) method that is used to invite a user or a service to participate in a session.

mailbox: A message store that contains email, calendar items, and other Message objects for a single recipient.

read-only mode: An attribute that indicates that an object cannot be changed or deleted. The object can only be accessed or displayed.

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

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].

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.

SIP response code: A three-digit code in a Session Initiation Protocol (SIP) message, as described in [RFC3261].

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.

tenant: A protocol client or protocol server that accesses a partition in a shared service database.

unauthenticated user: A user who has not received a Session Initiation Protocol (SIP) 200 OK response from a protocol server during registration. With the exception of federated users, all users are unauthenticated initially and are authenticated only after providing the appropriate credentials to the server.

Voice over IP (VoIP): The use of the Internet Protocol (IP) for transmitting voice communications. VoIP delivers digitized audio in packet form and can be used to transmit over intranets, extranets, and the Internet.

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 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.