2.1.1 RPC Over HTTP Transport

  • Article

The RDGSP Protocol uses the Remote Procedure Call over HTTP Protocol [MS-RPCH] as transport.

This protocol uses the following static endpoints as well as well-known endpoints. These endpoints are ports as defined in [MS-RPCH] section 1.5 on the RDG server. The only protocol sequence used for the transport is "ncacn_http".

  • Port 80: This endpoint is used by [MS-RPCH] as the underlying transport, when [MS-RPCH] runs over plain HTTP.

  • Port 443: This endpoint is used by [MS-RPCH] as the underlying transport, when [MS-RPCH] runs over HTTPS.

  •  Port 3388: This endpoint is used by the RDG server to listen for incoming RPC method calls. The authenticated RPC interface allows RPC to negotiate the use of authentication and the authentication level on behalf of the RDG client and target server.

Port 3388 endpoint and at least one of Port 80 and Port 443 endpoints MUST be supported.

 The RDGSP Protocol MUST use the UUID, as specified in section 1.9. The RPC version number is 1.3.