2.2 Protocol Summary

The following table provides a comprehensive list of the RMS protocols.

Protocol name

Description

Short name

Rights Management Services (RMS): Client-to-Server Protocol

This protocol obtains and issues certificates and licenses that are used for creating and working with protected content.

The Rights Management Services (RMS): Client-to-Server Protocol is used for all client and server communication in relation to bootstrapping a client, consuming protected content, or protecting content.

This protocol uses SOAP ([SOAP1.1] or [SOAP1.2-1/2007]) over HTTP [RFC2616]. HTTPS support is recommended; however, it is only required when using the Web Browser Federated Sign-on Protocol [MS-MWBF] in conjunction with the Licensing or Certification interfaces.

[MS-RMPR]

Rights Management Services (RMS): Server-to-Server Protocol

This protocol locates RMS services, enrolls servers in RMS, and performs group expansion.

The Rights Management Services (RMS): Server-to-Server Protocol is used for communication between RMS servers in relation to finding service locations and group expansion, and for enrolling subordinate RMS servers.

This protocol uses SOAP over HTTP. HTTPS support is recommended, but not required. Binary group expansion uses the HTTP transport.

[MS-RMPRS]

Rights Management Services (RMS): ISV Extension Protocols

This protocol communicates information between applications and RMS servers directly without using the RMS client. (ISV extensions are not supported in Windows 2000 operating system.)

The Rights Management Services (RMS): ISV Extension Protocols are used for scenarios that are not supported by the RMS: Client-to-Server Protocol in relation to decommissioning protected content, precertifying users, prelicensing content, and republishing content.

These protocols use SOAP over HTTP. HTTPS support is recommended, but not required.

[MS-RMSI]