11/30/2007 1.2.7 Editorial Changed language and formatting in the technical content. 1/25/2008 1.2.8 Editorial Changed language and formatting in the technical content. 3/14/2008 1.2.9 Editorial Changed language and formatting in the technical content. 5/16/2008 1.2.10 Editorial Changed language and formatting in the technical content. 6/20/2008 1.3 Minor Clarified the meaning of the technical content. 7/25/2008 1.3.1 Editorial Changed language and formatting in the technical content. 8/29/2008 1.3.2 Editorial Changed language and formatting in the technical content. 10/24/2008 1.3.3 Major Updated and revised the technical content. 12/5/2008 2.0 Major Updated and revised
the technical content. 1/16/2009 3.0 Major Updated and revised the technical content. 2/27/2009 4.0 Major Updated and revised the technical content. 4/10/2009 4.1 Minor Clarified the meaning of the technical content. 5/22/2009 4.2 Minor Clarified the meaning of the technical content. 7/2/2009 4.2.1 Editorial Changed language and formatting in the technical content. 8/14/2009 4.2.2 Editorial Changed language and formatting in the technical content. 9/25/2009 4.3 Clarified the meaning of the technical content. 11/6/2009 4.3.1 Editorial Changed language and formatting in the technical content. 12/18/2009 4.3.2 Editorial Changed language and formatting
in the technical content. 1/29/2010 4.4 Minor Clarified the meaning of the technical content. 3/12/2010 4.4.1 Editorial Changed language and formatting in the technical content. 4/23/2010 5.0 Major Updated and revised the technical content. 6/4/2010 5.1 Minor Clarified the meaning of the technical content. 7/16/2010 5.1 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 5.1 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 5.1 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 5.1 None No changes to the
Vendor-Extensible Fields This protocol uses s as specified in section 2.1. Vendors can define their own HRESULT values, provided that the C bit (0x20000000) is set for each vendor-specific value. Standards Assignments The following is a table of well-known in this protocol. Parameter Reference identifier, identifier, and identifier (guidTransactionProperty) section A.2.5 identifier (guidActivityProperty) [C706] section A.2.5 identifier and identifier (guidSecurityProperty) [C706] section A.2.5 identifier (guidUserPropertiesProperty) [C706] section A.2.5 OBJREF_CUSTOM unmarshaler for (CLSID_CFW) [C706] section A.2.5 OBJREF_CUSTOM unmarshaler for User-Defined Context Property (CLSID_UserContextProperty) [C706] section A.2.5 OBJREF_CUSTOM unmarshaler CLSID for Transaction Context Property (CLSID_TransactionUnmarshal) [C706] section A.2.5 OBJREF_CUSTOM unmarshaler CLSID for Activity Context Property (CLSID_ActivityUnmarshal) [C706] section A.2.5 Unmarshaling CLSID for the Security Envoy Property (CLSID_SecurityEnvoy) [C706] section A.2.5 Unmarshaling for the Transaction Envoy Property (CLSID_TransactionEnvoy) [C706] section A.2.5 interface UUID for (IID_ITransactionStream) [C706] section A.2.5
Security Property Types The following table lists the valid Security Property Types for the PropertyType field of the Security Property structure. See . Type Size field of Security Property Data of Security Property 0x0b01 or 0x0b06 MUST be set to the number of bytes in the Data field rounded to a multiple of 4. MUST be an array of bytes specifying the of the caller. The array MUST be padded to a multiple of 4. If the value is 0x0b01, the Data field MUST contain a SID obtained by authenticating the caller using DCOM/RPC authentication mechanisms. If the value is 0x0b06, the Data field MUST contain a SID supplied by an application or a higher-level protocol. The collectionType field of the MUST be set to 0x0a02. 0x0b02 or 0x0b07 MUST be set to the number of in the Data field rounded to a multiple of 4. MUST be an array of Unicode characters that specifies the Windows NT account name of the caller. The array MUST be terminated with the NULL Unicode character and MUST be padded to a multiple of 4. If the is 0x0b02, the Data field MUST contain a Windows NT account name obtained by authenticating the caller using DCOM/RPC authentication mechanisms. If the value is 0x0b07, the Data field MUST contain a Windows NT account name supplied by an application or a higher-level protocol. The collectionType of the security property collection header (section 2.2.3.2.2) MUST be set to 0x0a02. 0x0b03 MUST be set to 0x0004. MUST be a that MUST contain the RPC authentication service value used in the ORPC call. For more details on RPC authentication services, see section 2.2.1.1.8. The collectionType field of the security property collection header (section 2.2.3.2.2) MUST be set to 0x0a02.
0x0b04 MUST be set to 0x0004. MUST be a DWORD that MUST contain the RPC authentication level value used in the ORPC call. For more details on RPC authentication levels, see [MS-RPCE] section 2.2.1.1.8. The collectionType field of the security property collection header (section 2.2.3.2.2) MUST be set to 0x0a02. 0x0b05 MUST be set to 0x0004. MUST be a that MUST contain the RPC impersonation level value used in the ORPC call. The collectionType field of the security property collection header (section 2.2.3.2.2) MUST be set to 0x0a02. 0x0b10 MUST be set to 0x0004. MUST be a DWORD that contains the minimum of the RPC authentication level values used across all the calls in the ORPC call chain. For more details on RPC authentication levels, see [MS-RPCE] section 2.2.1.1.8. The collectionType field of the security property collection header (section 2.2.3.2.2) MUST be set to 0x0a01. Security Property Collection Header The Security Property Collection Header structure specifies the header of a collection. 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 collectionType cProperties collectionType (2 An unsigned short that MUST contain one of the following values:
Index A Abstract data model 42 44 43 55 69 51 67 44 70 41 39 70 48 63 50 49 66 62 46 64 58 50 21 Activations 13 13 14 18 Activity activation - client 42 43 43 43 43 43 Activity activation - server 48 48 48 48 49 48 24 24 19 C 19 80 factory wrapper activation - client 44 45 45 45 46 45 Class factory wrapper activation - server 50 50 50 50 51 50 36 Client activity activation 42 43 43 43 43 43 43 Client class factory wrapper activation 44 45 46 45 45 46 45 13 Client partition activation 43 43 44 43 43 44 43 Client security ORPC extension 55 55 57 55 55 57 55 Client security unmarshaling 69 69 69 69 69 69 69 74 74 Client transaction ORPC extension 51 52 54 52 53 52 53 54 52 Client transaction unmarshaling 67 67 68
68 68 68 67 Client user property activation 44 44 44 44 44 44 44 21 38 26 Context properties 13 15 13 D Data model - abstract 42 44 43 55 69 51 67 44 70 41 70 48 63 50 49 66 62 46 64 58 50 21 21 Diagram client transaction ORPC extension 53 53 14 15 16 17 38 E Events 73 73 74 74 F 19 78 G 70 71 72 73 10 I 78 77 77 12 Initialization 43 45 43 55 69 52 67 44 70 42 40 70 48 63 50 49 66 62 46 65 58 50 10 ITransactionStream server 70 70 73 70 70 73 70 70 71 72 73 L 21 Local events 43 46 44 57 69 54
68 73 42 73 49 64 51 50 66 63 46 66 62 50 M 14 Message processing 43 45 43 55 69 52 68 44 70 42 40 70 48 63 50 49 66 63 46 65 58 50 Messages 21 21 21 Methods 70 71 72 73 17 N 17 Non-root transaction object activation 41 42 42 42 42 42 42 12 O 34 15 Overview 39 44 40 40 40 41 39 12 P 77 Partition activation - client 43 43 43 43 44 43 Partition activation - server 49 49 49 49 49 49 18 19 19 79 Protocol Details 39 14 R 12 12 12 19 16 S Security 77 30 77 31 18 Security marshaling - server 66 66 66 66 66 66 Security ORPC extension - client 55 55
55 55 57 55 Security ORPC extension - server 62 62 63 63 63 62 Security unmarshaling - client 69 69 69 69 69 69 35 33 31 33 Sequencing rules 43 45 43 55 69 52 68 44 70 42 40 70 48 63 50 49 66 63 46 65 58 50 Server 70 70 70 71 72 73 73 70 70 73 70 Server - ITransactionStream 70 70 70 70 73 70 Server activity activation 48 48 49 48 48 49 48 Server activity ORPC processing 63 63 64 63 63 64 63 Server class factory wrapper activation 50 50 51 50 50 51 50 Server partition activation 49 49 50 49 49 49 49 Server security envoy marshaling 66 66 66 66 66 66 66 Server security ORPC extension 62 62 63 63 63 63 62 Server transaction activation 46 46 46 46 46 46 46 Server transaction marshaling 64 65 66 65 65 65 65 Server transaction ORPC extension
58 58 62 58 58 62 58 Server user property activation 50 50 50 50 50 50 50 19 T Timer events 43 46 44 57 69 54 68 44 73 42 41 73 49 64 51 49 66 63 46 65 62 50 Timers 43 45 43 55 69 52 67 44 70 42 39 70 48 63 50 49 66 62 46 65 58 50 80 Transaction 41 41 42 Transaction activation - server 46 46 46 46 46 46 22 38 18 Transaction marshaling - server 64 65 65 65 65 Transaction object activation - non-root 41 42 42 42 42 42 42 27 Transaction ORPC extension - client 51 52 52 52 54 52 Transaction ORPC extension - server 58 58 58 58 62 58 27 29 16 Transaction unmarshaling - client 67 67 68 68 68 67 34 23 22 28 27 28 29 30 Transactions 17 17