Revision Summary Date Revision History Revision Class Comments 10/22/2006 0.01 New Version 0.01 release 1/19/2007 1.0 Major Version 1.0 release 3/2/2007 1.1 Minor Version 1.1 release 4/3/2007 1.2 Minor Version 1.2 release 5/11/2007 1.3 Minor Version 1.3 release 6/1/2007 1.3.1 Editorial Changed language and formatting in the technical content. 7/3/2007 1.3.2 Editorial Changed language and formatting in the technical content. 7/20/2007 1.3.3 Editorial Changed language and formatting in the technical content. 8/10/2007 2.0 Added new content. 9/28/2007 2.0.1 Editorial Changed language and formatting in the technical content. 10/23/2007 2.1 Minor new content. 11/30/2007 2.1.1 Editorial Changed language and formatting in the
2/27/2009 7.0 Major Updated and revised the technical content. 4/10/2009 8.0 Major Updated and revised the technical content. 5/22/2009 8.0.1 Editorial Changed language and formatting in the technical content. 7/2/2009 9.0 Major Updated and revised the technical content. 8/14/2009 10.0 Major Updated and revised the technical content. 9/25/2009 11.0 Updated and revised the technical content. 11/6/2009 11.0.1 Editorial Changed language and formatting in the technical content. 12/18/2009 12.0 Major Updated and revised the technical content. 1/29/2010 12.1 Minor Clarified the meaning of the technical content. 3/12/2010 13.0 Major Updated and revised the
technical content. 4/23/2010 14.0 Major Updated and revised the technical content. 6/4/2010 15.0 Major Updated and revised the technical content. 7/16/2010 16.0 Major Updated and revised the technical content. 8/27/2010 17.0 Major Updated and revised the technical content. 10/8/2010 18.0 Major Updated and revised the technical content. 11/19/2010 19.0 Major Updated and revised the technical content. 1/7/2011 20.0 Major Updated and revised the technical content. 2/11/2011 21.0 Major Updated and revised the technical content. 3/25/2011 22.0 Updated and revised the technical content. 5/6/2011 23.0 Major Updated and revised the technical content.
6/17/2011 23.1 Minor Clarified the meaning of the technical content. 9/23/2011 23.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 24.0 Major Updated and revised the technical content. 3/30/2012 24.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 24.1 Minor Clarified the meaning of the technical content. 10/25/2012 25.0 Major Updated and revised the technical content. 1/31/2013 25.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 26.0 Major Updated and revised the technical content. 11/14/2013 27.0 Updated and revised
the technical content. 2/13/2014 27.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 27.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 28.0 Major Significantly changed the technical content. 10/16/2015 28.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 28.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 29.0 Major Significantly changed the technical content.
of the encodings in chapter 12. specification in sections and . Implementations support the Authentication Verifier encodings, as specified in chapter 13. Conforms except as noted in section . Implementations support the rules and encodings for , as specified in chapter 14. Conforms except noted in this specification in sections 2.2.4 through 2.2.7, 3.1.1.5, 3.1.2.5.1, , and . Implementations support the syntax, semantics, and encoding for , as specified in appendix A. Conforms except noted in this specification in section . Implementations support the naming and semantics for protocol sequence strings, as specified in appendix B. Conforms except where noted in this specification in section . Implementations support the naming and semantics for the name_syntax arguments, as specified in appendix C. Extensions to name services are documented in Implementations support the naming and semantics for security parameters, as specified in appendix D. Remote Procedure Call extensions does not implement the authentication scheme specified in Appendix D of [C706]. Remote Procedure Call extensions security and authentication is specified in section , with additional security provider details in section and modifications to rpc_c_authn_dce_secret in section .
Implementations support the naming and encodings for comm_status and fault_status, as specified in appendix E. Conformant with respect to status codes sent between network nodes, but not conformant with respect to status codes returned to the higher-layer protocol. The status codes returned to the higher-layer protocol are specified in section . Implementations support the mapping from IDL types to NDR types, and from NDR types to defined International Organization for Standardization (ISO) C types, as specified in appendix F. Conforms IDL to NDR mappings conform with [C706] except where noted in section , where Remote Procedure Call extensions extends the specification with new types. Implementations support the portable character set, as specified in appendix G. Conforms. Implementations use the as specified in appendix H, for the corresponding protocols. Conforms for TCP/IP and UPD transports (NCACN_IP_TCP and NCADG_IP_UDP). transports use other ports as specified in section 2.1. Implementations adhere to the for assignment, as specified in appendix I. Not conformant, as specified in this specification in section 2.1. Implementations adhere to the mappings for directory service attributes, as specified in the DCE: Directory Services specification. Remote Procedure Call extensions is not an implementation or extension of DCE: Directory Services. Implementations provide defaults for the protocol machine values This specification redefines the protocol state machines that are specified in [C706], in
specified in appendix K. sections 3.2.1.1.1, 3.2.2.1, 3.2.3.1, 3.3.2, and 3.3.3. Some specific values from appendix K are used in this specification where noted. Implementations obey the special encoding rules specified in appendix L. Conforms. Implementations support the syntax and semantics of the dce_error_inq_text routine specified in appendix M. Conforms. Implementations adhere to the mappings for transfer syntax UUIDs, as specified in appendix N. Conforms except noted in this specification in section and . Remote Procedure Call extensions uses an NDR64 transfer syntax UUID (section 2.2.5.1) which modifies section 2.3 of [C706] "Binding" and adds addition UUID_type_identifiers to the list specified in Appendix I. Implementations support the endpoint mapper semantics, as specified in appendix O. Conforms except where noted in this specification in section . Implementations support the conversation manager semantics, as specified in appendix P. Conforms except where noted in this specification in section . Implementations support the remote management semantics, as specified in appendix Q. Conforms except where noted in this specification in section .
Index [ [C706] requirements - RPC extensions conformance to 171 165 171 163 _ 59 59 __int3264 ( 59, 74) 59 59 6 63 63 A Abstract data model client - connectionless RPC ( 71, 80, 85, 91) client - connection-oriented RPC ( 71, 80, 112, 124) 85 server - connectionless RPC ( 71, 83, 85, 101) server - connection-oriented RPC ( 71, 83, 112, 131) 85 ACK 100 100 Additional limitations ( 77, 77) 46 33 27 60 60 64 36 149 149 Authentication tokens ( 49, 58) B 46 74 55 56 62 C 60 27 172 Client - connectionless RPC abstract data model ( 71, 80, 85, 91) triggered events 86 89 99 73 73 81 initialization ( 73, 81, 86, 96) local events ( 80, 81, 91, 101) message processing ( 74, 81, 89, 99, 99, 99) 100 100 100 100 100 100 100 99 100 sequencing rules ( 74, 81, 89, 99, 99, 99) 100 100 100 100 100 100 100 99 100 timer events ( 80, 91, 101) timers ( 73, 81, 86, 95) Client - connection-oriented RPC abstract data ( 71, 80, 112, 124) higher-layer triggered events 73 114 73 127 128 81 initialization ( 73, 81, 114, 127) local events ( 80, 81, 123, 130) message processing ( 74, 81, 114, 129) 123 sequencing ( 74, 81, 114, 129) timer events ( 80, 122, 129) timers ( 73, 81, 114, 126) Common types 35 35 68 69 64 61 64 65 145 71 84 56
56 Connectionless RPC transports 35 38 43 34 34 145 34 71 44 Connection-oriented RPC transports 35 38 43 29 34 Constants 35 35 64 60 146 74 75 D Data model - abstract client - connectionless RPC ( 71, 80, 85, 91) client - connection-oriented RPC ( 71, 80, 112, 124) server - connectionless RPC ( 71, 83, 85, 101) server - connection-oriented RPC ( 71, 83, 112, 131) Data types NDR64 ( 64, 64) E 67 38 42 42 42 39 42 41 42 39 Examples 145 145 146 140 143 140 142 147 147 61 35 74 F FACK message processing 100 100 100 100 57 28 150 150 G 13 H Higher-layer triggered events client - connectionless RPC 86 89 99 73 73 81 client - connection-oriented RPC 73 114 73 127 128 81 server - connectionless RPC 86 89 73 106 106 73 83 106 83 server - connection-oriented RPC 73 114 135 73 135 83 135 83 I 150 59 59 37 149 149 149 149 149
149 149 74 18 Initialization client - connectionless RPC ( 73, 81, 86, 96) client - connection-oriented RPC ( 73, 81, 114, 127) server - connectionless RPC ( 73, 83, 86, 106) server - connection-oriented RPC ( 73, 83, 114, 134) 13 L Local events client - connectionless RPC ( 80, 81, 91, 101) client - connection-oriented RPC ( 80, 81, 123, 130) server - connectionless RPC ( 80, 84, 91, 111) server - connection-oriented RPC ( 80, 84, 123, 138) M 43 35 Message processing client - connectionless RPC ( 74, 81, 89, 99, 99, 99) 100 100 100 100 100 100 100 99 100 client - connection-oriented RPC ( 74, 81, 114, 129) server - connectionless RPC ( 74, 84, 89, 107) server - connection-oriented RPC ( 74, 84, 114, 136) Messages 63 56 34 34 29 59 34 29 67 69 60 65 N 61 NDR64 64 67 65 65 64 64 63 45 31 33 32 59 45 NOCALL 100 100 16 O 26 P 35 143 140 142 149 PDU segments ( 44, 57) 57 44 45 99 99 66 61 67 35 27 Preferred security providers 149 149 27 69 59 70 68 74 151 Protocol Details 71 35 Q QUACK 100 100 QUIT 100 100 R 62 Range attribute 62
62 62 16 18 16 REJECT 100 100 26 64 99 99 99 99 150 RPC extensions conformance to [C706] requirements 171 165 171 163 34 47 46 35 43 43 43 43 53 53 54 54 46 S 48 57 50 Security implementer considerations 149 149 149 149 71 36 Sequencing client - connectionless RPC ( 74, 81, 89, 99, 99, 99) 100 100 100 100 100 100 99 100 client - connection-oriented RPC ( 74, 81, 114, 129) server - connectionless RPC ( 74, 84, 89, 107) server - connection-oriented RPC ( 74, 84, 114, 136) 100 Server - connectionless RPC abstract data ( 71, 83, 85, 101) higher-layer triggered events 86 89 73 106 106 73 83 106 83 initialization ( 73, 83, 86, 106) local events ( 80, 84, 91, 111) message processing ( 74, 84, 89, 107) sequencing ( 74, 84, 89, 107) timer events ( 80, 84, 91, 111) timers ( 73, 83, 86, 105) Server - connection-oriented RPC abstract data model ( 71, 83, 112, 131) higher-layer triggered events 73 114 135 73 135 83 135 83 initialization ( 73, 83, 114, 134) local events ( 80, 84, 123, 138) message processing ( 74, 84, 114, 136) 130 sequencing ( 74, 84, 114, 136) timer events ( 80, 84, 122, 138) timers ( 73, 83, 114, 134) 64 30 31 28 State machines - abstract data model 85 85 74 62 Strings 60 65 66 66 66 147 65 Syntax 63 56 34 44 34 59 64 67 65 65 64 64