Groups None. Attribute Groups None. Common Data Structures This section describes the way the RMS: Client-to-Server Protocol utilizes for certificates and licenses. Common Certificate and License Structures This section describes in detail common elements of RMS certificate formats. All elements MUST follow the schema. ISSUEDTIME The ISSUEDTIME element specifies the time that a certificate or license was generated, expressed in . ISSUEDTIME is specified in the XrML Document Type Definition (DTD). All certificates and licenses MUST contain an ISSUEDTIME element. An ISSUEDTIME element MUST follow this template. <ISSUEDTIME> [[- issuedtime -]] </ISSUEDTIME> [[- issuedtime -]]: The time at the certificate or license was generated, expressed in UTC. VALIDITYTIME VALIDITYTIME is an optional element that specifies the time period in which a certificate or license can be used. The certificate or license MUST be considered invalid outside this time period. The time period is a half-closed interval in which the start time is included in the set but the end time is not. A certificate or license SHOULD contain a VALIDITYTIME element. A VALIDITYTIME element MUST use the following template. <VALIDITYTIME> <FROM>[[- starttime -]]</FROM> <UNTIL>[[- endtime -]]</UNTIL> </VALIDITYTIME> [[- starttime -]]: The beginning of the time interval in the certificate is allowed to be considered valid, expressed in UTC. [[- endtime -]]: The end of the time interval in which the certificate is allowed to be considered valid, expressed in UTC. RANGETIME
The server SHOULD validate the element of the request. If the MinimumVersion element or the MaximumVersion element do not contain a version number (specified in section 2.2.4.2), the server SHOULD return a Microsoft.DigitalRightsManagement.Core.MalformedDataVersionException fault. If the MaximumVersion element contains a version number that is higher than the range supported by the server for the operation, the server SHOULD return a Microsoft.DigitalRightsManagement.Core.UnsupportedDataVersionException. If any input element that is required for successful processing of the operation is set to null, the server SHOULD return a System.ArgumentNullException fault. Cryptographic Modes RMS servers MAY<35> support operating in multiple cryptographic modes. These modes define the set of key sizes and hash algorithms that clients and servers use in XrML certificates. Two modes are defined, named Mode 1 and Mode 2. Servers that do not support multiple cryptographic modes SHOULD use key sizes and hash algorithms specified for Mode 1. The following table specifies the differences between certificates in each of the cryptographic modes. Certificate Mode 1 Mode 2 SLC The public key is 1,024-bit RSA. The signature hash algorithm is SHA-1. The public key is 2,048-bit RSA. The signature hash algorithm is SHA256. SLC Chain Intermediate and Root Certificates The public key is 1,024-bit or RSA. The signature hash algorithm is SHA-1. The public key is 2,048-bit RSA. The signature hash algorithm is SHA256. SPC The public key is 1,024-bit or RSA. The signature hash algorithm is SHA-1. The public key is 2,048-bit RSA. The signature hash algorithm is SHA256. SPC Chain Intermediate and Root Certificates The public key is 1,024-bit or RSA. The signature The public key is 2,048-bit RSA. The signature hash algorithm
hash algorithm is SHA-1. is SHA256. RAC The public key is 1,024-bit RSA. The signature hash algorithm is SHA-1. The enabling bits type is The public key is 2,048-bit RSA. The signature hash algorithm is SHA256. The enabling bits type is CLC The public key is 1,024-bit RSA. The signature hash algorithm is SHA-1. The enabling bits type is The public key is 2,048-bit RSA. The signature hash algorithm is SHA256. The enabling bits type is PL The signature hash algorithm is SHA-1. The enabling bits type is The signature hash algorithm is SHA256. The enabling bits type is UL The signature hash algorithm is SHA-1. The enabling bits type is The signature hash algorithm is SHA256. The enabling bits type is
Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces. Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire. The changes made to this document are listed in the following For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type KeyHeader Updated content for Windows 10 and Windows Server 2016 Technical Preview. Y Content update. Server Endpoint URLs Documented the GetServerInfo operation. Y New content added. GetServerInfo Operation New operation added. Y New content added. Messages Added content for the GetServerInfo operation. Y New content added. GetServerInfoSoapIn content for the GetServerInfo operation. Y New content GetServerInfoSoapOut Added content for the GetServerInfo operation. Y New content added. Elements Added content for the GetServerInfo operation. Y New content added. GetServerInfo Added content for the GetServerInfo operation. Y New content added. GetServerInfoResponse Added content for the GetServerInfo operation. Y New content added. Complex Types Added content for the GetServerInfo operation. Y New content added. ArrayOfServerInfoRequest Added content for the GetServerInfo operation. Y New content added. ServerInfoRequest Added content for the GetServerInfo operation. Y New content
GetServerInfoResponse Added content for the GetServerInfo operation. Y New content added. Simple Types Added content for the GetServerInfo operation. Y New content added. ServerInfoType Added content for the GetServerInfo operation. Y New content added. GetServerInfoResponse Example Added example of GetServerInfoResponse element. Y New content added. Appendix B: Product Behavior Updated the product applicability list and product behavior to include Windows 10 operating system. Y Content update. 7 Appendix B: Product Behavior Updated the product behavior notes to include the Windows Server 2016 Technical Preview operating system. Y Content update.
Index A Abstract data model 95 101 155 132 107 122 server ( 81, 95, 101, 107, 122, 132, 143) 143 164 166 187 ActivationProxyWebServiceSoap server 95 95 100 95 95 95 100 95 31 22 27 138 28 28 AUTHENTICATEDDATA ( 59, 67, 79) 90 B Bootstrapping client ( 20, 159) C 23 35 25 169 28 25 Certificates 52 38 48 45 189 CertificationWebServiceSoap Server 101 101 107 101 101 101 106 101 Chains 35 35 87 215 Client 155 bootstrapping ( 20, 159) 157 161 158 81 158 161 157 52 28 26 27 27 73 CONDITIONLIST ( 44, 60, 73) 92 94 D Data model - abstract 95 101 155 132 107 122 server ( 81, 95, 101, 107, 122, 132, 143) 143 DESCRIPTOR ( 29, 39, 46, 49, 53, 57, 62, 68, 75) 79 DISTRIBUTIONPOINT ( 30, 45, 47, 50, 54, 58, 63, 70, 76) E Elements 25 25 26 26 26 26 25 79 33
61 91 Enrollment 138 20 133 205 EnrollServiceSoap Server 132 132 143 133 133 143 132 Events 161 - server ( 100, 107, 122, 132, 143, 155) 161 timer - server ( 100, 106, 122, 132, 143, 155) Examples 164 169 162 166 168 95 F 93 51 23 187 187 189 205 191 197 201 G 12 28 I 186 186 186 18 Initialization 95 101 157 132 107 122 server ( 87, 95, 101, 107, 122, 132, 143) 143 12 ISSUEDPRINCIPALS ( 31, 42, 47, 51, 55, 58, 69) 28 ISSUER ( 29, 39, 46, 49, 53, 57, 63, 69, 75) 38 K 34 L License 55 67 35 28 LicenseSoap and TemplateDistributionWebServiceSoap Server 107 107 122 107 107 107 122 107 Licensing ( 21, 161) 191 Local events 100 107 161 143 122 132 server ( 95, 100, 107, 122, 132, 143, 155) 155 M 26 Message processing 95 101 158 133 107 122 server ( 89, 95, 101, 107, 122, 133, 143) 143 Messages 27 28 28 25 25