1.1 Glossary
This document uses the following terms:
big-endian: Multiple-byte values that are byte-ordered with the most significant byte stored in the memory location with the lowest address.
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).
little-endian: Multiple-byte values that are byte-ordered with the least significant byte stored in the memory location with the lowest address.
media: Compressed audio, video, and text data that is used by the client to play a presentation.
playlist: One or more content items that are streamed sequentially.
proxy: A network node that accepts network traffic originating from one network agent and transmits it to another network agent.
Real-Time Streaming Protocol (RTSP): A protocol used for transferring real-time multimedia data (for example, audio and video) between a server and a client, as specified in [RFC2326]. It is a streaming protocol; this means that RTSP attempts to facilitate scenarios in which the multimedia data is being simultaneously transferred and rendered (that is, video is displayed and audio is played).
session: A collection of multimedia senders and receivers and the data streams that flow between them. A multimedia conference is an example of a multimedia session.
stub: Used as specified in [C706] section 2.1.2.2. A stub that is used on the client is called a "client stub", and a stub that is used on the server is called a "server stub".
tag: The format of all Device Services Lightweight Remoting Protocol ([MS-DSLR]) messages includes the size of the payload, number of children, and the tag payload itself.
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.