Export (0) Print
Expand All

8 Appendix C: RPC Extensions Conformance to [C706] Requirements

The following table documents the conformance of RPC extensions to the [C706] 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 [MS-RPCL] (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 must support the API naming, syntax, and semantics, as defined in chapter 3. Implementations may extend the set of status codes documented in chapter 3.

The API differences between [C706] and RPC extensions are documented in Appendix C.

Implementations must support the naming, syntax, and semantics for IDL, as specified in chapter 4.

Conforms to aspects that affect the protocol and interoperability except where noted in this specification in sections 2.2.4 through 2.2.7 and 3.1.1.5.

Implementations must support the naming, syntax, and semantics for stubs, 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 3.1.2.5.1.

Implementations must 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 must support the service semantics specified in chapter 7.

Conforms.

Implementations must follow the conformance rules specified in chapter 9.

This specification redefines the state machines of [C706] in sections 3.2.1.1.1, 3.2.2.1, 3.2.3.1, 3.3.2, and 3.3.3.

Implementations must support the syntax of the PDU encodings in chapter 12.

Conforms except where noted in this specification in sections 2.2.2 and 2.2.3.

Implementations must support the Authentication Verifier encodings, as specified in chapter 13.

Conforms except as noted in section 2.2.2.11.

Implementations must support the rules and encodings for NDR, 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, 3.1.2.7.1, and 3.1.3.5.

Implementations must support the syntax, semantics, and encoding for UUIDs, as specified in appendix A.

Conforms except where noted in this specification in section 2.2.1.1.3.

Implementations must support the naming and semantics for protocol sequence strings, as specified in appendix B.

Conforms except where noted in this specification in section 2.1.

Implementations must support the naming and semantics for the name_syntax arguments, as specified in appendix C.

Extensions to name services are documented in [MS-RPCL].

Implementations must 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 5, with additional security provider details in section 2.2.1.1.7 and modifications to rpc_c_authn_dce_secret in section 3.2.1.5.1.

Implementations must 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 3.1.1.5.5.

Implementations must 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 2.2.4.1, where Remote Procedure Call extensions extends the specification with new types.

Implementations must support the portable character set, as specified in appendix G.

Conforms.

Implementations must use the endpoint mapper ports, as specified in appendix H, for the corresponding protocols.

Conforms for TCP/IP and UPD transports (NCACN_IP_TCP and NCADG_IP_UDP). Other transports use other ports as specified in section 2.1.

Implementations must adhere to the rules for protocol identifier assignment, as specified in appendix I.

Not conformant, as specified in this specification in section 2.1.

Implementations must 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 must provide defaults for the protocol machine values specified in appendix K.

This specification redefines the protocol state machines that are specified in [C706], in 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 must obey the special protocol tower encoding rules specified in appendix L.

Conforms.

Implementations must support the syntax and semantics of the dce_error_inq_text routine specified in appendix M.

Conforms.

Implementations must adhere to the mappings for transfer syntax UUIDs, as specified in appendix N.

Conforms except where noted in this specification in section 3.3.1.5.3 and 2.2.5.1. 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 must support the endpoint mapper semantics, as specified in appendix O.

Conforms except where noted in this specification in section 2.2.1.2.

Implementations must support the conversation manager semantics, as specified in appendix P.

Conforms except where noted in this specification in section 3.2.

Implementations must support the remote management semantics, as specified in appendix Q.

Conforms except where noted in this specification in section 2.2.1.3.

Implementations must register all protocol sequences with the Open Software Foundation (OSF), as specified in [C706] appendix B.

The protocol sequence strings listed in section 2.1 that are not already specified in [C706] appendix B have not been registered with OSF.

 
Show:
© 2014 Microsoft