1.1 Glossary

This document uses the following terms:

back-end client: A component of this protocol that sends the notifications to the server application.

BITS session: An entity collection of data on the server that maintains the state of a single instance of a BITS upload. More details about the session state and actions can be found in section 3.2.1.4.

BITS session ID: A GUID that identifies the BITS session on the server. See section 2.2.1.2 for more details.

BITS-Host-ID: An optional secondary server address. See section 2.2.3.2 for more information.

destination URL: The location to which the request entity is being uploaded. For more information, see [RFC1738].

entity: The payload of a transfer (by analogy to the definition in [RFC2616]).

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

origin server: The URL host name in the destination URL or an IPv6address (as specified in [RFC2373] Appendix B).

proxy: A network node that accepts network traffic originating from one network agent and transmits it to another network agent.

reply URL: The URL of the response entity.

request entity: The server's copy of an entity being uploaded from the client.

response entity: An entity that maintains the response data from the server application. See section 1.3.3 for more information.

server application: The application that listens to the notification URL in [MC-BUP] section 3.2.1.1. This is also called a back-end server.

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.

Universal Naming Convention (UNC): A string format that specifies the location of a resource. For more information, see [MS-DTYP] section 2.2.57.

upload-reply: A type of upload where the server application sends a response entity to the client upon receiving and processing the complete request entity. See section 1.3.3 for more information.

virtual directory: A URL prefix that corresponds to a physical directory on the server.

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.