technical content. 1/25/2008 2.1.2 Editorial Changed language and formatting in the technical content. 3/14/2008 2.1.3 Editorial Changed language and formatting in the technical content. 5/16/2008 2.1.4 Editorial Changed language and formatting in the technical content. 6/20/2008 3.0 Updated and revised the technical content. 7/25/2008 3.1 Minor Clarified the meaning of the technical content. 8/29/2008 3.2 Clarified the meaning of the technical content. 10/24/2008 4.0 Updated and revised the technical content. 12/5/2008 5.0 Major Updated and revised the technical content. 1/16/2009 6.0 Major Updated and revised the technical content.
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 Major 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 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
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 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 Major 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 Significantly changed the technical content. 9/15/2017 30.0 Significantly changed the technical content.
Appendix C: RPC Extensions Conformance to [C706] Requirements The following table documents the conformance of extensions to the specification against the list of conformance requirements specified in [C706] section 1.3, except for any portion that relates to name services. The Windows implementation of name services is detailed in Remote Procedure Call Location Services Protocol (This is a legacy protocol that has been deprecated). In cases where these extensions do not conform to [C706], specific section references are provided only where the conformance failure is specified explicitly by an individual section. Conformance failures specified across numerous sections are not accompanied by lists of those sections. Conformance requirements from [C706] section 1.3 Status of this specification Implementations support the API naming, syntax, and semantics, as defined in chapter 3. Implementations can extend the set of status codes documented in chapter 3. The API differences between [C706] and RPC extensions are documented in Appendix C. Implementations support the naming, syntax, and semantics for , as specified in chapter 4. Conforms to aspects that affect the protocol and interoperability except noted in this specification in sections through and . Implementations support the naming, syntax, and semantics for , as specified in chapter 5. Conforms except where noted in this specification in sections 2.2.4 through 2.2.7, 3.1.1.5, and . Implementations support the semantics specified in chapter 6. Conforms, except that Microsoft support for NSI interface and associated extensions to name service are detailed in [MS-RPCL] have been deprecated. Implementations support the service semantics specified in chapter 7. Conforms. Implementations follow the conformance specified in chapter 9. This specification redefines the state machines of [C706] in sections , , , , and . Implementations support the syntax Conforms except where noted in this
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 and encodings for , as specified in chapter 14. Conforms except where 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 where 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 .
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 where 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 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 .
Connectionless RPC transports 36 39 44 35 35 146 35 72 45 Connection-oriented RPC transports 36 39 44 30 35 Constants 36 36 65 61 147 75 76 D Data model - abstract client - connectionless RPC ( 72, 81, 86, 92) client - connection-oriented RPC ( 72, 81, 113, 125) server - connectionless RPC ( 72, 84, 86, 102) server - connection-oriented RPC ( 72, 84, 113, 132) Data types NDR64 ( 65, 65) E 68 39 43 43 43 40 43 42 43 40 Examples 146 146 147 141 144 141 143 148 148 62 36 75 F FACK message processing 101 101 FAULT 101 101 58 29 151 151 G 14 H triggered events client - connectionless RPC 87 90 100 74 74 82 client - connection-oriented RPC 74 115 74 128 129 82 server - connectionless RPC 87 90 74 107 107 74 84 107 84 server - connection-oriented RPC 74 115 136 74 136 84 136 84 I 151 60 60 38 150 150 150 150 150 150
63 17 19 17 REJECT 101 101 27 65 100 100 100 100 151 RPC extensions conformance to [C706] requirements 172 166 172 164 35 48 47 36 44 44 44 44 54 54 55 55 47 S 49 58 51 Security implementer considerations 150 150 150 150 72 37 Sequencing rules client - connectionless RPC ( 75, 82, 90, 100, 100, 100) 101 101 101 101 101 101 100 101 client - connection-oriented RPC ( 75, 82, 115, 130) server - connectionless RPC ( 75, 85, 90, 108) server - connection-oriented RPC ( 75, 85, 115, 137) 101 Server - connectionless RPC abstract data ( 72, 84, 86, 102) higher-layer triggered events 87 90 74 107 107 74 84 107 84 initialization ( 74, 84, 87, 107) local events ( 81, 85, 92, 112) message processing ( 75, 85, 90, 108) sequencing rules ( 75, 85, 90, 108) timer events ( 81, 85, 92, 112) timers ( 74, 84, 87, 106) Server - connection-oriented RPC abstract data model ( 72, 84, 113, 132) higher-layer triggered events 74 115 136 74 136 84 136 84 initialization ( 74, 84, 115, 135) events ( 81, 85, 124, 139) message processing ( 75, 85, 115, 137) 131 sequencing ( 75, 85, 115, 137) timer events ( 81, 85, 123, 139) timers ( 74, 84, 115, 135) 65 31 32 29 State machines - abstract data model 86 86 75 63 Strings 61 66 67 67 67 148 66 Syntax 64 57 35 45 35 60 65 68 66 66 65 65 64