1.5.1 Client Implementation Requirements
Clients implementing the Remote Desktop Protocol: Graphics Pipeline Extension must set the RNS_UD_CS_SUPPORT_DYNVC_GFX_PROTOCOL (0x0100) flag in the earlyCapabilityFlags field of the Client Core Data ([MS-RDPBCGR] section 2.2.1.3.2) to indicate support for the protocol. Furthermore, the client must be capable of processing the following messages:
RDPGFX_WIRE_TO_SURFACE_PDU_1 (section 2.2.2.1)
RDPGFX_WIRE_TO_SURFACE_PDU_2 (section 2.2.2.2)
RDPGFX_DELETE_ENCODING_CONTEXT_PDU (section 2.2.2.3)
RDPGFX_SOLIDFILL_PDU (section 2.2.2.4)
RDPGFX_SURFACE_TO_SURFACE_PDU (section 2.2.2.5)
RDPGFX_SURFACE_TO_CACHE_PDU (section 2.2.2.6)
RDPGFX_CACHE_TO_SURFACE_PDU (section 2.2.2.7)
RDPGFX_EVICT_CACHE_ENTRY_PDU (section 2.2.2.8)
RDPGFX_CREATE_SURFACE_PDU (section 2.2.2.9)
RDPGFX_DELETE_SURFACE_PDU (section 2.2.2.10)
RDPGFX_START_FRAME_PDU (section 2.2.2.11)
RDPGFX_END_FRAME_PDU (section 2.2.2.12)
RDPGFX_RESET_GRAPHICS_PDU (section 2.2.2.14)
RDPGFX_MAP_SURFACE_TO_OUTPUT_PDU (section 2.2.2.15)
RDPGFX_CAPS_CONFIRM_PDU (section 2.2.2.19)
Furthermore, clients implementing the Remote Desktop Protocol: Graphics Pipeline Extension must be capable of sending the following messages:
Clients that implement optional persistent bitmap caching must be capable of sending the RDPGFX_CACHE_IMPORT_OFFER_PDU (section 2.2.2.16) message and processing the RDPGFX_CACHE_IMPORT_REPLY_PDU (section 2.2.2.17) message.
Clients that implement Enhanced RemoteApp ([MS-RDPERP] section 1.3.3) must be capable of processing the RDPGFX_MAP_SURFACE_TO_WINDOW_PDU (section 2.2.2.20) message.
Clients that advertise the RDPGFX_CAPSET_VERSION105 (section 2.2.3.8) or RDPGFX_CAPSET_VERSION106 (section 2.2.3.9) capability sets MUST be capable of processing the following messages: