Revision Summary Date Revision History Revision Comments 2/22/2007 0.01 New Version 0.01 release 6/1/2007 1.0 Major Updated and revised the technical content. 7/3/2007 1.0.1 Minor Editorial fixes only. 7/20/2007 1.0.2 Editorial Changed language and formatting in the technical content. 8/10/2007 1.0.3 Editorial Changed language and formatting in the technical content. 9/28/2007 1.0.4 Editorial Changed language and formatting in the technical content. 10/23/2007 1.0.5 Minor Revised a figure; revised size of cmd field in several packets. 11/30/2007 1.1 Clarified the meaning of the technical content. 1/25/2008 1.1.1 Editorial Changed language and formatting in the technical content.
3/14/2008 1.1.2 Editorial Changed language and formatting in the technical content. 5/16/2008 1.1.3 Editorial Changed language and formatting in the technical content. 6/20/2008 1.2 Minor Clarified the meaning of the technical content. 7/25/2008 1.2.1 Editorial Changed language and formatting in the technical content. 8/29/2008 1.2.2 Editorial Changed language and formatting in the technical content. 10/24/2008 1.2.3 Editorial Changed language and formatting in the technical content. 12/5/2008 2.0 Major Updated and revised the technical content. 1/16/2009 2.1 Minor Clarified the meaning of the technical content. 2/27/2009 2.1.1 Editorial Changed language and formatting
in the technical content. 4/10/2009 2.1.2 Editorial Changed language and formatting in the technical content. 5/22/2009 3.0 Major Updated and revised the technical content. 7/2/2009 3.0.1 Editorial Changed language and formatting in the technical content. 8/14/2009 3.0.2 Editorial Changed language and formatting in the technical content. 9/25/2009 3.0.3 Editorial Changed language and formatting in the technical content. 11/6/2009 3.0.4 Editorial Changed language and formatting in the technical content. 12/18/2009 4.0 Major Updated and revised the technical content. 1/29/2010 5.0 Major Updated and revised the technical content.
3/12/2010 6.0 Major Updated and revised the technical content. 4/23/2010 6.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 7.0 Major Updated and revised the technical content. 7/16/2010 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 7.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 7.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 7.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 7.0 None No changes to the
meaning, language, or formatting of the technical content. 2/11/2011 8.0 Updated and revised the technical content. 3/25/2011 9.0 Major Updated and revised the technical content. 5/6/2011 9.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 9.1 Minor Clarified the meaning of the technical content. 9/23/2011 9.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 10.0 Major Updated and revised the technical content. 3/30/2012 10.0 None No changes to the meaning, language, or formatting of the technical content.
0x00000003 NumberOfDVCs (2 bytes): A 16-bit, unsigned integer indicating the number of DVCs that will have data written by the server manager on this tunnel. ListOfDVCIds (variable): One or more 32-bit, unsigned integers, as indicated by the NumberOfDVCs containing the channel ID of each DVC that will have data written by the server manager on this tunnel. Soft-Sync Response PDU (DYNVC_SOFT_SYNC_RESPONSE) A DYNVC_SOFT_SYNC_RESPONSE PDU is sent by a DVC client manager over the DRDYNVC static virtual channel on the main RDP connection in response to a Soft-Sync Request PDU (section ). This PDU MUST include all of the multitransport tunnels that will be used by the client manager for writing data to a DVC. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 cbId Sp Cmd Pad NumberOfTunnels ... TunnelsToSwitch (variable) ... cbId (2 bits): Unused. MUST be set to 0x00. Sp (2 bits): Unused. MUST be set to 0x00. Cmd (4 bits): MUST be set to 0x09. (Soft-Sync Response) Pad (1 byte): An 8-bit unsigned integer. Unused. MUST be set to 0x00. NumberOfTunnels (4 bytes): A 32-bit, unsigned integer indicating the number of multitransport tunnels on which DVC data will be written by the client manager. TunnelsToSwitch (variable): One or more 32-bit, unsigned integers, as indicated by the NumberOfTunnels field, containing the type of each tunnel on which DVC data will be written by the client manager. Value Meaning TUNNELTYPE_UDPFECR 0x00000001 RDP-UDP Forward Error Correction (FEC) reliable multitransport tunnel ( section 1.3). TUNNELTYPE_UDPFECL 0x00000003 RDP-UDP FEC lossy multitransport tunnel ([MS-RDPEMT] section 1.3).
A Abstract data client ( 31, 37) server ( 31, 41) 55 45 46 46 13 C 13 59 Client ( 30, 37) abstract data ( 31, 37) higher-layer triggered events ( 32, 39) initialization ( 32, 38) message processing ( 32, 39) 40 30 sequencing rules ( 32, 39) timer events ( 37, 40) timers ( 32, 38) 26 D Data receiving ( 11, 12, 21, 33, 39, 43) sending ( 11, 12, 21, 32, 39, 43) Data - abstract client ( 31, 37) server ( 31, 41) 9 DVC 17 19 38 closing ( 13, 26) 20 21 initialization ( 39, 42) 16 10 message flow - receiving data ( 11, 12) message flow - sending data ( 11, 12) 20 41 9 9 19 17 17 18 26 20 21 23 22 E encapsulation 9 Examples 55 45 46 46 45 F 14 G 7 H Higher-layer triggered events client ( 32, 39) server ( 32, 42) I 56 56 8 Initialization client ( 32, 38) server ( 32, 41) 16 7 M Message flow 10 DVC - receiving data ( 11, 12) DVC - sending data ( 11, 12) Message processing client ( 32, 39) server ( 32, 43) 15 Messages 26 16 20 15 21 26 15 15 N 8