Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 2.0 Major Significantly changed the technical content. 10/25/2012 3.0 Major Significantly changed the technical content. 1/31/2013 3.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.1 Minor Clarified the meaning of the technical content. 11/14/2013 4.0 Major Significantly changed the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the technical content.
5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 10/16/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 5.0 None No changes to the meaning, language, or formatting of the technical content.
Introduction The Remote Desktop Protocol: Input Virtual Channel Extension applies to the Remote Desktop Protocol: Basic Connectivity and Graphics Remoting, as specified in sections 1 to 5. The input protocol defined in section is used to remote multitouch and pen input from a client to a terminal server. The multitouch and pen input is generated at the client by a physical or virtual digitizer, encoded, and then sent on the wire to the server. After this input is received and decoded by the server, it is injected into the session associated with the remote user, effectively remoting the multitouch and pen input generated at the client. Sections 1.5, 1.8, 1.9, 2, and 3 of this specification are normative. All other sections and examples in this specification are informative. Glossary This document uses the following ANSI character: An 8-bit Windows-1252 character set unit. little-endian: Multiple-byte values that are byte-ordered with the least significant byte stored in the memory location with the lowest address. protocol data unit (PDU): Information that is delivered as a unit among peer entities of a network and that may contain control information, address information, or data. For more information on remote procedure call (RPC)-specific PDUs, see section 12. terminal server: A computer on which terminal services is running. MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in . All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT. References Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the . Normative References We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact . We will assist you in finding the relevant information. [MS-RDPBCGR] Microsoft Corporation, "". [MS-RDPEDYC] Microsoft Corporation, "". [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, Informative References None.
Index A Abstract data model 28 25 29 26 25 7 C 7 37 Client 28 25 29 higher-layer triggered events ( 26, 29) initialization ( 26, 29) message processing events 26 29 30 30 29 sending RDPINPUT_TOUCH_PDU message ( 29, 30) other local events ( 26, 31) sequencing rules 26 29 30 30 29 sending RDPINPUT_TOUCH_PDU message ( 29, 30) timer events ( 26, 31) timers ( 26, 29) D Data - abstract 28 25 29 26 25 24 E 24 F 7 G 5 H Higher-layer triggered events client ( 26, 29) server ( 26, 27) I 35 35 5 Initialization client ( 26, 29) server ( 26, 27) 5 M Message processing events client 26 29 30 30 29 sending RDPINPUT_TOUCH_PDU message ( 29, 30) server 26 27 processing RDPINPUT_TOUCH_PDU message ( 27, 27) 27 28 27 Messages 8 8 N 5 O local events client ( 26, 31) server ( 26, 28) Overview (synopsis) ( 6, 7) P 35 7 7 36 R 5 5 5