2.1 Transport

Both RPC over HTTP v1 and RPC over HTTP v2 start their transport mapping process from a stream of RPC and RPC over HTTP PDUs that need to be mapped to one or more HTTP or HTTPS requests and TCP/IP connections. Both protocol dialects also share the following characteristics:

  • An endpoint mapper with a well-known endpoint of 593.

  • An RPC protocol identifier of 0x1F.

  • An RPC network address for the RPC server provided by a higher layer that MUST be an IPv4 or IPv6 address.

  • The RPC endpoint for the RPC server MUST be a TCP/IP port number.

  • The predecessor RPC protocol sequence is "ncacn_http".

  • RPC network options provided by higher layers that:

    • MUST contain a valid IPv4 or IPv6 address for the HTTP server.<3>

    • MAY contain an HTTP proxy.<4>