technical content. 8/29/2008 3.1.1 Editorial Changed language and formatting in the technical content. 10/24/2008 3.1.2 Editorial Changed language and formatting in the technical content. 12/5/2008 4.0 Major Updated and revised the technical content. 1/16/2009 4.0.1 Editorial Changed language and formatting in the technical content. 2/27/2009 4.0.2 Editorial Changed language and formatting in the technical content. 4/10/2009 4.0.3 Editorial Changed language and formatting in the technical content. 5/22/2009 5.0 Major Updated and revised the technical content. 7/2/2009 5.0.1 Editorial Changed language and formatting in the technical content.
8/14/2009 5.0.2 Editorial Changed language and formatting in the technical content. 9/25/2009 5.1 Clarified the meaning of the technical content. 11/6/2009 5.1.1 Editorial Changed language and formatting in the technical content. 12/18/2009 5.1.2 Editorial Changed language and formatting in the technical content. 1/29/2010 6.0 Updated and revised the technical content. 3/12/2010 6.0.1 Editorial Changed language and formatting in the technical content. 4/23/2010 7.0 Updated and revised the technical content. 6/4/2010 8.0 Major Updated and revised the technical content. 7/16/2010 8.0 None No changes to the meaning, language, or formatting
of the technical content. 8/27/2010 9.0 Major Updated and revised the technical content. 10/8/2010 9.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 9.1 Minor Clarified the meaning of the technical content. 1/7/2011 9.1 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 9.1 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 9.1 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 9.1 None No changes to the meaning, language, or formatting
of the technical content. 6/17/2011 9.2 Minor Clarified the meaning of the technical content. 9/23/2011 9.2 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 9.2 None No changes to the meaning, language, or formatting of the technical content. 3/30/2012 9.2 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 9.2 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 9.2 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 9.2 None No changes to the
meaning, language, or formatting of the technical content. 8/8/2013 10.0 Major Updated and revised the technical content. 11/14/2013 11.0 Major Updated and revised the technical content. 2/13/2014 11.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 11.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 12.0 Significantly changed the technical content. 7/14/2016 12.0 None No changes to the meaning, language, or formatting of the technical content.
... RecordTypeEnum (1 byte): A value that identifies the record type. The value MUST be 0x10. ObjectId (4 bytes): An INT32 value ( section 2.2.22) that uniquely identifies the array instance in the serialization stream. The ID MUST be a positive integer. Length (4 bytes): An INT32 value ([MS-DTYP] section 2.2.22) that specifies the number of items in the array. The value MUST be 0 or a positive integer. Values (variable): A sequence of data values contained in the array. Each data value MUST be one of the record types defined in sections , , and . Member Reference Records MemberPrimitiveTyped The MemberPrimitiveTyped record contains a primitive type value other than a string. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 RecordTypeEnum PrimitiveTypeEnum Value (variable) ... RecordTypeEnum (1 byte): A that identifies the record type. The value MUST be 0x08. PrimitiveTypeEnum (1 byte): A RecordTypeEnumeration value that specifies the primitive type of data that is being transmitted. This field MUST NOT contain a value of 0x11 (Null) or 0x12 (String). Value (variable): The value whose type is inferred from the field, as specified in the table in section 2.3.2.3. MemberPrimitiveUnTyped The MemberPrimitiveUnTyped record is the most compact record to represent a primitive type This type of record does not have a to indicate the record type. The record MUST be used when a class record member value is a primitive type. Because the containing class specifies the primitive type of each member, the primitive type is not re-specified along with the value. Also, the primitive values cannot be referenced by any other record; therefore it does not require an ObjectId. This record has no field besides the value. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 Value (variable) ... Value (variable): A primitive type value, other than a string.
... RecordTypeEnum (1 byte): A value that identifies the record type. Its value MUST be 0x04. ObjectId (4 bytes): An INT32 value ( section 2.2.22) that uniquely identifies the object in the serialization stream. An implementation MAY use any algorithm to generate the unique ID. If the ObjectId is referenced by a record elsewhere in the serialization stream, the ObjectId MUST be positive. If the ObjectId is not referenced by any MemberReference in the serialization stream, then the ObjectId SHOULD be positive, but MAY be negative. ClassName (53 A identifying the class name. Its value MUST be "System.Runtime.Remoting.Messaging.LogicalCallContext". MemberCount (4 bytes): An INT32 value ([MS-DTYP] section 2.2.22) that specifies the number of members in this type. Its value MUST be 0x00000000. Principal The Principal record contains information a user that was discovered while checking group membership. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 RecordTypeEnum ObjectId ... ClassName (62 bytes) ... ... ... MemberCount ... MemberName1 (22 bytes) ... ... ... MemberName2 (17 ... ... ... MemberName3 (16 ... ... ... MemberName4 (19 bytes)
LicensorCertChain Complex Type The LicensorCertChain complex type contains the responder's SLC <s:complexType name="LicensorCertChain"> <s:sequence> <s:element minOccurs="0" maxOccurs="1" name="CertificateChain" type="tns:ArrayOfXmlNode" /> </s:sequence> </s:complexType> CertificateChain: Contains the responder's SLC as an array of XML nodes. It MUST follow the schema in section . ArrayOfXmlNode Complex Type The ArrayOfXmlNode complex type contains an SLC certificate chain. <s:complexType name="ArrayOfXmlNode"> <s:sequence> <s:element minOccurs="0" maxOccurs="unbounded" name="Certificate" nillable="true"> <s:complexType <s:sequence> <s:any /> </s:sequence> </s:complexType> </s:element> </s:sequence> </s:complexType> Certificate: XML that contains the SLC certificate chain. Timer Events None. Other Local Events None. GroupExpansionWebServiceSoap Server Details An RMS server can be requested to issue a for content that has been published with a policy that specifies a group in a forest that the RMS server cannot contact. In this case, the RMS server needs to contact the appropriate RMS server for that forest and request it to verify group membership. This communication SHOULD use the GroupExpansionWebServiceSoap port type. This communication MAY use the interface. RMS version 1.0 and RMS version 1.0 SP1 use the Binary Expansion interface. RMS version 1.0 SP2 supports both the Binary Group Expansion interface and the GroupExpansionWebServiceSoap port type. It will use the GroupExpansionWebServiceSoap interface whenever possible. RMS version 2.0 supports only the GroupExpansionWebServiceSoap interface. The GroupExpansionWebServiceSoap port type provides one operation: .