Technical Documents
This section provides information about the technical specifications that are contained in the Windows Protocols documentation set.
For preview or pre-release versions of the technical specifications, see Preview Documents.
Note The inter-document links in a PDF version of a technical specification document are functional only if all the cross-referenced documents are saved to the same local directory folder. An error message appears if you click a link that references a PDF document that is not located in the same folder (when viewing via your local hard drive) or is part of a different download (when viewing online). To save a complete set of PDF files to the same folder, download the Windows Protocols .zip file. This is a large file and can take a few minutes to download.
|
Specification |
Description |
|---|---|
|
[MC-BUP]: Background Intelligent Transfer Service (BITS) Upload Protocol |
Specifies the Background Intelligent Transfer Service (BITS) Upload Protocol, which is used to upload large entities from a client to a server over networks with frequent disconnections, and to send notifications from the server to a server application about the availability of the uploaded entities. |
|
Specifies the Server Cluster: Configuration (ClusCfg) Protocol, which enables users to restore a node that is no longer a configured member of a failover cluster back to its pre-cluster installation state. |
|
|
[MC-COMQC]: Component Object Model Plus (COM+) Queued Components Protocol |
Specifies the Component Object Model Plus (COM+) Queued Components Protocol, which is used for persisting method calls made on COM+ objects in such a way that they can later be played back and executed. |
|
Specifies the Conceptual Schema Definition File Format, which defines some well-known primitive types, such as Edm.String, that are used as the building blocks for structural types like Entity Types and Complex Types. |
|
|
[MC-DPL4CS]: DirectPlay 4 Protocol: Core and Service Providers |
Specifies DirectPlay 4 Protocol: Core and Service Providers. This protocol enables the implementation of functions to enumerate hosted game sessions and players, to add and remove game players, and to interchange data between game instances. |
|
Specifies the DirectPlay 4 Protocol: Reliable, which describes functionality related to the reliable delivery of DirectPlay 4 messages and provides throttling for applications that use DirectPlay 4. |
|
|
[MC-DPL8CS]: DirectPlay 8 Protocol: Core and Service Providers |
Specifies the DirectPlay 8 Protocol: Core and Service Providers, which creates and manages game sessions over existing datagram protocols such as UDP. |
|
Specifies the DirectPlay 8 Protocol: Reliable, which provides mixed, not reliable, and reliable messages over existing datagram protocols such as the User Datagram Protocol (UDP). |
|
|
[MC-DPLHP]: DirectPlay 8 Protocol: Host and Port Enumeration |
Specifies the DirectPlay 8 Protocol: Host and Port Enumeration, which enables a DirectPlay 8 client application to discover one or more DirectPlay 8 server applications. |
|
Specifies the DirectPlay 8 Protocol: NAT Locator, which provides extensions to the DirectPlay 8 Core and Service Providers Protocol (as specified in [MC-DPL8CS]) to improve Network Address Translation (NAT) support. |
|
|
Specifies the DirectPlay Voice Protocol, which is used to provide voice communications for applications that use the DirectPlay protocol to communicate. |
|
|
Specifies the Distributed Routing Table (DRT) Version 1.0 protocol, which is used to maintain a network of nodes (referred to as a cloud) and to resolve keys to their endpoint information when requested by a node within the cloud. |
|
|
Specifies the MSDTC Connection Manager: OleTx Transaction Protocol, which describes the extensions that support XA [XOPEN-DTP]-compliant software components in an OleTx distributed transaction processing environment. |
|
|
[MC-EDMX]: Entity Data Model for Data Services Packaging Format |
Specifies the Entity Data Model for Data Services Packaging Format (EDMX), which is an XML-based file format that serves as the packaging format for the service metadata of a data service. |
|
[MC-IISA]: Internet Information Services (IIS) Application Host COM Protocol |
Specifies the Internet Information Services (IIS) Application Host COM Protocol, which provides read/write access to administrative configuration data that is located on a remote server. |
|
Specifies the Message Queuing (MSMQ): ActiveX Client Protocol, which is a collection of Distributed Component Object Model (DCOM) [MS-DCOM] interfaces that expose message queuing functionality for use by client applications. |
|
|
[MC-MQSRM]: Message Queuing (MSMQ): SOAP Reliable Messaging Protocol (SRMP) |
Specifies the Message Queuing (MSMQ): SOAP Reliable Messaging Protocol (SRMP), which defines a mechanism for reliably transferring messages between two message queues that are located on two different hosts. |
|
Specifies the SOAP data structure for the .NET Binary Format for XML. This structure uses the XML data structure format [MC-NBFX], but specifies the set of strings to which a producer and consumer can refer. |
|
|
Specifies the SOAP extension for the .NET Binary Format for XML. This SOAP extension is a new format built by extending the format specified in [MC-NBFS]; it provides a context under which strings may be transmitted once and referred to by subsequent documents in order to reduce the size of the documents. |
|
|
Specifies the XML data structure for the .NET Binary Format for XML. This format can represent many XML documents, as specified in [XML1.0]. The purpose of the format is to reduce the processing costs associated with XML documents by encoding an XML document in fewer bytes than the same document encoded in UTF-8, as specified in [RFC2279]. |
|
|
Specifies the .NET Context Exchange Protocol, which defines a message syntax for identifying context that is shared between a client and a server, and a protocol for establishing that context. |
|
|
Specifies the .NET Message Framing Protocol, which defines a mechanism for framing messages. While this is primarily aimed at framing SOAP messages, the protocol can be used to frame other message types as well. |
|
|
Specifies the .NET Packet Routing Protocol, which defines a SOAP message header to indicate that a message can safely be treated as a packet or datagram. |
|
|
Specifies the Peer Channel Protocol, which is used for broadcasting messages over a virtual network of cooperating nodes. |
|
|
Specifies the Peer Channel Custom Resolver Protocol, which is used for storage and retrieval of endpoint information of clients with access to a known service. |
|
|
Specifies the Session Multiplex Protocol, which provides session management capabilities between a database client and a database server. This protocol enables multiple logical client connections to connect to a single server over a single physical connection. |
|
|
Specifies the SQL Server Resolution Protocol, which facilitates connectivity to a database server. |
|
|
Specifies the Automatic Bluetooth Pairing Protocol, which facilitates the establishment of a secure, trusted Bluetooth pairing relationship between two devices without requiring any user interaction at the time of pairing. |
|
|
Specifies the Active Directory Schema Attributes A-L, which contains a partial list of the objects that exist in the Active Directory schema (attributes beginning with A - L). |
|
|
Specifies the Active Directory Schema Attributes M, which contains a partial list of the objects that exist in the Active Directory schema (attributes beginning with M). |
|
|
Specifies the Active Directory Schema Attributes N-Z, which contains a partial list of the objects that exist in the Active Directory schema (attributes beginning with N through Z). |
|
|
[MS-ADCAP]: Active Directory Web Services: Custom Action Protocol |
Specifies the Active Directory Web Services: Custom Action Protocol, used for directory access in identity management and topology management. This protocol enables the transition of client applications that are currently using non-web services protocols for managing information held in directory services to instead use Web services protocols. |
|
[MS-ADDM]: Active Directory Web Services: Data Model and Common Elements |
Specifies the Active Directory Web Services: Data Model and Common Elements. This protocol contains an XML data model and other protocol components (such as the definition of an XPath 1.0-derived selection language) that are used in various protocols that belong to the set of Active Directory Web Services protocols. |
|
[MS-ADFSOAL]: Active Directory Federation Services OAuth Authorization Code Lookup Protocol |
Specifies the Active Directory Federation Services OAuth Authorization Code Lookup Protocol, which is used to find the issuing server of an access token for an OAuth authorization code. |
|
[MS-ADFSPIP]: Active Directory Federation Services and Proxy Integration Protocol |
Specifies the Active Directory Federation Services Proxy and Web Application Proxy Integration Protocol. This protocol integrates Active Directory Federation Services with an authentication and application proxy to enable access to services located inside the boundaries of the corporate network for clients that are located outside of that boundary. |
|
[MS-ADFSPP]: Active Directory Federation Service (AD FS) Proxy Protocol |
Specifies the Federation Service Proxy Protocol, which is used by a security token service (STS) proxy to obtain configuration data about an STS in order to assist users in selecting an acceptable security realm from which to obtain a security token. |
|
[MS-ADFSWAP]: Active Directory Federation Service (AD FS) Web Agent Protocol |
Specifies the Federation Service Web Agent Protocol, which is used by a Web service (WS) resource to obtain configuration data about a security token service (STS) in order to validate tokens from that STS using the protocol defined in [MS-MWBF]. |
|
[MS-ADLS]: Active Directory Lightweight Directory Services Schema |
Specifies the Active Directory Lightweight Directory Services Schema, which contains a list of the objects that exist in the Active Directory Lightweight Directory Services schema. |
|
Specifies the Active Directory Schema Classes, which contains a partial list of objects that exist in the Active Directory schema. |
|
|
Specifies the Remote Data Services (RDS) Transport Protocol, an HTTP request/response protocol that facilitates remote method definition and invocation, method definitions for executing database commands and for synchronizing database results, and definition of a record format for encoding of database results. |
|
|
Specifies the core functionality of Active Directory. Active Directory extends and provides variations of the Lightweight Directory Access Protocol (LDAP). |
|
|
Specifies the Authenticated Internet Protocol. This protocol supports a more generalized authentication exchange than the Internet Key Exchange Protocol and provides the optimizations in key exchange and policy discoverability. |
|
|
Specifies Authentication Protocol Domain Support, which is the communication process between a server and a domain controller that uses Netlogon interfaces to complete an authentication sequence. |
|
|
Specifies the ASP.NET State Server Protocol, which is a contract for transmitting session state data between a client and a state server. |
|
|
Specifies the Authorization Manager (AzMan) Policy File Format, which defines the XML structure of AzMan policy files. These files are used by the Microsoft Management Console (MMC) AzMan snap-in and the authorization manager runtime. |
|
|
[MS-BDSRR]: Business Document Scanning: Scan Repository Capabilities and Status Retrieval Protocol |
Specifies the Business Document Scanning: Scan Repository Capabilities and Status Retrieval Protocol, which is used to query a server for the capabilities and status of the scan repository. |
|
Specifies Border Gateway Protocol (BGP) Profile a dynamic routing protocol that automatically learns routes between sites that are connected using site-to-site VPN connections and clarifies what portions of [RFC1997] and [RFC4271] are not supported. |
|
|
Specifies the BackupKey Remote Protocol. This protocol encrypts secret values (such as cryptographic keys) so they can be backed up to storage that is not specially protected, and enables decryption of such values if recovery is necessary. |
|
|
Specifies the Microsoft NT Backup File Structure protocol, which describes the network format of the Windows NT backup file format and its constituent structures that may be used in other protocols. |
|
|
[MS-BPAU]: Background Intelligent Transfer Service (BITS) Peer-Caching: Peer Authentication Protocol |
Specifies the Background Intelligent Transfer Service (BITS) Peer-Caching: Peer Authentication Protocol. This protocol provides authentication for computers in an Active Directory domain in support of the BITS Peer-Caching Content Retrieval Protocol ([MS-BPCR]). |
|
[MS-BPCR]: Background Intelligent Transfer Service (BITS) Peer-Caching: Content Retrieval Protocol |
Specifies the Background Intelligent Transfer Service (BITS) Peer-Caching: Content Retrieval Protocol, which is one of the family of protocols that implements a distributed URL cache known as ""BITS peer-caching"". Other protocols in the family are used to discover potential peers and to authenticate them. |
|
[MS-BPDP]: Background Intelligent Transfer Service (BITS) Peer-Caching: Peer Discovery Protocol |
Specifies the Background Intelligent Transfer Service (BITS) Peer-Caching: Peer Discovery Protocol, which is used to locate hosts in a domain that supports the URL-caching protocol implemented by BITS. |
|
[MS-BRWS]: Common Internet File System (CIFS) Browser Protocol |
Specifies the Common Internet File System (CIFS) Browser Protocol, which updates all backup browser servers with the contents of the response to a NetServerEnum2 request and shares the processing load of enumerating the services available in the network across different servers. |
|
[MS-BRWSA]: Common Internet File System (CIFS) Browser Auxiliary Protocol |
Specifies the Common Internet File System (CIFS) Browser Auxiliary Protocol, which is used by the master browser server to query configuration information for the domains from the domain master browser server. |
|
[MS-CAPR]: Central Access Policy Identifier (ID) Retrieval Protocol |
Specifies the Central Access Policy ID Retrieval Protocol, which allows administrative applications to retrieve the set of central access policies deployed on remote computers. |
|
Specifies the Callback Control Protocol, which provides a standard method for transporting multi-protocol datagrams over point-to-point links. |
|
|
Specifies the Connected Devices Platform Protocol Version 3. This protocol provides a discovery system to authenticate and verify users and devices, as well as providing a message exchange between devices. It provides a transport-agnostic means of building connections among all of a user's devices, whether available through the cloud or through direct physical presence. |
|
|
Specifies the Corporate Error Reporting Version 1.0 Protocol, which enables an organization to copy error reports from a set of client machines to a CER file share on a specified Server Message Block (SMB) Protocol file server with additional configuration options. |
|
|
Specifies the Corporate Error Reporting V.2 Protocol, which enables enterprise computing sites to manage all error reporting information within the organization. |
|
|
Specifies the Compound File Binary File Format, a general-purpose file format that provides a file-system-like structure within a file for the storage of arbitrary, application-specific streams of data. |
|
|
Specifies the Extensible Authentication Protocol Method for Microsoft Challenge Handshake Authentication Protocol (CHAP). This protocol enables extensible authentication for network access. |
|
|
Specifies the Common Internet File System (CIFS) Protocol, a cross-platform, transport-independent protocol that provides a mechanism for client systems to use file and print services made available by server systems over a network. |
|
|
[MS-CMOM]: MSDTC Connection Manager: OleTx Management Protocol |
Specifies the MSDTC Connection Manager: OleTx Management Protocol. This protocol enables the remote management of an OleTx Transaction Manager and its extensions. |
|
[MS-CMP]: MSDTC Connection Manager: OleTx Multiplexing Protocol |
Specifies the MSDTC Connection Manager Protocol: Connection Multiplexing Protocol, which enables partners to multiplex any number of two-way connections over the MSDTC Connection Manager: OleTx Transports Protocol session. |
|
[MS-CMPO]: MSDTC Connection Manager: OleTx Transports Protocol |
Specifies the MSDTC Connection Manager: OleTx Transports Protocol, a peer-to-peer messaging protocol layered over a bidirectional pair of RPC connections. |
|
[MS-CMRP]: Failover Cluster: Management API (ClusAPI) Protocol |
Specifies the Failover Cluster: Management API (ClusAPI) Protocol, an RPC-based protocol that is used for remotely managing a cluster. |
|
Specifies the Component Object Model Plus (COM+) Protocol, which consists of a DCOM interface (and DCOM protocol extensions) that is used for adding transactions, implementing synchronization, managing multiple object class configurations, enforcing security, and providing additional functionality and attributes to DCOM-based distributed object applications. |
|
|
[MS-COMA]: Component Object Model Plus (COM+) Remote Administration Protocol |
Specifies the Component Object Model Plus (COM+) Remote Administration Protocol, which enables remote clients to register, import, remove, configure, control, and monitor components and conglomerations for an Object Request Broker (ORB). |
|
[MS-COMEV]: Component Object Model Plus (COM+) Event System Protocol |
Specifies the Component Object Model Plus (COM+) Event System Protocol, which is a protocol that exposes DCOM interfaces for storing and managing configuration data for publishers of events and their respective subscribers on remote computers. This protocol also specifies how to get specific information about a publisher and its subscribers. |
|
[MS-COMT]: Component Object Model Plus (COM+) Tracker Service Protocol |
Specifies the Component Object Model Plus (COM+) Tracker Service Protocol, which enables clients to monitor running instances of components. |
|
[MS-CPSP]: Connection Point Services: Phonebook Data Structure |
Specifies the Connection Point Services: Phonebook Data Structure. This structure describes a format for documenting POP entry information and a logical grouping of POPs based on their geographic location. |
|
Specifies the Certificate Templates Structure. This structure describes the syntax and interpretation of certificate templates, which forms the basis of certificate management for the Certificate Templates Protocol. |
|
|
[MS-CSRA]: Certificate Services Remote Administration Protocol |
Specifies the Certificate Services Remote Administration Protocol, which consists of a set of Distributed Component Object Model (DCOM) interfaces that enable administrative tools to configure the state and policy of a certification authority (CA) on a server. |
|
[MS-CSSP]: Credential Security Support Provider (CredSSP) Protocol |
Specifies the Credential Security Support Provider (CredSSP) Protocol, which enables an application to securely delegate a user's credentials from a client to a target server. |
|
[MS-CSVP]: Failover Cluster: Setup and Validation Protocol (ClusPrep) |
Specifies the Failover Cluster: Setup and Validation Protocol (ClusPrep), which remotely configures cluster nodes, cleans up cluster nodes, and validates that hardware and software settings are compatible with Failover Clustering. |
|
Specifies the Claims Transformation Algorithm (CTA), which consists of two components: a grammar describing a transformation rules language and an algorithm for transforming input claims into output claims. A claim is an assertion about a user identity in the form of a name-value tuple. Sets of claims are transformed from sending authority formats to receiving authority formats at authentication trust traversal boundaries. |
|
|
[MS-DCOM]: Distributed Component Object Model (DCOM) Remote Protocol |
Specifies the Distributed Component Object Model (DCOM) Remote Protocol, which exposes application objects via remote procedure calls (RPCs) and consists of a set of extensions layered on the Microsoft Remote Procedure Call Extensions. |
|
Specifies the Distributed File System (DFS): Referral Protocol, which enables file system clients to resolve names from a namespace distributed across many servers and geographies into local names on specific file servers. |
|
|
[MS-DFSNM]: Distributed File System (DFS): Namespace Management Protocol |
Specifies the Distributed File System (DFS): Namespace Management Protocol, which provides an RPC interface for administering DFS configurations. The client is an application that issues method calls on the RPC interface to administer DFS. The server is a DFS service that implements support for this RPC interface for administering DFS. |
|
Specifies the DFS Replication Helper Protocol, which is made up of a set of distributed component object model (DCOM) interfaces for configuring and monitoring DFS Replication Helper Protocols on a server. |
|
|
Specifies the Device Health Attestation Service Protocol, which enables the assessment of the attested boot state of devices. The outcome of the health assessment is included in a signed health certificate which can then be evaluated by other services to determine whether a device is meeting enterprise corporate policy for device health, or by third party services to identify jailbroken devices that should not receive content or access to certain resources. |
|
|
[MS-DHCPE]: Dynamic Host Configuration Protocol (DHCP) Extensions |
Specifies the Dynamic Host Configuration Protocol (DHCP), which describes the Microsoft specific vendor-class options included in the Microsoft implementation of DHCP. |
|
Specifies the DHCP Failover Protocol Extension, which extends the DHCP Failover Protocol by encrypting messages sent between the servers in a failover relationship and by providing client implementation options. |
|
|
[MS-DHCPM]: Microsoft Dynamic Host Configuration Protocol (DHCP) Server Management Protocol |
Specifies the Microsoft Dynamic Host Configuration Protocol (DHCP) Server Management Protocol, which defines the RPC interfaces that provide methods for remotely accessing and administering the DHCP server. This protocol is a client and server protocol based on RPC that is used in the configuration, management, and monitoring of a DHCP server. |
|
Specifies Digital Living Network Alliance (DLNA) Home Networked Device Interoperability Guidelines: Microsoft Extensions. The DLNA Guidelines define protocol extensions to protocols related to streaming of content. |
|
|
Specifies the Distributed Link Tracking: Workstation Protocol, which works with the Distributed Link Tracking (DLT) Central Manager Protocol to discover the new location of a file that has moved. DLT can determine whether the file has moved on a mass-storage device, within a computer, or between computers in a network. |
|
|
[MS-DNSP]: Domain Name Service (DNS) Server Management Protocol |
Specifies the Domain Name Service (DNS) Server Management Protocol, which defines the RPC interfaces that provide methods for remotely accessing and administering a DNS server. It is a client and server protocol based on RPC that is used in the configuration, management, and monitoring of a DNS server. |
|
Specifies the DirectPlay DXDiag Usage Protocol, intended for peer-to-peer network video gaming and used by the DXDiag application. |
|
|
Specifies the Digest Protocol Extensions, which describes the variations in the Windows implementation of the Digest Authentication protocol from the standard, as specified in [RFC2617]. |
|
|
[MS-DPWSSN]: Devices Profile for Web Services (DPWS): Size Negotiation Extension |
Specifies the Devices Profile for Web Services (DPWS): Size Negotiation Extension. This is an extension to the Devices Profile for Web Services (DPWS) and enables the negotiation of message sizes between a client and a service for a specific message transaction. |
|
Specifies the Desired State Configuration Pull Model Protocol, which is used to get a client's configuration and modules from the server and to report the client's status back to the server. The protocol depends on HTTP for the transfer of all protocol messages. With the Desired State Configuration Pull Model Protocol, binary data flows from the server to the client. |
|
|
Specifies the Device Services Lightweight Remoting Protocol, which enables remoting of services (objects, function calls, events, and so on) over a reliable point-to-point channel. |
|
|
[MS-DSML]: Directory Services Markup Language (DSML) 2.0 Protocol Extensions |
Specifies the Directory Services Markup Language (DSML) 2.0 Protocol Extensions. The SOAP session extensions (SSE) make it possible to maintain state information across multiple request/response operations. |
|
Specifies the Directory Services Setup Remote Protocol, which exposes an RPC interface that a client can call to obtain domain-related computer state and configuration information. |
|
|
[MS-DTCLU]: MSDTC Connection Manager: OleTx Transaction Protocol Logical Unit Mainframe Extension |
Specifies the MSDTC Connection Manager: OleTx Transaction Protocol Logical Unit Mainframe Extension, which provides concrete mechanisms for associating an Atomic Transaction and an LU type 6.2 Logical Unit of Work. |
|
[MS-DTCM]: MSDTC Connection Manager: OleTx Transaction Internet Protocol |
Specifies the MSDTC Connection Manager: OleTx Transaction Internet Protocol, which extends the OleTx protocol (see [MS-DTCO]) to enable its interoperation with the open-standard Transaction Internet Protocol (TIP). |
|
[MS-DTCO]: MSDTC Connection Manager: OleTx Transaction Protocol |
Specifies the MSDTC Connection Manager: OleTx Transaction Protocol, which provides concrete mechanisms for beginning, propagating, and completing atomic transactions. This protocol also provides mechanisms for coordinating agreement on a single atomic outcome for each transaction, and for reliably distributing that outcome to all participants in the transaction. |
|
Specifies the Device Registration Discovery Protocol, which is used to discover information about servers that can register corporate-owned and personal devices with a corporate network. |
|
|
Specifies the Device Registration Enrollment Protocol, which is used to register corporate-owned and personal devices with a corporate network. |
|
|
Specifies the Device Registration Join Protocol, which establishes a device identity between the physical device and a directory service. The identity is used at the system level to identify the device only. |
|
|
Specifies the Enterprise Client Sync protocol, which enables devices (such as tablets, PCs, or laptops) to synchronize files to and from a file server in a REST-based manner. |
|
|
Specifies the ExtendedError Remote Data Structure, which encodes extended error information. This data structure assumes that the reader has familiarity with the concepts and the requirements that are detailed in [MS-RPCE] and [C706]. |
|
|
Specifies the Encrypting File System Remote (EFSRPC) Protocol, which performs maintenance and management operations on encrypted data that is stored remotely and accessed over a network. |
|
|
Specifies the Enhanced Metafile Format (EMF) structure, which can store a picture in device-independent form. |
|
|
Specifies the Enhanced Metafile Format Plus Extensions, which defines a device-independent structure that encapsulates graphics commands and objects for storage or for sending to devices, such as displays and printers that support the drawing of images, graphics, and text. |
|
|
Specifies the Enhanced Metafile Spool Format. This structure specifies a metafile format that can store a print job in portable form. |
|
|
Specifies the EventLog Remoting Protocol, which exposes the RPC methods for reading events in both live and backup event logs on remote computers. |
|
|
Specifies the EventLog Remoting Protocol Version 6.0 protocol, which exposes RPC methods for reading events in both live and backup event logs on remote computers. This protocol was originally made available for Windows Vista. |
|
|
Specifies the Firewall and Advanced Security Protocol. The protocol manages firewall and advanced security components on remote computers. |
|
|
Specifies the Fax Server and Client Remote Protocol. It is an RPC-based, client-server protocol, and is used to send faxes and to manage the fax server and its queues. |
|
|
[MS-FCIADS]: File Classification Infrastructure Alternate Data Stream (ADS) File Format |
Specifies the File Classification Infrastructure Alternate Data Stream (ADS) File Format, which consists of structures for persisting file metadata information into NTFS alternate data streams. |
|
Specifies the File Replication Service Protocol, which is a replication protocol that is used to replicate files and folders across one or more members in an Active Directory domain. It works to keep copies of a file system tree up to date on all members of a replication group, while allowing any member of the group to change the contents at any time. |
|
|
Specifies the SD Microsoft Distributed File System Replication Protocol, which defines an RPC interface that replicates files between servers and enables the creation of multimaster optimistic file replication systems. |
|
|
Specifies File System Algorithms in terms of an abstract model for how an object store can be implemented to support the Server Message Block (SMB) Version 1.0 Protocol [MS-SMB] and the Server Message Block (SMB) Version 2.0 Protocol [MS-SMB2]. |
|
|
Specifies the File System Control Codes that define the network format of native Windows structures that may be used within other protocols. |
|
|
Specifies the File Server Resource Manager Protocol, which implements a set of a Distributed Component Object Model (DCOM) interfaces for managing the configuration of directory quotas, file screens, and storage report jobs on a machine. |
|
|
Specifies the File Server Remote VSS Protocol, an RPC-based protocol used for creating shadow copies of file shares on a remote computer, and for facilitating backup applications in performing application-consistent backup and restore of data on SMB2 shares. |
|
|
Specifies the File Set Version Comparison Algorithms, which is used by the Enterprise Client Synchronization Protocol to build and serialize a compact representation of version state across a data set consisting of files and directories. |
|
|
[MS-FTPS]: File Transfer Protocol over Secure Sockets Layer (FTPS) |
Specifies an extension to the File Transfer Protocol over TLS (FTPS). This extends FTPS with a feature known as Implicit SSL and introduces the AUTH SSL message to allow interoperability with legacy FTP clients. |
|
[MS-GIPUSB]: Gaming Input Protocol (GIP) Universal Serial Bus (USB) Extension |
Specifies the Gaming Input Protocol (GIP) Universal Serial Bus (USB) Extension of the USB 2.0 interface that provides extended semantics for interaction between game controller devices and a host. This protocol includes enumeration of device capabilities, determining of device type and subtype, transfer of gamepad and voice data, and support for an expansion device on the controller. |
|
Specifies the Group Key Distribution Protocol, which enables clients to obtain cryptographic keys associated with Active Directory security principals. |
|
|
Specifies the Group Policy: Audit Configuration Extension, which provides a mechanism for an administrator to control audit policies on clients. |
|
|
[MS-GPCAP]: Group Policy: Central Access Policies Protocol Extension |
Specifies the Group Policy: Central Access Policies Extension, which provides the means of configuring central access policies that are applied to Group Policy client computer resources for authorization purposes. |
|
[MS-GPDPC]: Group Policy: Deployed Printer Connections Extension |
Specifies the Group Policy: Deployed Printer Connections Extension, which supports the use of preconfigured collections of shared printer connections. |
|
Specifies the Group Policy: Encrypting File System Extension, which uses the Microsoft Group Policy Protocol to enable remote administrative configuration of the Encrypting File System. |
|
|
[MS-GPFAS]: Group Policy: Firewall and Advanced Security Data Structure |
Specifies The Group Policy: Firewall and Advanced Security data structure extension, which provides a mechanism for an administrator to control the Firewall and Advanced Security behavior of the client through group policy by using the Group Policy: Registry Extension Encoding protocol [MS-GPREG]. |
|
[MS-GPFR]: Group Policy: Folder Redirection Protocol Extension |
Specifies the Group Policy: Folder Redirection Protocol Extension, which provides a mechanism to relocate specific user folders to server disk volumes. The protocol extension describes how file system access requests to a user's folders are automatically redirected to a newly created folder for each user. |
|
[MS-GPIE]: Group Policy: Internet Explorer Maintenance Extension |
Specifies the Group Policy: Internet Explorer Maintenance Extension, which enables administrators to apply custom settings to the Internet Explorer configuration on one or more computers to enforce Internet-related security standards and provide a common browser interface within the organization. |
|
[MS-GPIPSEC]: Group Policy: IP Security (IPsec) Protocol Extension |
Specifies the IP Security (IPSec) Protocol Extension to the Group Policy: Core Protocol. This extension enables administrators to arbitrarily instruct large groups of client machines to configure their local IPsec/IKE components to provide basic IP traffic filtering, IP data integrity, and (optionally) IP data encryption. |
|
[MS-GPNAP]: Group Policy: Network Access Protection (NAP) Extension |
Specifies the Group Policy: Network Access Protection (NAP) Extension, used for controlling access to network resources. This extension enables network administrators to grant or restrict access to network resources based on client computer identity and compliance with corporate governance policy. |
|
[MS-GPNRPT]: Group Policy: Name Resolution Policy Table (NRPT) Data Extension |
Specifies the Name Resolution Policy Table (NRPT) Group Policy Data Extension, an extension to Group Policy: Registry Extension Encoding [MS-GPREG]. The NRPT Group Policy Data Extension provides a mechanism for an administrator to control any Name Resolution Policy behavior on a client by using group policy-based settings. |
|
Specifies the Group Policy: Core Protocol, which enables clients to discover and retrieve policy settings that administrators of a domain create. |
|
|
[MS-GPPREF]: Group Policy: Preferences Extension Data Structure |
Specifies the Group Policy: Preferences Extension. This extension to the Group Policy: Core Protocol provides a mechanism to manage and deploy policy preferences. |
|
Specifies the Group Policy: Registry Extension Encoding, an extension to the Group Policy: Core Protocol. This mechanism enables an administrator to control any behavior on a client that depends on registry-based settings. |
|
|
Specifies the Group Policy: Security Protocol Extension, which is an extension to the Group Policy: Core Protocol. This extension enables security policies to be distributed to multiple client systems, so these systems can enact the policies in accordance with the intentions of the administrator. |
|
|
Specifies the Group Policy: Scripts Extension Encoding, an extension to the Group Policy: Core Protocol that provides a mechanism for an administrator to instruct an arbitrarily large group of clients to execute administrator-specified code at computer startup, computer shutdown, user logon, and user logoff. |
|
|
[MS-GPSI]: Group Policy: Software Installation Protocol Extension |
Specifies the Group Policy: Software Installation Protocol Extension, which enables an administrator to install and remove software applications on client computers. |
|
Specifies the Group Policy: Wireless/Wired Protocol Extension, an extension to the Group Policy: Core Protocol that specifies the behaviors of the Wireless/Wired Group Policy administrative-side and client-side plug-in extensions. |
|
|
Specifies the Generic Security Service Algorithm for Secret Key Transaction Authentication for DNS (GSS-TSIG) Protocol Extension, which identifies one possible extension to TSIG based on the Generic Security Service Application Program Interface (GSS-API). |
|
|
Specifies the H.245 Protocol: Microsoft Extensions, which describes Microsoft extensions for the H.323 protocol. |
|
|
[MS-H26XPF]: Real-Time Transport Protocol (RTP/RTCP): H.261 and H.263 Video Streams Extensions |
Specifies the Real-Time Transport Protocol (RTP/RTCP): H.261 and H.263 Video Streams Extensions, which are used to transmit and receive H.261 or H.263 video streams in a two-party, peer-to-peer call. |
|
Specifies the Health Certificate Enrollment Protocol, which enables a network endpoint to obtain digital certificates. |
|
|
Specifies the HomeGroup Protocol, which is used to create a trust relationship that facilitates the advertising and publishing of content between machines via a peer-to-peer (P2P) infrastructure. |
|
|
Specifies the Host Guardian Services Attestation (HGSA) protocol, one of two services that comprise the Host Guardian Service. Host Guardian Service is a server role that provides security assurance for Shielded Virtual Machines (VMs) by ensuring that Shielded VMs can be run only on known and trusted fabric hosts that have a legitimate configuration. The other component service, the Key Protection Service, is specified in the [MS-KPS] protocol document. |
|
|
Specifies the Host Name Data Structure Extension, which defines the allowable host names that may be assigned to a computer. |
|
|
Specifies the Hyper-V Replica Log (HRL) File Format. Hyper-V Replica log files, required for tracking changes that have been made to the primary server, are created as part of failover replication. They are transported to the recovery server and parsed; updates are then applied to the recovery server. |
|
|
[MS-HTTP2E]: Hypertext Transfer Protocol Version 2 (HTTP/2) Extension |
Specifies a profile of and an extension to the Hypertext Transfer Protocol (HTTP) version 2, which is defined by [RFC7540]. |
|
Specifies the Hypertext Transfer Protocol (HTTP) Extensions, which extend the HyperText Transfer Protocol (HTTP) and deal with internationalization of host names and query strings. |
|
|
Specifies information regarding the implementation for hosting Hyper-V virtual machine files on Server Message Block (SMB) Version 3 shares. |
|
|
Specifies the ICertPassage Remote Protocol, a subset of the Windows Client Certificate Enrollment Protocol, as specified in [MS-WCCE]. This protocol only enables the client to enroll certificates, whereas [MS-WCCE] provides enrollment and additional functionality. |
|
|
[MS-IISS]: Internet Information Services (IIS) ServiceControl Protocol |
Specifies the Internet Information Services (IIS) ServiceControl Protocol, a client-to-server protocol that enables remote control of Internet services as a single unit. |
|
Specifies the Internet Key Exchange (IKE) Protocol Extensions, which describe the extensions specified in [RFC2409]. |
|
|
[MS-IMSA]: Internet Information Services (IIS) IMSAdminBaseW Remote Protocol |
Specifies the Internet Information Services (IIS) IMSAdminBaseW Remote Protocol, which defines interfaces that provide Unicode-compliant methods for remotely accessing and administering the IIS metabase associated with an application that manages IIS configuration, such as the IIS snap-in for Microsoft Management Console (MMC). |
|
Specifies the IManagedObject Interface Protocol. The IManagedObject interface is a COM interface used by the common language runtime (CLR) to identify managed objects (objects created by the CLR) that are exported for interoperability with the Component Object Model (COM). |
|
|
[MS-IPAMM]: IP Address Management (IPAM) Management Protocol |
Specifies the IP Address Management (IPAM) Management Protocol. This protocol is used to remotely retrieve and manage the data in the IPAM data store. The IPAM data store consists of the data pertaining to address space management, which includes the configuration data available with the DHCP and DNS server instances in the network. |
|
[MS-IPAMM2]: IP Address Management (IPAM) Management Protocol Version 2 |
Specifies the IP Address Management (IPAM) Management Protocol. This protocol is used to remotely retrieve and manage the data in the IPAM data store. The IPAM data store consists of the data pertaining to the address space management, which includes the configuration data available with the DHCP and DNS server instances in the network. |
|
Specifies the IP over HTTPS (IP-HTTPS) Tunneling Protocol, a mechanism to transport IPv6 packets on an HTTPS connection. |
|
|
Specifies the IrDA Object Exchange (OBEX) Protocol Profile, which clarifies the implementation details of [IROBEX] where necessary and clarifies which portions of [IROBEX] are not implemented. |
|
|
[MS-IRP]: Internet Information Services (IIS) Inetinfo Remote Protocol |
Specifies the Internet Information Services (IIS) Inetinfo Remote Protocol, an RPC-based client/server protocol that is used for managing Internet protocol servers such as those hosted by IIS. |
|
Specifies the Microsoft implementation of the Kerberos Protocol Extensions, as specified in [RFC4120], by specifying any Windows behaviors that differ from the Kerberos Protocol, in addition to Windows extensions for interactive logon and the inclusion of authorization information expressed as group memberships and related information. |
|
|
[MS-KKDCP]: Kerberos Key Distribution Center (KDC) Proxy Protocol |
Specifies the Kerberos Key Distribution Center (KDC) Proxy Protocol, which provides a mechanism for a client to use a KKDCP server to change passwords and securely obtain Kerberos service tickets from a Kerberos V5 server. |
|
Specifies the Key Provisioning Protocol, which defines a mechanism for a client to register a set of cryptographic keys on a user and device pair. |
|
|
Specifies the Key Protection Service protocol, one of two services that comprise the Host Guardian Service. Host Guardian Service is a server role that provides security assurance for Shielded Virtual Machines (VMs) by ensuring that Shielded VMs can be run only on known and trusted fabric hosts that have a legitimate configuration. The other component service, the Attestation Service, is specified in the [MS-HGSA] protocol document. |
|
|
[MS-L2TPIE]: Layer 2 Tunneling Protocol (L2TP) IPsec Extensions |
Specifies the Layer 2 Tunneling Protocol (L2TP) IPsec Extensions, which allows IP, IPX, or NetBEUI traffic to be encrypted and then sent over any medium that supports point-to-point (PPP) (Point to Point Protocol [RFC1661]) datagram delivery, such as IP, X.25, Frame Relay, or ATM. |
|
[MS-LLMNRP]: Link Local Multicast Name Resolution (LLMNR) Profile |
Specifies the Link Local Multicast Name Resolution (LLMNR) Profile, which describes the differences between this profile and the one defined in [RFC4795]. |
|
Specifies the Link Layer Topology Discovery (LLTD) Protocol, which an application or a higher-layer protocol can use to facilitate discovery of link-layer topology and diagnose various problems associated with a network's signal strength and bandwidth. |
|
|
Specifies the Live Remote Event Capture (LREC) Protocol, which enables a management station to monitor events on a target system across a network. The protocol supports various monitoring scenarios, such as a ""first line of defense"" for troubleshooting, where the remote system does not support the ability to log events locally. |
|
|
[MS-LSAD]: Local Security Authority (Domain Policy) Remote Protocol |
Specifies the Local Security Authority (Domain Policy) Remote Protocol. This protocol provides an RPC interface used for providing remote management for policy settings related to account objects, secret objects, trusted domain objects (TDOs), and other security-related policy settings. |
|
[MS-LSAT]: Local Security Authority (Translation Methods) Remote Protocol |
Specifies the Local Security Authority (Translation Methods) Remote Protocol, which is implemented in Windows-based products to translate identifiers for security principal between human-readable and machine-readable forms. |
|
Specifies the Lightweight Web Services Security Profile. This profile specifies how to perform lightweight client authentication and security token exchange based on set of security-related Web services protocols. |
|
|
Specifies the Remote Mailslot Protocol. This protocol is a simple, nonsecure, and unidirectional interprocess communications (IPC) protocol between a client and server. |
|
|
Specifies the Content Indexing Services Protocol, which enables a client to communicate with a server hosting an indexing service to issue queries. |
|
|
Specifies the Mobile Device Management Enrollment Protocol, which provides a mechanism for discovering devices and enrolling them into a management system. After enrollment, devices can be managed through the Microsoft Mobile Device Management Protocol [MS-MDM]. |
|
|
Specifies version 2 of the Mobile Device Enrollment Protocol (MDE), which enables enrolling a device with the DMS through an Enrollment Service (ES). The protocol includes the discovery of the Management Enrollment Service (MES) and enrollment with the ES. |
|
|
Specifies the Mobile Device Management Protocol (MDM), a subset of the Open Mobile Association (OMA) standard protocol, which provides a mechanism for managing devices previously enrolled into a management system through the Microsoft Mobile Device Management Enrollment Protocol [MS-MDE]. |
|
|
[MS-MICE]: Miracast over Infrastructure Connection Establishment Protocol |
The Miracast over Infrastructure Connection Establishment Protocol specifies a connection negotiation sequence used to connect, indicate readiness to connect, and disconnect from a Miracast over Infrastructure endpoint. This protocol also specifies the Miracast over Infrastructure Information Element (IE), which helps identify Miracast receivers (sinks) that can support a Miracast session over an infrastructure link (as opposed to a Wi-Fi Direct link). |
|
Specifies the Microsoft Media Server (MMS) Protocol, which defines how MMS streams multimedia from Windows Media Services to Windows Media Player, or to another instance of Windows Media Services. MMS uses TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). |
|
|
Specifies the Microsoft NetMeeting Protocol, which implements a method of application sharing over the T.120 Multipoint Communication Service (MCS) layer, using the S20 MCS Channel. |
|
|
[MS-MQBR]: Message Queuing (MSMQ): Binary Reliable Message Routing Algorithm |
Specifies the Message Queuing (MSMQ): Binary Reliable Message Routing Algorithm, which is used by MSMQ to communicate across both connected networks and heterogeneous networks. |
|
[MS-MQCN]: Message Queuing (MSMQ): Directory Service Change Notification Protocol |
Specifies the Message Queuing (MSMQ): Directory Service Change Notification Protocol. It defines a mechanism used by the MSMQ Directory Service or a queue manager to notify a queue manager of changes to its owned objects. |
|
[MS-MQDMPR]: Message Queuing (MSMQ): Common Data Model and Processing Rules |
Specifies the Message Queuing (MSMQ): Data Structures, which define an abstract data model and events shared by multiple MSMQ protocols. |
|
[MS-MQDS]: Message Queuing (MSMQ): Directory Service Protocol |
Specifies the Message Queuing (MSMQ): Directory Service Protocol, an RPC-based protocol that is used by MSMQ clients and Message Queuing servers to remotely access and maintain MSMQ directory objects. |
|
[MS-MQDSSM]: Message Queuing (MSMQ): Directory Service Schema Mapping |
Specifies the Message Queuing (MSMQ): Data Structures that are used by any protocol that manipulates the subset of the abstract data elements and data element attributes defined in [MS-MQDMPR] section 3.1. |
|
[MS-MQMP]: Message Queuing (MSMQ): Queue Manager Client Protocol |
Specifies the Message Queuing (MSMQ): Queue Manager Client Protocol, which enables communication between message queuing client applications and an MSMQ Queue Manager. |
|
Specifies Message Queuing (MSMQ): Data Structures, which contains common definitions and data structures that are used in the Microsoft Message Queuing protocols. |
|
|
[MS-MQMR]: Message Queuing (MSMQ): Queue Manager Management Protocol |
Specifies the Message Queuing (MSMQ): Queue Manager Management Protocol that is used for management operations on the MSMQ server, including monitoring the MSMQ installation and the queues. |
|
[MS-MQQB]: Message Queuing (MSMQ): Message Queuing Binary Protocol |
Specifies the Message Queuing (MSMQ): Binary Reliable Messaging Protocol, which defines a mechanism for reliably transferring messages between two message queues located on two different hosts. |
|
[MS-MQQP]: Message Queuing (MSMQ): Queue Manager to Queue Manager Protocol |
Specifies the Message Queuing (MSMQ): Queue Manager to Queue Manager Protocol, an RPC-based protocol used by the queue manager and runtime library to read and purge messages from a remote queue. |
|
[MS-MQRR]: Message Queuing (MSMQ): Queue Manager Remote Read Protocol |
Specifies the Message Queuing (MSMQ): Queue Manager Remote Read Protocol, an RPC-based protocol that is used by MSMQ clients to read or reject a message from a queue, move a message between queues, and purge messages from a queue. |
|
[MS-MQSD]: Message Queuing (MSMQ): Directory Service Discovery Protocol |
Specifies the Message Queuing (MSMQ): Directory Service Discovery Protocol, which is used by MSMQ clients to discover an accessible executing instance of an MSMQ Directory Service server. |
|
Specifies the Media Stream Broadcast (MSB) Protocol, which enables distribution of Advanced Systems Format (ASF) packets over a network for which Internet Protocol (IP) multicasting is enabled. |
|
|
[MS-MSBD]: Media Stream Broadcast Distribution (MSBD) Protocol |
Specifies the Media Stream Broadcast Distribution (MSBD) Protocol, which describes how to transfer an audio-visual content stream from a server to a single client. |
|
Specifies the Messenger Service Remote Protocol, a set of RPC interfaces that instructs a server to display short text messages to a console user, to deliver messages to a local or remote server for display to a console user, and to manage the names for which the server receives messages. |
|
|
[MS-MWBE]: Microsoft Web Browser Federated Sign-On Protocol Extensions |
Specifies the Microsoft Web Browser Federated Sign-On Protocol Extensions. This extension enables Web browser requestors that do not support scripting (to create POST messages) and enables passing security identifiers (SIDs) in Security Assertion Markup Language (SAML) V1.1 assertions. It is assumed that the reader is familiar with the terms, concepts, and protocols that are defined in [MS-MWBF]. |
|
Specifies the Microsoft Web Browser Federated Sign-On Protocol, which is primarily a restriction of the protocol that is specified in [WSFederation1.2] section 13. The restrictions are designed to enable greater interoperability by reducing the number of variations that must be implemented. This protocol also specifies minor additions to [WSFederation1.2] section 13 to handle common scenarios. |
|
|
Specifies the Negotiate and Nego2 HTTP Authentication Protocol, which describes support for SPNEGO authentication as specified in [RFC4559]. The tokens are transmitted using base64-encoding. This protocol calls out the differences in the Microsoft implementation from what is specified in [RFC4559], where applicable. |
|
|
Specifies the NetBIOS over TCP (NBT) Extensions, as specified in [RFC1001] and [RFC1002]. These extensions modify the syntax of allowable NetBIOS names and the behavior of timers, and add support for multihomed hosts. |
|
|
Specifies the Network Controller Protocol, which is used by tenants and network administrators to control data center networking. Common tasks that would use these APIs include designing and monitoring a virtual network in a data center. |
|
|
Enables an 802.11 wireless access point (AP) to inform a wireless client of the network cost and hints about the AP type. |
|
|
[MS-NEGOEX]: SPNEGO Extended Negotiation (NEGOEX) Security Mechanism |
Specifies the SPNEGO Extended Negotiation (NEGOEX) Security Mechanism that enhances the capabilities of SPNEGO [RFC4178] by providing a security mechanism which can be negotiated by SPNEGO. When the NEGOEX security mechanism is selected by SPNEGO, NEGOEX provides a method allowing selection of a common authentication protocol based on meta-data such as trust configurations. |
|
Specifies the .NET Tracing Protocol, which provides a method for correlating call traces in a .NET remoting application. |
|
|
[MS-NFPB]: Near Field Proximity: Bidirectional Services Protocol |
Specifies the Near Field Proximity: Bidirectional Services Protocol, which provides a way for devices to discover services and versions from one device to another. The protocol uses the ""Proximity Publication Subscription"" transport to exchange messages between peers. |
|
Specifies the Near Field Proximity: Sharing Protocol, which provides a way for devices to share files over an already established single-purpose channel. A client can use this protocol to send a set of files packaged in an Open Packaging Convention (OPC) file and encrypted over the channel. |
|
|
Specifies the Network Key Protector Unlock Protocol, which enables a client to send an encrypted package of key material along with a session key to a remote server and to receive the decrypted key material protected by the session key. |
|
|
Specifies the NT LAN Manager (NTLM) Authentication Protocol, used in Windows for authentication between clients and servers. NTLM is used by application protocols to authenticate remote users and, optionally, to provide session security when requested by the application. |
|
|
Specifies the .NET Message Framing MSMQ Binding Protocol, which defines how the mechanism described in [MC-NMF] for framing messages over any transport protocol can be applied over Message Queue (MSMQ). This protocol specification also defines how to indicate the use of .NET Message Framing over MSMQ as a SOAP transport in Web Services Description Language (WSDL). |
|
|
Specifies how the .NET Message Framing Protocol [MC-NMF] is bound to a TCP connection, including the initiation of the stream by using the net.tcp URI scheme and the application of .NET Message Framing over TCP as a SOAP transport in WSDL. |
|
|
Specifies the .NET NegotiateStream Protocol, which provides mutually authenticated and confidential communication over a TCP connection. It uses the Simple and Protected GSS-API Negotiation mechanism (SPNEGO) for security services (authentication, key derivation, and data encryption and decryption). |
|
|
[MS-NNTP]: NT LAN Manager (NTLM) Authentication: Network News Transfer Protocol (NNTP) Extension |
Specifies the NT LAN Manager (NTLM) Authentication: Network News Transfer Protocol (NNTP) Extension, which defines the use of NTLM authentication by NNTP to facilitate client authentication to a Windows-based NNTP server. |
|
Specifies the .NET Remoting: Binary Format Data Structure protocol, which defines a set of structures for representing object graph or method invocation information as an octet stream. |
|
|
Specifies the .NET Remoting: Lifetime Services Extension, which adds lifetime and remote activation capabilities to the .NET Remoting Core Protocol (specified in [MS-NRTP]). |
|
|
Specifies the Netlogon Remote Protocol, an RPC interface that is used for user and machine authentication on domain-based networks; to replicate the user account database for operating systems earlier than Windows 2000 backup domain controllers; to discover, manage, and maintain domain relationships of domain members and domain controllers across domains. |
|
|
Specifies the .NET Remoting: Core Protocol, a mechanism by which a calling program can invoke a method in a different address space over the network. Arguments are passed along as part of the invocation message, and return values are sent in the response. |
|
|
Specifies the Name Service Provider Interface (NSPI) Protocol, which provides messaging clients with a way to access and manipulate addressing data stored by a server. This protocol consists of an abstract data model and a single RPC call interface to manipulate data in that model. |
|
|
Specifies the NTLM Over HTTP Protocol, which is used to authenticate a Web client to a Web server. This protocol authentication variant works only with NTLM; the Kerberos protocol is not supported. |
|
|
[MS-NVGREE]: Network Virtualization using Generic Routing Encapsulation (NVGRE) Extensions |
Specifies the Network Virtualization using Generic Routing Encapsulation (NVGRE) Extensions protocol, which adds additional support to the NVGRE protocol by defining two new extension/control messages. One message initiates traffic redirection to a new network virtualization endpoint (NVE) when a VM is moved to a new NVE during a data center migration event. The other new message pushes out a policy refresh via an NVE in response to the moved VM. |
|
Specifies the OAuth 2.0 Protocol Extensions, which are used to extend the OAuth 2.0 Authorization Framework. These extensions enable authorization features such as resource specification, request identifiers, and login hints. |
|
|
[MS-OAPXBC]: OAuth 2.0 Protocol Extensions for Broker Clients |
Specifies the OAuth 2.0 Protocol Extensions for Broker Clients, extensions to [RFC6749] (The OAuth 2.0 Authorization Framework) that allow a broker client to obtain access tokens on behalf of calling clients. |
|
Specifies the OLE Automation Protocol, which uses DCOM as its transport layer and provides support for an additional set of types as well as for a late-bound calling mechanism. |
|
|
[MS-OCSP]: Online Certificate Status Protocol (OCSP) Extensions |
Specifies the Online Certificate Status Protocol (OCSP) Extensions, which defines the data that needs to be exchanged between an application that checks the status of a certificate and the responder that provides the status. |
|
Specifies the Microsoft OCSP Administration Protocol, which consists of a set of distributed component object model (DCOM) interfaces that allows administrative tools to configure the properties of the Online Responder. |
|
|
Specifies the Open Data (OData) Protocol. This protocol enables applications to expose data, by using common Web technologies, and by means of a data service that can be consumed by clients within corporate networks and across the Internet. |
|
|
Specifies the OpenID Connect 1.0 Protocol Extensions. These extensions define additional claims to carry information about the end user, including the user principal name, a locally unique identifier, a time for password expiration, and a URL for password change. These extensions also define additional provider metadata that enable the discovery of the issuer of access tokens and give additional information about provider capabilities. |
|
|
[MS-OLEDS]: Object Linking and Embedding (OLE) Data Structures |
Specifies the Object Linking and Embedding (OLE) Data Structures. These structures enable applications to create documents that contain linked or embedded objects. |
|
[MS-OLEPS]: Object Linking and Embedding (OLE) Property Set Data Structures |
Specifies the Object Linking and Embedding (OLE): Property Set Data Structures. These structures enable applications to write metadata in a manner that is discoverable to other software. |
|
[MS-OTPCE]: One-Time Password Certificate Enrollment Protocol |
Specifies the One-Time Password Certificate Enrollment Protocol, which enhances network security in remote access connections by utilizing different components, such as the one-time password (OTP) authentication mechanism as well as a short-lived smart card logon certificate. |
|
Specifies the Privilege Attribute Certificate Data Structure, which is used to encode authorization information. The Privilege Attribute Certificate also contains memberships, additional credential information, profile and policy information, and supporting security metadata. |
|
|
Specifies the [MS-PAN]: Print System Asynchronous Notification Protocol, an asynchronous protocol that clients use to receive print status notifications from a print server and send server-requested responses to those notifications back to the server. It is based on the Remote Procedure Call (RPC) protocol, as specified in [C706]. |
|
|
Specifies the Print System Asynchronous Remote Protocol, which defines the communication of print job processing and print system management information between a print client and a print server. |
|
|
[MS-PASS]: Passport Server Side Include (SSI) Version 1.4 Protocol |
Specifies the Passport Server Side Include (SSI) Version 1.4 Protocol, which describes how messages are encapsulated on the wire. |
|
Specifies the Publication Services Data Structure. This structure describes the data that computers use to describe themselves and the resources they offer as Web services over IP-based networks. |
|
|
[MS-PCCRC]: Peer Content Caching and Retrieval: Content Identification |
Specifies Peer Content Caching and Retrieval: Content Identification, the content information format used by the Windows Branch Caching Framework to uniquely identify content for discovery and retrieval purposes. |
|
[MS-PCCRD]: Peer Content Caching and Retrieval: Discovery Protocol |
Specifies the Peer Content Caching and Retrieval Discovery Protocol, which is based on the Web Services Dynamic Discovery (WS-Discovery) protocol. It is a content caching and retrieval framework based on a peer-to-peer discovery and distribution model. |
|
[MS-PCCRR]: Peer Content Caching and Retrieval: Retrieval Protocol |
Specifies the Peer Content Caching and Retrieval: Retrieval Protocol. This protocol defines two message exchanges, one for querying the server for the availability of certain content, and the other for retrieving content from a server. |
|
[MS-PCCRTP]: Peer Content Caching and Retrieval: Hypertext Transfer Protocol (HTTP) Extensions |
Specifies the Peer Content Caching and Retrieval: Hypertext Transfer Protocol (HTTP) Extensions, which implements a new type of content encoding, PeerDist, that can be used in HTTP/1.1. In particular, it specifies the mechanism used by an HTTP/1.1 client and an HTTP/1.1 server to communicate with each other using the PeerDist content encoding. |
|
[MS-PCHC]: Peer Content Caching and Retrieval: Hosted Cache Protocol |
Specifies the Peer Content Caching and Retrieval: Hosted Cache Protocol, used by clients to offer metadata to a hosted cache server. |
|
Specifies the Performance Counter Query Protocol, which is used for browsing performance counters and retrieving performance counter values from a server. |
|
|
[MS-PEAP]: Protected Extensible Authentication Protocol (PEAP) |
Specifies the Protected Extensible Authentication Protocol (PEAP), which adds security services to the Extensible Authentication Protocol methods. |
|
Specifies the Public Key Authentication Protocol, which provides a method for HTTP clients to prove possession of a private key to a web server without having to rely on client Transport Layer Security (TLS) support from the underlying platform. |
|
|
[MS-PKCA]: Public Key Cryptography for Initial Authentication (PKINIT) in Kerberos Protocol |
Specifies the Public Key Cryptography for Initial Authentication (PKINIT) in Kerberos Protocol. This protocol enables the use of public key cryptography in the initial authentication exchange of the Kerberos Protocol (PKINIT) and specifies the Windows implementation of PKINIT where it differs from [RFC4556]. |
|
Specifies the Performance Logs and Alerts Protocol, which provides a set of DCOM interfaces to control data collection on a remote system. The control includes starting, stopping, scheduling, and configuration of data collector objects, and the creation of alerts. |
|
|
Specifies the Peer Name Resolution Protocol (PNRP) Version 4.0, which is used to resolve a name to a set of information, such as IP addresses; to maintain a cloud of peer nodes; to maintain a distributed cache of endpoint information; and to transfer requests for Peer Name resolutions between nodes. |
|
|
[MS-POP3]: NT LAN Manager (NTLM) Authentication: Post Office Protocol - Version 3 (POP3) Extension |
Specifies the NT LAN Manager (NTLM) Authentication: Post Office Protocol - Version 3 (POP3) Extension, which describes the use of NTLM Authentication (see [MS-NLMP]) by the Post Office Protocol 3 (POP3) to facilitate client authentication to a Windows POP3 server. POP3 specifies a protocol for the inquiry and retrieval of electronic mail. |
|
Specifies the Peer-to-Peer Graphing Protocol, a peer-to-peer protocol for establishing and maintaining a connected set of nodes (referred to as a graph), and replicating data among the nodes. |
|
|
Specifies the PPP Over IrDA Dialup Protocol, which enables the scenario in which a computer with infrared capabilities obtains network access by using a modem via the infrared link. |
|
|
Specifies the Peer-to-Peer Grouping Security Protocol (P2P Grouping), which layers on top of the Peer-to-Peer Graphing Protocol [MS-PPGRH] and adds security and discovery services. |
|
|
Specifies the Property Store Binary File Format. This file format is a persistence format for a set of properties. Implementers can use this file format to store a set of properties in a file or within another structure. |
|
|
Specifies the Proximity Service Discovery Protocol, which conveys service discovery information, such as service advertisements, as part of Beacon frames, as specified in [IEEE802.11-2007]. |
|
|
Specifies the PowerShell Remote Debugging Protocol (PSRDP).This protocol extends the existing PowerShell Remoting Protocol (PSRP) specified in [MS-PSRP] to support debugging over a remote session. |
|
|
Specifies the Windows PowerShell Remoting Protocol, which encodes messages prior to sending them over the Web Services Management Protocol Extensions for the Windows Vista [MS-WSMV] layer. |
|
|
Specifies the Point-to-Point Tunneling Protocol, which allows the Point-to-Point Protocol (PPP) [RFC1661] to be tunneled through an IP network. |
|
|
[MS-QDP]: Quality Windows Audio/Video Experience (qWave): Wireless Diagnostics Protocol |
Specifies the Quality Windows Audio/Video Experience (qWave): Wireless Diagnostics Protocol. This protocol is used to obtain information from a host or a device about its wireless characteristics, which can facilitate the diagnosis of wireless network issues. |
|
[MS-QLPB]: Quality Windows Audio/Video Experience (qWave): Layer 3 Probing Protocol |
Specifies the Quality Windows Audio/Video Experience (qWave): Layer 3 Probing (L3P) (qWave) Protocol, which operates over TCP/IP and UDP/IP. qWave enables applications to evaluate link bandwidth and quality by analyzing timestamps of probe packets transmitted between two devices. |
|
Specifies the Remote Assistance Protocol, which is used after a remote assistance connection is established between two computers. |
|
|
Specifies the Remote Authorization API Protocol, which is used to perform ""what-if"" authorization queries on remote computers. It allows applications to simulate an access control decision that would be made when a principal attempts to access a remote resource protected with an authorization policy. |
|
|
Specifies the Remote Assistance Initiation Protocol, which enables an authorized expert to start Remote Assistance (RA) on a remote novice computer to retrieve data that is required to make a Remote Assistance connection from the expert's computer to the novice's computer. |
|
|
Specifies the Remote Assistance Initiation over PNRP Protocol, which is used to establish a Remote Assistance connection between two computers. |
|
|
Specifies the Remote Administrative Interface: WINS protocol, which enables local or remote administration of the Windows Internet Name Service (WINS) within the Microsoft Management Console (MMC) WINS snap-in and the NetSh command line (WINS context). |
|
|
Specifies the Microsoft Remote Administration Protocol (RAP), which Microsoft LAN Manager uses to perform remote administrative functions and is included in the Microsoft Windows operating system for compatibility reasons. |
|
|
[MS-RASA]: Remote Access Server Advertisement (RASADV) Protocol |
Specifies the Remote Access Server Advertisement (RASADV) Protocol, by which Remote Access Service (RAS) Servers advertise their presence within a local network, enabling network administrators to detect nonmalicious configuration and deployment of gateways providing external access to their network. |
|
Specifies the Remote Certificate Mapping Protocol, which enables servers to use a directory, database, or other technology to map the user's X.509 certificate to a security principal. |
|
|
Specifies the Remote Differential Compression Algorithm protocol, which enables efficient synchronization of files with a remote source by using compression techniques to minimize the amount of data sent between a client and server. |
|
|
Specifies the Remote Desktop Protocol: Audio Level and Drive Letter Persistence Virtual Channel Extension, which allows an RDP (remote desktop connection) client device to mimic a Windows client PC session with respect to audio levels and drive letters. |
|
|
[MS-RDPBCGR]: Remote Desktop Protocol: Basic Connectivity and Graphics Remoting |
Specifies the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting, designed to facilitate user interaction with a remote computer system by transferring graphics display information from the remote computer to the user and transporting input from the user to the remote computer, where it may be injected locally. |
|
[MS-RDPCR2]: Remote Desktop Protocol: Composited Remoting V2 |
Specifies the Remote Desktop Protocol: Composited Remoting V2, which displays the contents of the Windows-based desktop running on one machine on a second machine connected to the first via a network. |
|
[MS-RDPEA]: Remote Desktop Protocol: Audio Output Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Audio Output Virtual Channel Extension, which transfers audio data from the server to the client. |
|
[MS-RDPEAI]: Remote Desktop Protocol: Audio Input Redirection Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Audio Input Redirection Virtual Channel Extension, which transfers audio data from a client to a server. |
|
[MS-RDPEAR]: Remote Desktop Protocol Authentication Redirection Virtual Channel |
Performs authentication over a Remote Desktop connection. By establishing a virtual channel between the source and the target devices, it can relay authentication requests received by the target device to the source device. |
|
[MS-RDPECAM]: Remote Desktop Protocol: Video Capture Virtual Channel Extension |
The Remote Desktop Protocol: Video Capture Virtual Channel Extension adds remoting of video capture devices, such as webcams, to the Basic Connectivity and Graphics Remoting Protocol. |
|
[MS-RDPECI]: Remote Desktop Protocol: Core Input Virtual Channel Extension |
The Remote Desktop Protocol: Core Input Virtual Channel Extension enables remoting of keyboard and mouse pointer input over the UDP transport. This is an extension to the Basic Connectivity and Graphics Remoting Protocol (2785). |
|
[MS-RDPECLIP]: Remote Desktop Protocol: Clipboard Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Clipboard Virtual Channel Extension, which enables users to seamlessly transfer data via the system clipboard between applications that are running on different computers. |
|
[MS-RDPEDC]: Remote Desktop Protocol: Desktop Composition Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Desktop Composition Virtual Channel Extension, which enables a remote display client to replicate the functionality of the Desktop Window Manager (DWM) across a network boundary. |
|
[MS-RDPEDISP]: Remote Desktop Protocol: Display Update Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Display Control Virtual Channel Extension to the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting, as specified in [MS-RDPBCGR]. This control protocol is used to request display configuration changes in a remote session. |
|
[MS-RDPEDYC]: Remote Desktop Protocol: Dynamic Channel Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Dynamic Channel Virtual Channel Extension, which supports features such as classes of priority (that may be used to implement bandwidth allocation) and individually connected endpoints using dynamic virtual channel (DVC) listeners. |
|
[MS-RDPEECO]: Remote Desktop Protocol: Virtual Channel Echo Extension |
Specifies the Remote Desktop Protocol: Virtual Channel Echo Extension. This extension is used as a ping and echo mechanism to determine various network characteristics that are significant for RDP. |
|
[MS-RDPEFS]: Remote Desktop Protocol: File System Virtual Channel Extension |
Specifies the Remote Desktop Protocol: File System Virtual Channel Extension, which runs over a static virtual channel with the name RDPDR. |
|
[MS-RDPEGDI]: Remote Desktop Protocol: Graphics Device Interface (GDI) Acceleration Extensions |
Specifies the Remote Desktop Protocol: Graphics Device Interface (GDI) Acceleration Extensions, which reduces the bandwidth associated with graphics remoting by encoding the drawing operations that produce an image instead of encoding the actual image. |
|
[MS-RDPEGFX]: Remote Desktop Protocol: Graphics Pipeline Extension |
Specifies the Remote Desktop Protocol: Graphics Pipeline Extension, a graphics protocol that is used to encode graphics display data generated in a remote terminal server session so that the data can be sent from the server and received, decoded, and rendered by a compatible client. The net effect is that a desktop or an application running on a remote terminal server appears as if it is running locally. |
|
[MS-RDPEGT]: Remote Desktop Protocol: Geometry Tracking Virtual Channel Protocol Extension |
Specifies the Remote Desktop Protocol: Geometry Tracking Virtual Channel Extension, which extends the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting. This protocol facilitates graphics rendering between a desktop host and a remote desktop client in a way that the client does not need to know the origin of the graphics. |
|
[MS-RDPEI]: Remote Desktop Protocol: Input Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Input Virtual Channel Extension, which is used to remote multitouch input frames from a terminal server client to a terminal server. Multitouch input frames are generated at the client, encoded, and sent to the server. Thereafter, these frames are received and decoded by the server and injected into the session associated with the remote user. |
|
[MS-RDPEL]: Remote Desktop Protocol: Location Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Location Channel Extension, which adds the ability to redirect the client's location (latitude, longitude and altitude) to a server so that location-based services running in a user session can provide a more contextualized experience where possible. |
|
Specifies the Remote Desktop Protocol: Licensing Extension, which expands on the licensing protocol sequence specified in [MS-RDPBCGR] to address scenarios requiring the exchange of licensing information between the client and server. |
|
|
[MS-RDPEMC]: Remote Desktop Protocol: Multiparty Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Multiparty Virtual Channel Extension, which describes the messages that are exchanged between a remote desktop host and the participants with whom it is engaging in multiparty application sharing. |
|
[MS-RDPEMSC]: Remote Desktop Protocol: Mouse Cursor Virtual Channel Extension |
The Remote Desktop Protocol: Mouse Cursor Virtual Channel Extension enables remoting of mouse cursor bitmap over the UDP transport. This is an extension to the Basic Connectivity and Graphics Remoting Protocol (2785). |
|
[MS-RDPEMT]: Remote Desktop Protocol: Multitransport Extension |
This document specifies the Remote Desktop Protocol: Multitransport Extension, which is used to create multiple data-transport connections between an RDP client and an RDP server. |
|
[MS-RDPEPC]: Remote Desktop Protocol: Print Virtual Channel Extension |
Specifies the Desktop Protocol: Print Virtual Channel Extensions, which specifies the communication used to enable the redirection of printers between a terminal client and a terminal server. |
|
[MS-RDPEPNP]: Remote Desktop Protocol: Plug and Play Devices Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Plug and Play Devices Virtual Channel Extension, which is used to redirect Plug and Play devices from a terminal client to the terminal server. |
|
[MS-RDPEPS]: Remote Desktop Protocol: Session Selection Extension |
Specifies the Remote Desktop Protocol: Session Selection Extension, which expands upon the original connectivity options specified in [MS-RDPBCGR] to address a wide range of new scenarios. |
|
[MS-RDPERP]: Remote Desktop Protocol: Remote Programs Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Remote Programs Virtual Channel Extension, an RDP feature that presents a remote application (running remotely on a RAIL server) as a local user application (running on the RAIL client machine). |
|
[MS-RDPESC]: Remote Desktop Protocol: Smart Card Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Smart Card Virtual Channel Extension, an extension (including virtual channels) that supports smart card reader-like devices. |
|
[MS-RDPESP]: Remote Desktop Protocol: Serial and Parallel Port Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Serial and Parallel Port Virtual Channel Extension, which redirects serial and parallel ports from a terminal client to the terminal server. This extension allows the server to access client ports as if the connected devices were local to the server. |
|
[MS-RDPET]: Remote Desktop Protocol: Telemetry Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Telemetry Virtual Channel Extension, which extends the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting [MS-RDPBCGR]. This extension is a telemetry protocol that is used to send client performance metrics to the server. |
|
[MS-RDPETXT]: Remote Desktop Protocol: Text Input Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Text Input Virtual Channel Extension, which enables text input and IME integration in virtualized or remote applications. This protocol is used to enable local input methods to operate on applications hosted in virtualized environments or on remote machines. This includes input methods such as speech dictation, software keyboard, IMEs, or handwriting. |
|
[MS-RDPEUDP]: Remote Desktop Protocol: UDP Transport Extension |
Specifies the Remote Desktop Protocol: UDP Transport Extension, which extends the transport mechanisms in the Remote Desktop Protocol (RDP) to enable network connectivity between the user's machine and a remote computer system over the User Datagram Protocol (UDP). |
|
[MS-RDPEUDP2]: Remote Desktop Protocol: UDP Transport Extension Version 2 |
Remote Desktop Protocol: UDP Transport Extension Version 2 is used to exchange data, for example audio and video, between a remote desktop client and remote desktop server over UDP transport using a URCP based rate control. |
|
[MS-RDPEUSB]: Remote Desktop Protocol: USB Devices Virtual Channel Extension |
Specifies the Remote Desktop Protocol: USB Devices Virtual Channel Extension, which is used to redirect USB devices from a terminal client to the terminal server. This allows the server access to devices that are physically connected to the client as if the device were local to the server. |
|
[MS-RDPEV]: Remote Desktop Protocol: Video Redirection Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Video Redirection Virtual Channel Extension, which redirects audio/video streams from the terminal server to the terminal client. |
|
[MS-RDPEVOR]: Remote Desktop Protocol: Video Optimized Remoting Virtual Channel Extension |
Specifies the Remote Desktop Protocol: Video Optimized Remoting Virtual Channel Extension. This is an extension of the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting protocol [MS-RDPBCGR], which runs over a dynamic virtual channel, as specified in [MS-RDPEDYC]. The Remote Desktop Protocol: Video Optimized Remoting Virtual Channel Extension is used to redirect certain rapidly changing graphics content as a video stream from the remote desktop host to the remote desktop client. This protocol specifies the communication between a remote desktop host and a remote desktop client. |
|
[MS-RDPEWA]: Remote Desktop Protocol: WebAuthn Virtual Channel Protocol |
Specifies the Remote Desktop Protocol (RDP): WebAuthn Virtual Channel Protocol which provides a way for a user to do WebAuthn operations over the RDP protocol. It enables a server to send webauthn request to a client, the client can then use this request to talk to authenticators (platform as well as cross-platform) and reply with the response. |
|
[MS-RDPEXPS]: Remote Desktop Protocol: XML Paper Specification (XPS) Print Virtual Channel Extension |
Specifies the Remote Desktop Protocol: XML Paper Specification (XPS) Print Virtual Channel Extension, which redirects printing jobs from the terminal server to the terminal client. |
|
Specifies the Remote Desktop Protocol: NSCodec Extension, an extension to the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting (as specified in [MS-RDPBCGR]). This extension specifies an image codec that can be used to encode screen images by utilizing efficient and effective compression. |
|
|
[MS-RDPRFX]: Remote Desktop Protocol: RemoteFX Codec Extension |
Specifies the Remote Desktop Protocol: RemoteFX Codec Extension, which uses a lossy image codec to encode screen images with efficient and effective compression. |
|
Specifies the Remote Desktop Workspace Runtime Protocol, an HTTP-based protocol for the Remote Desktop Service to discover disconnected sessions for a user and obtain the files required to reconnect to those disconnected sessions. The protocol uses a SOAP-based payload to describe and provide the remote resources to reconnect to a user's disconnected sessions. |
|
|
[MS-RMPR]: Rights Management Services (RMS): Client-to-Server Protocol |
Specifies the Rights Management Services (RMS) Client-to-Server Protocol, a SOAP protocol used to obtain and issue certificates and licenses used for creating and working with protected content. |
|
[MS-RMPRS]: Rights Management Services (RMS): Server-to-Server Protocol |
Specifies the Rights Management Services (RMS): Server-to-Server Protocol, which is used to communicate information between RMS servers, implementing five interfaces, using either a binary-formatted interface over HTTP or a SOAP-based protocol over HTTP. |
|
[MS-RMSI]: Rights Management Services (RMS): ISV Extension Protocol |
Specifies the Rights Management Services (RMS): ISV Extension Protocol, a SOAP protocol that is used to communicate information between applications and RMS servers directly without using the RMS client. |
|
[MS-RNAP]: Vendor-Specific RADIUS Attributes for Network Access Protection (NAP) Data Structure |
Specifies the Vendor-Specific RADIUS Attributes for Network Access Protection (NAP) Data Structure protocol, which describes the Microsoft RADIUS vendor-specific attributes (VSAs) that are implemented in the Windows operating system. |
|
[MS-RNAS]: Vendor-Specific RADIUS Attributes for Network Policy and Access Server Data Structure |
Specifies the Vendor-Specific RADIUS Attributes for the Network Policy and Access Server (NPAS) Data Structure protocol, which describes the Microsoft RADIUS vendor-specific attributes (VSAs) that are implemented in the Windows operating system. |
|
Specifies the Remote Procedure Call Protocol Extensions, a set of extensions to the DCE Remote Procedure Call 1.1 Specification, as specified in [C706]. These extensions add new capabilities to the DCE 1.1: RPC Specification, allow for more secure implementations to be built, and, in some cases, place additional restrictions on the DCE RPC Specification. |
|
|
Specifies the Remote Procedure Call over HTTP Protocol, which describes the use of HTTP or HTTPS as a transport for the Remote Procedure Call (RPC) Protocol, as specified in [C706] and extended in [MS-RPCE]. |
|
|
[MS-RPCL]: Remote Procedure Call Location Services Extensions |
Specifies the Remote Procedure Call Location Services Extensions, a set of extensions and restrictions to the DCE Remote Procedure Call Location Services specification as defined in [C706]. |
|
Specifies the Print System Remote Protocol, which defines the communication of print job processing and print system management between a print client and a print server. |
|
|
[MS-RRASM]: Routing and Remote Access Server (RRAS) Management Protocol |
Specifies the Routing and Remote Access Server (RRAS) Management Protocol, which enables remote management (configuration and monitoring) of RRAS. The RRAS implementation refers to the components that can be configured to provide routing, remote access service, and site-to-site connectivity. |
|
Specifies the Windows Remote Registry Protocol, a remote procedure call (RPC)-based client/server protocol that is used to remotely manage a hierarchical data store such as the Windows registry. |
|
|
Specifies the Remote Rendering Protocol Version 2, a user interface system for applications in Windows Media Center, which consists of an application-side component model connected to a remote renderer by an asynchronous messaging system that enables the quick and easy construction of captivating interfaces. |
|
|
Specifies and provides support for client machines to monitor and manage Remote Desktop Protocol (RDP) sessions on a server machine. The protocol provides a set of web service APIs that are implemented as a SOAP-based protocol that uses Hypertext Transfer Protocol (HTTP) and Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) as its transport. |
|
|
Specifies the Removable Storage Manager (RSM) Remote Protocol, a set of distributed component object model (DCOM) interfaces for applications to manage robotic changers, media libraries, and tape drives. This protocol deals with detailed low-level operating system and storage concepts. |
|
|
Specifies the Remote Shutdown Protocol, which is designed for shutting down, or for terminating the shutdown, of a remote computer during the shutdown waiting period. |
|
|
Specifies the Remote Shared Virtual Disk Protocol, which supports accessing and manipulating virtual disks stored as files on an SMB3 file server. This protocol enables opening, querying, administering, reserving, reading, and writing the virtual disk objects, providing for flexible access by single or multiple consumers. It also provides for forwarding of SCSI operations, to be processed by the virtual disk. |
|
|
Specifies the Real-Time Transport Protocol (RTP/RTCP): DTMF Digits, Telephony Tones, and Telephony Signals Data Extensions, which describes the payload format needed to carry DTMF digits, tones, and signals in RTP packets over a network transport. |
|
|
[MS-RTPME]: Real-Time Transport Protocol (RTP/RTCP): Microsoft Extensions |
Specifies the Real-Time Transport Protocol (RTP/RTCP): Microsoft Extensions, which is a set of network transport functions suitable for applications transmitting real-time data, such as audio and video, across multimedia endpoints. |
|
[MS-RTPRAD]: Real-Time Transport Protocol (RTP/RTCP): Redundant Audio Data Extensions |
Specifies the Real-Time Transport Protocol (RTP/RTCP): Redundant Audio Data Extensions, which encodes redundant audio data for use with the Real-Time Transport Protocol (RTP) Extensions protocol. |
|
[MS-RTSP]: Real-Time Streaming Protocol (RTSP) Windows Media Extensions |
Specifies the Real-Time Streaming Protocol (RTSP) Windows Media Extensions, which defines Windows Media extensions to the Real-Time Streaming Protocol (RTSP). |
|
Specifies the Remote Experience Advertisement Protocol, which enables a Universal Plug and Play (UPnP) service implemented by a device to be used by the client to advertise available remote experience information to that device. |
|
|
[MS-SAMLPR]: Security Assertion Markup Language (SAML) Proxy Request Signing Protocol |
Specifies the Security Assertion Markup Language (SAML) Proxy Request Signing Protocol, which allows proxy servers to perform operations that require knowledge of configured keys and other state information about federated sites known by the Security Token service server. |
|
[MS-SAMR]: Security Account Manager (SAM) Remote Protocol (Client-to-Server) |
Specifies the Security Account Manager (SAM) Remote Protocol, which supports management functionality for an account store or directory containing users and groups. The goal of the protocol is to enable IT administrators and users to manage users, groups, and computers. |
|
[MS-SAMS]: Security Account Manager (SAM) Remote Protocol (Server-to-Server) |
Specifies the Security Account Manager (SAM) Remote Protocol (Server-to-Server). Domain controllers (DCs) use this protocol to forward time-critical database changes to the primary domain controller (PDC), and to forward time-critical database changes from a read-only domain controller (RODC) to a writable NC replica within the same domain outside the normal replication protocol. |
|
Specifies the Shadow Copy Management Protocol, which programmatically enumerates shadow copies and configures shadow copy storage on remote machines. |
|
|
Specifies the Service Control Manager Remote Protocol, which is used for remotely managing the Service Control Manager (SCM), an RPC server that enables service configuration and control of service programs. |
|
|
Specifies the Session Description Protocol (SDP) Extensions, which describes the session description that is used to negotiate instant messaging, audio and video, and data collaboration sessions, and notes the extensions used. |
|
|
Specifies the Server and File Management Web APIs Protocol, which is used to access a REST-based server and to manage files over the HTTPS transports. The protocol exposes a set of built-in web services for third-party developers to build applications on different devices that can access files and manage servers remotely. The protocol also allows third-party developers to add their own web services without the need to handle authentication. |
|
|
[MS-SFU]: Kerberos Protocol Extensions: Service for User and Constrained Delegation Protocol |
Specifies the Kerberos Protocol Extensions: Service for User and Constrained Delegation Protocol, which are two extensions to the Kerberos protocol as developed by Microsoft. These two extensions, collectively known as Service for User (S4U), enable an application service to obtain a Kerberos service ticket on behalf of a user. |
|
Specifies the Shell Link Binary File Format, which contains information that can be used to access another data object. The Shell Link Binary File Format is the format of Windows files with the extension "LNK". |
|
|
Specifies Microsoft extensions to the Session Initiation Protocol (SIP), as specified in [RFC3261], which is used by terminals to establish, modify, and terminate multimedia sessions or calls. The SIP extensions add support for privacy features and for subscription requests for offline end nodes to the SIP extensions for presence. |
|
|
Specifies the Server Message Block (SMB) Protocol, which defines extensions to the existing Common Internet File System (CIFS) specification that have been implemented by Microsoft since the publication of the [CIFS] specification. |
|
|
[MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3 |
Specifies the Server Message Block (SMB) Protocol Versions 2 and 3, which support the sharing of file and print resources between machines and extend the concepts from the Server Message Block Protocol. |
|
[MS-SMBD]: SMB2 Remote Direct Memory Access (RDMA) Transport Protocol |
Specifies the SMB2 Remote Direct Memory Access (RDMA) Transport Protocol, a wrapper for the existing SMB2 protocol that allows SMB2 packets to be delivered over RDMA-capable transports such as iWARP or Infiniband while utilizing the direct data placement (DDP) capabilities of these transports. Benefits include reduced CPU overhead, lower latency, and improved throughput. |
|
[MS-SMTPNTLM]: NT LAN Manager (NTLM) Authentication: Simple Mail Transfer Protocol (SMTP) Extension |
Specifies the NT LAN Manager (NTLM) Authentication: Simple Mail Transfer Protocol (SMTP) Extension, which uses NT LAN Manager (NTLM) authentication (as specified in [MS-NLMP]) by the Simple Mail Transfer Protocol (SMTP) to facilitate client authentication to a Windows SMTP server. |
|
Specifies the Server Network Information Discovery Protocol, which defines a pair of request and response messages by which a protocol client can locate protocol servers within the broadcast/multicast scope. The client can then get network information (such as NetBIOS name, Internet Protocol version 4 (IPv4), and Internet Protocol version 6 (IPv6) addresses) about the servers. |
|
|
[MS-SNTP]: Network Time Protocol (NTP) Authentication Extensions |
Specifies the Network Time Protocol (NTP) Authentication Extensions, which is an authentication extension to the Network Time Protocol (NTP) version 3 ([RFC1305]) and the Simple Network Time Protocol (SNTP) version 4 ([RFC2030]). |
|
[MS-SPNG]: Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) Extension |
Specifies the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) Protocol Extension. SPNEGO is a security protocol that uses a GSS-API authentication mechanism. GSS-API is a literal set of functions that include both an API and a methodology for approaching authentication. |
|
[MS-SQMCS]: Software Quality Metrics (SQM) Client-to-Service Version 1 Protocol |
Specifies the Software Quality Metrics (SQM) Client-to-Service Protocol V1, used to send software instrumentation metrics to the SQM service and by the client to download client-specific control data. The protocol allows applications and operating system components to collect and send instrumentation metrics to a hosted service. |
|
[MS-SQMCS2]: Software Quality Metrics (SQM) Client-to-Service Version 2 Protocol |
Specifies the Software Quality Metrics (SQM) Client-to-Service Protocol V2, which is used to send software instrumentation metrics to the SQM service and for the client to download client-specific control data. The protocol extends the concepts of the Software Quality Metrics (SQM) Client-to-Service Protocol, as specified in [MS-SQMCS]. |
|
Specifies the Storage Quality of Service (QoS) Protocol, which is a block-based protocol that is used to manage the Quality of Service configuration of I/O flows targeting remote files accessed over SMB3. |
|
|
[MS-SRPL]: Directory Replication Service (DRS) Protocol Extensions for SMTP |
Specifies the Directory Replication Service (DRS) Protocol Extensions for SMTP. These are extensions to the DRS Protocol for transport over the Simple Mail Transfer Protocol (SMTP), which provide an alternate transport for the DRS protocol that may allow domain controllers to perform replication in environments where the RPC transport mechanism is unsuitable. |
|
Specifies the Server Service Remote Protocol, which remotely enables file and printer sharing and named pipe access to the server through the Server Message Block Protocol. |
|
|
[MS-SSDP]: SSDP: Networked Home Entertainment Devices (NHED) Extensions |
Specifies the Networked Home Entertainment Devices (NHED) Extensions, which detects devices on a home network. These extensions provide a mechanism for a control point to discover a device on the network without requiring the device to implement a complete SSDP stack. |
|
[MS-SSEAN]: Simple Mail Transfer Protocol (SMTP) AUTH Extension for SPNEGO |
Specifies the SMTP Service Extension for Negotiate Authentication, which enables SMTP clients to authenticate to SMTP servers by using the Simple and Protected Negotiate (SPNEGO) mechanism. |
|
Specifies the Secure Socket Tunneling Protocol (SSTP), which is a mechanism to transport data-link layer (L2) frames on a Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) connection. |
|
|
Specifies the Smooth Streaming Protocol, which provides a means of delivering media from servers to clients in a way that can be cached by standard HTTP Cache Proxies in the communication chain. Allowing standard HTTP Cache Proxies to respond to requests on behalf of the server increases the number of clients that can be served by a single server. |
|
|
Specifies the Service Witness Protocol, which enables an SMB2 clustered file server to notify SMB2 clients with prompt and explicit notifications about the failure or recovery of a network name and associated services. |
|
|
Specifies the SOAP over WebSocket Protocol Binding, a binding of SOAP to the WebSocket protocol (as defined in [DRAFT-WSP]), including a WSDL transport URI and supported message exchange patterns (MEPs). It specifies how messages defined by a higher-layer protocol are formed and framed for transport over [DRAFT-WSP]. This specification also defines a WebSocket subprotocol. |
|
|
Specifies the Telephony API Internet Locator Service Protocol, which uses Lightweight Directory Access Protocol (LDAP) requests to retrieve information stored in the Internet Locator Service (ILS) dynamic instance. It is used for communication between a client using the Telephony Application Programming Interface (TAPI) and an ILS server. |
|
|
Specifies the Tethering Control Channel Protocol, which enables the sharing of the network connection for a server with one or more clients. |
|
|
Specifies the Tabular Data Stream Protocol, which is an application layer request/response protocol that facilitates interaction with a database server and provides for authentication and channel encryption negotiation; specification of requests in SQL (including Bulk Insert); invocation of a stored procedure, also known as a Remote Procedure Call (RPC); returning of data; and Transaction Manager Requests. |
|
|
Specifies the Tracing HTTP Correlation Header, which is used to enable correlation between client and server-side traces. |
|
|
Specifies the Transaction Internet Protocol (TIP) Extensions, which is a set of extensions to the standard Transaction Internet Protocol (TIP) Version 3.0, as specified in [RFC2371]. The protocol provides concrete mechanisms for associating an OleTx transaction and a TIP transaction. |
|
|
Specifies the Transport Layer Security (TLS) Profile, which is the authentication option to the Telnet protocol as a generic method for negotiating an authentication type and mode, including determining whether encryption should be used and whether credentials should be forwarded. |
|
|
[MS-TNAP]: Telnet: NT LAN Manager (NTLM) Authentication Protocol |
Specifies the Telnet: NT LAN Manager (NTLM) Authentication Protocol, which is the authentication option to the Telnet protocol as a generic method for negotiating an authentication type and mode, including determining whether encryption should be used and whether credentials should be forwarded. |
|
[MS-TPMVSC]: Trusted Platform Module (TPM) Virtual Smart Card Management Protocol |
Specifies the DCOM Interfaces for Trusted Platform Module (TPM) Virtual Smart Card device management, which are used to manage virtual smart cards (VSCs) on a remote machine. They provide methods for a protocol client to request creation and destruction of VSCs, and to monitor the status of these operations. |
|
Specifies the Telemetry Protocol XML Schema. This schema defines the message structure used by the Software Quality Metrics (SQM) Client-to-Service Protocol V2, specified in [MS-SQMCS2]. The schema is used to send software instrumentation metrics from a client to the SQM service and for the client to download client-specific control data. |
|
|
Specifies the Telephony Remote Protocol, which enables implementation of communications applications ranging from voice mail to call centers with multiple agents and switches. |
|
|
Specifies the Task Scheduler Service Remoting Protocol, which is used to register and configure a task and to inquire about the status of tasks that are running on a remote machine. |
|
|
Specifies the Terminal Services Gateway Server Protocol, which is a mechanism to transport data-link layer (L2) frames on a Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS) connection. |
|
|
Specifies the Telnet Server Remote Administration Protocol, which is a set of interfaces used for performing management tasks on a Telnet Server. |
|
|
[MS-TSTS]: Terminal Services Terminal Server Runtime Interface Protocol |
Specifies the Terminal Services Terminal Server Runtime Interface Protocol, which is an RPC-based protocol used for remotely querying and configuring various aspects of a terminal server. |
|
[MS-TSWP]: Terminal Services Workspace Provisioning Protocol |
Specifies the Terminal Services Workspace Provisioning Protocol, which is used for transferring remote resource information from a server to a client. The client can use this resource information to launch resources such as remote applications on a remote server. |
|
Specifies the Telnet: VTNT Terminal Type Format Data Structure, which defines the structures for Telnet VTNT Terminal Type Format, and how the client and server negotiate the use of this format. |
|
|
Specifies the Update Agent Management Protocol, which provides a set of types and interfaces that allows callers to manage an update agent and to invoke some update agent operations, such as an update search. |
|
|
Specifies the User Name Mapping Protocol, which maps Windows domain user and group account names to the POSIX user and group identifiers used in AUTH_UNIX authentication, and vice versa. This enables the association of user names for users who have different identities in Windows-based and UNIX-based domains. |
|
|
[MS-UPIGD]: UPnP Device and Service Templates: Internet Gateway Device (IGD) Extensions |
Specifies the UPnP: Device and Service Templates: Internet Gateway Device (IGD) Extensions. These structure extensions define extensions to the Universal Plug-n-Play (UPnP) device schema that describes an Internet gateway device. |
|
[MS-UPMC]: UPnP Device and Service Templates: Media Property and Compatibility Extensions |
Specifies the Microsoft Media Property Extensions (MMPE), the Microsoft Compatibility Extension Flags (MCEF), and the Microsoft Power Management Extensions (MPME) to the Universal Plug and Play (UPnP) interoperability guidelines, as specified by the UPnP Forum [UPnP] and used by the Digital Living Network Alliance (DLNA) [DLNA]. |
|
Specifies the USB Protocol: Platform Detection Extensions protocol based on the USB 3.2 specification and Microsoft OS 2.0 Descriptors. It extends the USB protocol with operating system detection to provide OS platform IDs to USB devices so they can take advantage of an operating system's special drivers and features. |
|
|
Specifies the IPv4 Over IEEE 1394 Protocol Extension, which is the Microsoft extension to the IPv4 over IEEE 1394 protocol to support bridging and clarifies the implementation details as specified in [RFC2734] where necessary. |
|
|
[MS-VAPR]: Virtual Application Publishing and Reporting (App-V) Protocol |
Specifies the virtual applications that a user is entitled to so that these applications can be downloaded and installed on the user's machine. It is also used to report virtual application usage information to the server so that usage information across multiple users can be aggregated to infer broad virtual application usage patterns across an organization. |
|
Specifies the Virtual Disk Service (VDS) Protocol, a set of distributed component object model (DCOM) interfaces for managing the configuration of disk storage. |
|
|
Specifies the Virtual Hard Disk v2 (VHDX) File Format Protocol, the virtual hard disk format that provides a disk-in-a-file abstraction. |
|
|
Specifies the VT-UTF8 and VT100+ Protocols, which are used for point-to-point serial communication for terminal control and headless server configuration. |
|
|
Specifies the W32Time Remote Protocol, which is used for controlling and monitoring a time service on a machine. This RPC interface supports time services that synchronize time using the Network Time Protocol (NTP) Version 3, as specified in [RFC1305], as well as platform-specific hardware time sources. |
|
|
Specifies the Windows Client Certificate Enrollment Protocol, which consists of a set of DCOM interfaces that enable clients to request various services from a certification authority (CA). These services enable X.509 (as specified in [X509]) digital certificate enrollment, issuance, revocation, and property retrieval. |
|
|
[MS-WCFESAN]: WCF-Based Encrypted Server Administration and Notification Protocol |
Specifies the WCF-Based Encrypted Server Administration and Notification Protocol, which enables the protocol client to monitor and manage the protocol server in the same network. |
|
[MS-WDHCE]: Wi-Fi Display Protocol: Hardware Cursor Extension |
Specifies the Wi-Fi Display Protocol: Hardware Cursor Extension, which extends the Miracast v1.1 protocol to provide an additional, low-latency stream suitable for controlling the mouse cursor at a higher update rate. |
|
Specifies the Windows Deployment Services (WDS) Control Protocol, which is an RPC interface that provides the ability to remotely invoke services provided by WDS Server. It is a client/server protocol that uses RPC as a transport. The protocol provides a generic invocation mechanism to send requests to the server and receive replies. |
|
|
[MS-WDSMA]: Windows Deployment Services Multicast Application Protocol |
Specifies the Windows Deployment Services Multicast Application Protocol, which enables clients to join the multicast session at any point during the lifetime of the .multicast session, and still be able to get all pieces of the content. |
|
[MS-WDSMSI]: Windows Deployment Services Multicast Session Initiation Protocol |
Specifies the Windows Deployment Services Multicast Session Initiation Protocol, which describes two mechanisms for the client to request initiation of a Multicast Session from the server. |
|
[MS-WDSMT]: Windows Deployment Services Multicast Transport Protocol |
Specifies the Windows Deployment Services Multicast Transport Protocol, which enables transmission of content to multiple clients using Multicast UDP. |
|
[MS-WDSOSD]: Windows Deployment Services Operation System Deployment Protocol |
Specifies the Windows Deployment Services Operation System Deployment Protocol . This protocol defines services exposed by the WDS Server that are used by the clients to deploy an operating system on a machine. |
|
[MS-WDV]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions |
Specifies the Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions, which extends WebDAV by introducing new headers that both enable the file types that are not currently manageable and optimize protocol interactions for file system clients. These extensions do not introduce new functionality into WebDAV, but instead optimize processing and eliminate the need for special-case processing. |
|
[MS-WDVSE]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extensions |
Specifies the Web Distributed Authoring and Versioning (WebDAV) Protocol: Server Extension, which extends the standard HTTP mechanisms defined in [RFC2068] to provide file access and content management over the Internet. |
|
[MS-WFDAA]: Wi-Fi Direct (WFD) Application to Application Protocol |
Specifies the Wi-Fi Direct (WFD) Protocol: Proximity Extensions, which enable two or more devices that are running the same application to establish a direct connection without requiring an intermediary, such as an infrastructure wireless access point (WAP). |
|
Specifies an extension for the Wi-Fi Display Technical Specification v1.1. Enables latency control, extended diagnostic information, and dynamic format changes on Wi-Fi Display Devices. When implemented, these extensions provide an improved and more consistent Wi-Fi Display experience for a variety of wireless display scenarios, including word processing, web browsing, gaming, and video projection. |
|
|
Specifies the Workflow Instance Management Protocol, which defines a set of SOAP messages for the management of workflow instances, such as suspending, resuming, or canceling an instance. |
|
|
[MS-WINSRA]: Windows Internet Naming Service (WINS) Replication and Autodiscovery Protocol |
Specifies the Windows Internet Naming Service (WINS) Replication and Autodiscovery Protocol, the Microsoft implementation of NetBIOS Name Server (NBNS). This protocol supports resolution of NetBIOS names to IPv4 addresses. |
|
Specifies the Workstation Service Remote Protocol, which remotely queries and configures certain aspects of a Server Message Block network redirector on a remote computer. |
|
|
Specifies the Windows Metafile Format structure. A Windows metafile is a container for an image, which is defined by series of variable-length records, called metafile records. |
|
|
Specifies the Windows Media HTTP Push Distribution Protocol, which is used for transferring real-time multimedia data (for example, audio and video) from a client to a server. |
|
|
[MS-WMI]: Windows Management Instrumentation Remote Protocol |
Specifies the Windows Management Instrumentation Remote Protocol, which uses the Common Information Model (CIM), as specified in [DMTF-DSP004], to represent various components of the operating system. CIM is the conceptual model for storing enterprise management information. |
|
[MS-WMIO]: Windows Management Instrumentation Encoding Version 1.0 Protocol |
Specifies the Windows Management Instrumentation Encoding Version 1.0 Protocol, which is a binary data encoding format used by the Windows Management Instrumentation Remote Protocol, as specified in [MS-WMI], for network communication. |
|
Specifies the Windows Media Log Data Structure, which is a syntax for logging messages. The logging messages specify information about how a client received multimedia content from a streaming server. |
|
|
Specifies the Windows Media HTTP Streaming Protocol, a client/server-based protocol used to stream real-time data between the client (the receiver of streaming data) and server (the sender of streaming data). |
|
|
Specifies the Web Point-and-Print Protocol, which is an HTTP-based protocol that clients use to download printer driver software from a server in the client network or from a Web site. This enables distribution of printer driver software using standard Web technologies. |
|
|
[MS-WSDS]: WS-Enumeration: Directory Services Protocol Extensions |
Specifies the WS-Enumeration Directory Services Protocol Extensions, a set of extensions to the Web Services Enumeration (WS-Enumeration) [WSENUM] protocol for facilitating SOAP-based search operations against directory servers. |
|
[MS-WSH]: Windows Security Health Agent (WSHA) and Windows Security Health Validator (WSHV) Protocol |
Specifies the Windows Security Health Agent (WSHA) and Windows Security Health Validator (WSHV) Protocol, which reports the system security health state. |
|
[MS-WSMAN]: Web Services Management Protocol Extensions for Windows Server 2003 |
Specifies the Web Services Management Protocol Extensions, which is a general purpose, SOAP-based systems management extension that defines procedures for carrying out remote management operations. |
|
[MS-WSMV]: Web Services Management Protocol Extensions for Windows Vista |
Specifies the Web Services Management Protocol Extensions for Windows Vista, which provides Windows Vista extensions to the WS-Management Protocol, the WS-Management Binding Specification, and the WS-CIM Mapping Specification for accessing CIM objects as a Web service. |
|
Specifies the Windows Search Protocol (WSP), which allows a client to communicate with a server hosting a Windows Search service (WSS) to issue queries. |
|
|
Specifies the WebSocket Protocol: Disable Masking Extension, which extends the WebSocket Protocol to improve performance by allowing developers to set a property to disable masking. |
|
|
Specifies the WS-Transfer: Lightweight Directory Access Protocol (LDAP) v3 Controls, also known as WSPELD. This protocol extends the Web Services Enumeration (WS-Enumeration) [WSENUM] and Web Services Transfer (WS-Transfer) [WXFR] protocols. |
|
|
[MS-WSPOL]: Web Services: Policy Assertions and WSDL Extensions |
Specifies a collection of Web service policy assertions, which define domain-specific behavior for the interaction between two Web service entities. |
|
Specifies the Windows System Resource Manager (WSRM) Protocol, a set of Distributed Component Object Model (DCOM) interfaces for managing the configuration of processor, memory resources, and accounting functions on a server. |
|
|
[MS-WSRVCAT]: WS-AtomicTransaction (WS-AT) Version 1.0 Protocol Extensions |
Specifies the WS-AtomicTransaction (WS-AT) Version 1.0 Protocol Extensions, which extends the WS-AtomicTransaction protocol by enabling WS-AtomicTransaction initiators, participants, and coordinators to participate in transactions coordinated by OleTx transaction managers. |
|
[MS-WSRVCRM]: WS-ReliableMessaging Protocol: Advanced Flow Control Extension |
Specifies the WS-ReliableMessaging Protocol: Advanced Flow Control Extension, which is an advanced message flow control extension to the Web Services Reliable Messaging Protocol [WSRM1-0] [WSRM1-1]. |
|
[MS-WSRVCRR]: WS-ReliableMessaging Protocol: Reliable Request-Reply Extension |
Specifies the WS-ReliableMessaging Protocol: Reliable Request-Reply Extension. This extension assumes the use of duplex underlying protocols in order to provide support for applications designed to interact using a request-response message exchange pattern. The request-reply extension enables these applications to communicate reliably over transfer protocols that support only SOAP Request-Response. |
|
[MS-WSTC]: WS-Discovery: Termination Criteria Protocol Extensions |
Specifies the WS-Discovery: Termination Criteria Protocol Extensions. This extends the WS-Discovery protocol for sending and receiving termination criteria as part of WS-Discovery Probe and Resolve messages. |
|
Specifies the WS-Trust X.509v3 Token Enrollment Extensions, also known as WSTEP. The protocol specification defines the message formats and server behavior for the purposes of certificate enrollment. |
|
|
[MS-WSTIM]: WS-Transfer: Identity Management Operations for Directory Access Extensions |
Specifies the WS-Transfer: Identity Management Operations for Directory Access Extensions, a set of extensions to the WS-Transfer protocol [WXFR] for representing the protocol operations commonly used for directory access in identity management protocols. |
|
[MS-WSUSAR]: Windows Server Update Services: Administrative API Remoting Protocol (WSUSAR) |
Specifies the Windows Server Update Services: Administrative API Remoting Protocol (WSUSAR), which enables communication between the Windows Server Update Services (WSUS) management API and a WSUS server. |
|
[MS-WSUSSS]: Windows Update Services: Server-Server Protocol |
Specifies the Windows Update Services: Server-Server Protocol, which enables a hierarchically organized collection of servers to synchronize metadata and content associated with software updates over the Internet by using SOAP and HTTP protocols. |
|
Specifies the Windows Update Services: Client-Server Protocol, which enables machines to discover and download software updates over the Internet using the SOAP and HTTP protocols. |
|
|
Specifies the three variants of the Xpress Compression Algorithm: LZ77+Huffman, Plain LZ77, LZNT1, and their respective decompression algorithms. This algorithm efficiently compresses data that contains repeated byte sequences. It is not designed to compress image, audio, or video data. Between the trade-offs of compressed size and CPU cost, it heavily emphasizes low CPU cost. |
|
|
Specifies the X.509 Certificate Enrollment Policy Protocol. This protocol defines the interactions between a requesting client and a responding server for the exchange of a certificate enrollment policy, which is the collection of certificate templates and certificate issuers available to the requestor for X.509 certificate enrollment. |
|
|
Specifies the XML-binary Optimized Packaging (XOP) Profile, which provides extensions that enable more efficient implementations of [XML-XOP] to be built by requiring certain ordering of the MIME parts in the XOP package |
|
|
[MS-XUSBI]: Xbox Universal Serial Bus Protocol (XUSB) Interface Extension |
Specifies the Xbox Universal Serial Bus Protocol (XUSB) Interface Extension of the USB 2.0 interface that provides extended semantics for interaction between game controller devices and a host. This protocol includes enumeration of device capabilities, determining of device type and subtype, transfer of gamepad and voice data, and support for an expansion device on the controller. |