zilongwang/ReadingBank huggingface dataset:
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 Significantly changed the technical content. 1/31/2013 4.0 Significantly changed the technical content. 8/8/2013 5.0 Major Significantly changed the technical content. 11/14/2013 6.0 Major Significantly changed the technical content. 2/13/2014 7.0 Major Significantly changed the technical content. 5/15/2014 7.0 None No changes to the meaning, language, or formatting of the technical content.
6/30/2015 8.0 Major Significantly changed the technical content. 10/16/2015 8.0 None No changes to the meaning, language, or formatting of the technical content. 3/2/2016 9.0 Significantly changed the technical content. 7/14/2016 9.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 10.0 Significantly changed the technical content. 9/15/2017 11.0 Major Significantly changed the technical content.
A Abstract data model 18 18 10 C 10 43 Client 18 triggered events 28 28 28 28 28 28 28 timer events 35 35 34 27 D Data model - abstract 18 18 F 10 G 5 H Higher-layer triggered events client 28 28 28 28 server 28 28 28 28 I 41 41 6 Initialization 28 28 5 M Message processing 28 28 Messages 11 11 N 6 O 7 P 41 10 10 42 R 6 6 6 10 S Security 41 41 Sequencing rules 28 28 Server 18 higher-layer triggered events 28 28 28 28 28 28 28 timer events 35 35 34 27 10 11
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 4.0 Major Significantly changed the technical content. 8/8/2013 5.0 Major Significantly changed the technical content. 11/14/2013 6.0 Major Significantly changed the technical content. 2/13/2014 7.0 Major Significantly changed the technical content. 5/15/2014 7.0 None No changes to the meaning, language, or formatting of the technical content.
6/30/2015 8.0 Major Significantly changed the technical content. 10/16/2015 8.0 None No changes to the meaning, language, or formatting of the technical content. 3/2/2016 9.0 Significantly changed the technical content. 7/14/2016 9.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 10.0 Major Significantly changed the technical content. 9/15/2017 11.0 Major Significantly changed the technical content. 12/1/2017 11.0 None No changes to the meaning, language, or formatting of the technical content.
Vectors ACK Vector The ACK vector captures the of the queue of at the receiver endpoint. Each position in the can have two values that indicate whether a Source Packet is present in the queue, or not. The compression is used for encoding the states of Source Packets in the array. An ACK Vector comprises a number of elements, as specified by the uAckVectorSize field in the RDPUDP_ACK_VECTOR_HEADER structure (section ). Each element is 8 bits long. 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 uAckVectorSize S S L L L L L L AckVec Element[2] The two most significant bits of each element compose the VECTOR_ELEMENT_STATE enumeration (section ). The next 6 bits are the length of a continuous sequence of datagrams that share the same state. The ACK vectors form a , and are padded so that they are aligned to WORD ( section 2.2.61) boundaries. This is similar to the description of ACK vectors in the Datagram Congestion Control Protocol (DCCP), as described in .
Index A Abstract data 18 18 10 C 10 43 Client 18 higher-layer triggered events 28 28 28 28 28 28 28 timer events 35 35 34 27 D Data model - abstract 18 18 F 10 G 5 H Higher-layer triggered events client 28 28 28 28 server 28 28 28 28 I 41 41 6 Initialization 28 28 5 M Message processing 28 28 Messages 11 11 N 6 O 7 P 41 10 10 42 R 6 6 6 10 S Security 41 41 Sequencing rules 28 28 Server 18 higher-layer triggered events 28 28 28 28 28 28 28 timer events 35 35 34 27 10 11 T
TRANSFER_OUT_REQUEST 0x00000106 The server sends the message. RETRACT_DEVICE 0x00000107 The server the message. Client Device Sink Interface IDs are as follows. Value Meaning ADD_VIRTUAL_CHANNEL 0x00000100 The client sends the message. ADD_DEVICE 0x00000101 The client sends the message. Channel Notification Interface IDs are as follows. Value Meaning CHANNEL_CREATED 0x00000100 The server and the client send the message. messagePayload (variable): An array of unsigned 8-bit integers. The remainder of the message is interpreted based on the interface for which the packet is sent. This field is optional based on the packet length. Interface Manipulation This protocol utilizes the same Interface and Interface Release messages that are defined in section 2.2.2. Interface Manipulation Exchange Capabilities Interface The Exchange Capabilities Interface is identified by the interface ID 0x00000000. This interface is used to exchange the client's and the server's capabilities for interface manipulation. Interface Manipulation Exchange Capabilities Request (RIM_EXCHANGE_CAPABILITY_REQUEST) This message is used by the server to request interface manipulation capabilities from the client. 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 Header (variable) ... CapabilityValue
R 8 8 8 20 11 24 24 24 15 16 S Security 63 63 Sequencing rules client 54 54 54 54 54 49 55 55 57 55 54 56 58 58 49 55 56 58 58 server 49 49 50 50 50 49 51 50 51 51 51 50 51 53 53 49 51 51 52 52 Server 49 48 overview ( 48, 49) higher-layer triggered events ( 48, 49) initialization ( 48, 49) local events ( 49, 53) message processing 49 49 50 50 50 49 51 50 51 51 51 50 51 53 53 49 51 51 52 52 53 47 sequencing rules 49 49 50 50 50 49 51 50 51 51 51 50 51 53 53 49 51 51 52 52 timer events ( 49, 53) timers ( 48, 49) 13 13 13 12 T Timer events client ( 49, 59) server ( 49, 53) Timers client ( 48, 53)
Revision Summary Date Revision History Revision Class Comments 7/13/2009 0.1 Initial Availability 8/28/2009 0.2 Editorial Revised and edited the technical content 11/6/2009 0.3 Editorial Revised and edited the technical content 2/19/2010 1.0 Editorial Revised and edited the technical content 3/31/2010 1.01 Editorial Revised and edited the technical content 4/30/2010 1.02 Minor Updated the technical content 6/7/2010 1.03 Editorial Revised and edited the technical content 6/29/2010 1.04 Editorial Changed language and formatting in the technical content. 7/23/2010 1.04 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 1.04 None No changes to the meaning, language, or formatting of the
language, or formatting of the technical content. 9/12/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.1 Minor Clarified the meaning of the technical content. 2/11/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 11/18/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 2.1 None No changes to the meaning, language, or formatting of the technical content.
contains the trace information for the error. If no call-stack trace is generated, this value MUST be a CSOM null JSON value. This member is optional. ErrorTypeName If there is type name information, this value is a CSOM String JSON value with the type name of the error. If there is no type name information, this value MUST be a CSOM null JSON value. This member MUST be present. ErrorValue If is additional error information, this value is a CSOM String JSON value with additional information about the error. If there isn’t any additional error information, this MUST be a CSOM null JSON value. This
A CSOM DateTime value that contains the date when the book was published. Status– A Status type that contains the status of the book. Title– A CSOM String that contains the title of the book. UpdateSampleStream – Update the sample content of the book. The only parameter is a CSOM Stream that contains the sample content of the book. A type that contains information a book to be added to the catalog for the book store. Author– A CSOM String that contains the name of the author of the book. A CSOM DateTime value that contains the date when the book was published. Status– A Status type that contains the status of the book. Title– A CSOM String that contains the title of the book. None. Status A CSOM enumeration type that specifies whether a book is in None. None.
Index A Abstract data model 41 120 18 40 40 C 18 145 Client 43 41 44 22 D Data model - abstract 41 E 22 Examples 120 114 123 116 117 122 Update Book Information ( 119, 125) F 18 Full XML schema 128 G 12 40 I 127 127 16 Initialization 44 12 M Message processing 44 Messages 40 40 22 22 40 22 21 26 20 20 22 N 21 15 O Other local events 113 16 127 18 18 144 Protocol Details 41 R 15 16 15 17 128 116 123 117 S Security 127 127 Sequencing rules 44 Server 41 43 44 44 113 41 44 44 113 44
or formatting of the technical content. 6/17/2011 7.1 Minor Clarified the meaning of the technical content. 9/23/2011 8.0 Updated and revised the technical content. 12/16/2011 9.0 Major Updated and revised the technical content. 3/30/2012 10.0 Major Updated and revised the technical content. 7/12/2012 11.0 Major Updated and revised the technical content. 10/25/2012 12.0 Updated and revised the technical content. 1/31/2013 12.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 13.0 Updated and revised the technical content. 11/14/2013 13.0 None No changes to the meaning, language,
Change Tracking This section identifies changes that were made to this document since the last release. Changes are classified as Major, Minor, or None. The revision Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperability or implementation. Examples of major changes are: A document revision that incorporates changes to interoperability requirements. A document revision that captures changes to protocol functionality. The revision class Minor means that the meaning of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level. The revision class None means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the relevant technical content is identical to the last released version. The changes made to this document are listed in the following table. For more information, please contact . Section Description Revision Appendix A: Product Behavior Added Windows Server operating system to the list of applicable products. Major
Index A Abstract data model 53 48 overview ( 48, 53) 49 48 overview ( 48, 49) 17 16 12 C 19 12 65 18 18 10 60 18 Client 53 48 overview ( 48, 53) higher-layer triggered events ( 48, 53) initialization ( 48, 53) local events ( 49, 59) message processing 54 54 54 54 54 49 55 55 57 55 54 56 58 58 49 55 56 58 58 59 47 sequencing rules 54 54 54 54 54 49 55 55 57 55 54 56 58 58 49 55 56 58 58 timer events ( 49, 59) timers ( 48, 53) D Data model - abstract 53 48 overview ( 48, 53) 49 48 overview ( 48, 49) 16 16 E Examples 60 60 61 61 61 F 12 G 7 H Higher-layer triggered events client ( 48, 53) server ( 48, 49) I 11 63 63 8 Initialization client ( 48, 53) server ( 48, 49) 15 15 15
15 60 21 7 20 61 25 L Local events client ( 49, 59) server ( 49, 53) M Message processing client 54 54 54 54 54 49 55 55 57 55 54 56 58 58 49 55 56 58 58 server 49 49 50 50 50 49 51 50 51 51 51 50 51 53 53 49 51 51 52 52 Messages 18 16 15 15 24 13 13 13 27 38 19 44 42 27 N 10 8 O local events 59 53 Overview 10 11 10 9 10 9 P 63 12 12 64 Q 22 22 R 8 8 8 20 11 24 24 24 15 16 S Security 63 63 Sequencing rules client 54 54 54 54 54
Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 2.0 Major Significantly changed the technical content. 7/12/2012 2.0 None No changes to the meaning, languague, or formatting of the technical content. 10/25/2012 3.0 Major Significantly changed the technical content. 1/31/2013 4.0 Major Significantly changed the technical content. 8/8/2013 5.0 Major Significantly changed the technical content. 11/14/2013 5.0 None No changes to the meaning, languague, or formatting of the technical content. 2/13/2014 6.0 Major Significantly changed the technical content. 5/15/2014 6.0 None No changes to the meaning, languague, or
Index A Abstract data model client ( 15, 16) server ( 15, 17) 6 C 7 26 Client abstract data model ( 15, 16) higher-layer triggered events ( 16, 17) initialization ( 16, 16) message processing 17 16 other local events ( 16, 17) 15 sequencing rules 17 16 events ( 16, 17) timers ( 15, 16) D Data - abstract client ( 15, 16) server ( 15, 17) E Examples 19 19 22 20 21 F 7 G 5 H Higher-layer triggered events client ( 16, 17) server ( 16, 18) I 24 24 6 Initialization client ( 16, 16) server ( 16, 17) 5 M Message processing client 17 16 server 16 18 18 Messages 8 8 N 5 O Other local events client ( 16, 17) server ( 16, 18) 6 P 24 6 6 25 Proxy 15 R 5 6 5 6 S Security 24 24 Sequencing rules client 17 16 server 16 18 18 Server abstract data model ( 15, 17) higher-layer triggered events ( 16, 18)
Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 2.0 Major Significantly changed the technical content. 7/12/2012 2.0 None No changes to the meaning, languague, or formatting of the technical content. 10/25/2012 3.0 Major Significantly changed the technical content. 1/31/2013 4.0 Significantly changed the technical content. 8/8/2013 5.0 Major Significantly changed the technical content. 11/14/2013 5.0 None No changes to the meaning, languague, or formatting of the technical content. 2/13/2014 6.0 Major Significantly changed the technical content. 5/15/2014 6.0 None No changes to the meaning, languague, or
formatting of the technical content. 6/30/2015 7.0 Significantly changed the technical content. 10/16/2015 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 8.0 Major Significantly changed the technical content. 6/1/2017 9.0 Major Significantly changed the technical content. 9/15/2017 10.0 Significantly changed the technical content. 12/1/2017 10.0 None No changes to the meaning, language, or formatting of the technical content. 9/12/2018 11.0 Major Significantly changed the technical content.
0 UINT64 hnsTimestamp - C7C60600 00000000 0x6C6C7 444103 (100-ns intervals) ≈ 44 (ms) UINT64 hnsDuration – 00000000 00000000 0 UINT16 CurrentPacketIndex – 0100 1 UINT16 PacketsInSample – 0100 1 UINT32 SampleNumber – 01000000 1 UINT32 cbSample – 0B030000 779 (bytes) BYTE pSample[779] Raw video data UINT32 Reserved – 00 Message 4 – TSMM_PRESENTATION_REQUEST (STOP) Raw packet data: 44000000 01000000 03010200 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00 TSMM_VIDEO_PACKET_HEADER UINT32 cbSize – 44000000 68 (bytes) UINT32 PacketType – 01000000 1 (TSMM_PACKET_TYPE_PRESENTATION_REQUEST) TSMM_PRESENTATION_REQUESTUINT8 PresentationId – 03 3 UINT8 Version – 01 1 Command – 02
Index A Abstract data model client ( 15, 16) server ( 15, 17) 6 C 7 26 Client abstract data model ( 15, 16) higher-layer triggered events ( 16, 17) initialization ( 16, 16) message processing 17 16 other local events ( 16, 17) 15 sequencing 17 16 timer events ( 16, 17) timers ( 15, 16) D Data model - abstract client ( 15, 16) server ( 15, 17) E Examples 19 19 22 20 21 F 7 G 5 H Higher-layer triggered events client ( 16, 17) server ( 16, 18) I 24 24 6 Initialization client ( 16, 16) server ( 16, 17) 5 M Message processing client 17 16 server 16 18 18 Messages 8 8 N 5 O Other local events client ( 16, 17) server ( 16, 18) 6 P 24 6 6 25 15 R 5 6 5 6 S Security 24 24 Sequencing client 17 16 server 16 18 18 Server abstract data model ( 15, 17) higher-layer triggered events ( 16, 18)
ASYNC_PRINTER_PROPS_REQ 0x00000107 Server Printer Properties request CANCEL_ASYNC_PRINTER_PROPS_REQ 0x0000010A Server Cancel Printer Properties request ASYNC_DOC_PROPS_REQ 0x00000106 Server Document Properties request CANCEL_ASYNC_DOC_PROPS_REQ 0x00000109 Server Cancel Async Document Properties request MOVE_DOC_PROPERTIES_REQ 0x0000010B Server Move Document Properties Window request MXDC_GETPDEV_ADJUSTMENT_REQ 0x0000010C Server Get Device Adjustments request Printer Properties Callback FunctionIds are as follows. Meaning PRINTER_PROPS_CALLBACK_REQ 0x00000100 Client Printer Properties Callback request Document Properties Callback FunctionIds are as follows. Meaning DOC_PROPS_CALLBACK_REQ 0x00000100 Client Document Properties Callback request MessagePayload (variable): An array of unsigned 8-bit integers. The remainder of the message is interpreted based on the interface for which the packet is sent. This field is optional based on the packet length. Interface Manipulation Interface Query The Interface Query message is used to query for new interface versions based on a GUID, as defined in section 2.3.4. Query Interface Request (QI_REQ) The QI_REQ request message is sent from either the client side or the server side, and is used to request a new interface ID. 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
Security Security Considerations for Implementers There are no security considerations for the Remote Desktop Protocol: XPS Print Virtual Channel Extension messages because all traffic is secured by the underlying RDP core protocol. An overview of the implemented security-related mechanisms is as specified in section 5. of Security Parameters None.
server ( 54, 62) Initialization messages Printer Driver interface ( 15, 33, 58, 64) Printer Ticket interface ( 13, 24, 56, 62) Interface manipulation client ( 54, 56) messages ( 22, 22) 12 54 Interface Query ( 12, 22, 54, 56) Interface Release ( 12, 55, 55) 53 9 L Local events client ( 55, 61) server ( 55, 67) M Message processing client ( 54, 56) server ( 54, 62, 62) 53 Messages 50 interface manipulation ( 22, 22) 33 51 23 20 20 20 50 MOVE_DOC_PROPERTIES_REQ ( 61, 67) 49 MOVE_DOC_PROPERTIES_RSP ( 61, 67) 49 MXDC_GETPDEV_ADJUSTMENT_REQ ( 59, 65) 41 MXDC_GETPDEV_ADJUSTMENT_RSP ( 60, 65) 42 N 10 O Other local events 61 67 11 11 P 79 79 18 18 PRINT_CAPS_FROM_PRINT_TKT_REQ ( 57, 63) 31 PRINT_CAPS_FROM_PRINT_TKT_RSP ( 57, 64) 31 63 30 63 30 PRINT_TKT_TO_DEVMODE_REQ ( 57, 63) 27 PRINT_TKT_TO_DEVMODE_RSP ( 57, 63) 28 Printer Driver interface capability negotiation messages ( 15, 34, 58, 64) client ( 58, 64, 64) initialization messages ( 15, 33, 58, 64) 33 13 user interface messages ( 42, 60, 66) 33 60 60 Printer properties UI ( 42, 43, 60, 66) 51 Printer Ticket interface capability negotiation messages ( 13, 26, 56, 63) client ( 56, 62) initialization messages ( 13, 24, 56, 62) 23 13 23 66 44 66 44 PrintTicket ( 57, 57, 57) 80 Q 22 23 QUERY_DEV_NS_REQ ( 57, 63) 26 QUERY_DEV_NS_RSP ( 57, 63) 26 R 10 11 10 17 S 79 79 79 Sequencing rules client ( 54, 56) server ( 54, 62, 62) Server abstract data model ( 53, 62) higher-layer triggered events ( 54, 62) initialization ( 54, 62)
Revision Summary Date Revision History Revision Class Comments 4/23/2010 0.1 Major First Release. 6/4/2010 0.1.1 Editorial Changed language and formatting in the technical content. 7/16/2010 1.0 Updated and revised the technical content. 8/27/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 2.0 Updated and revised the technical content. 11/19/2010 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 3.0 Major Updated and revised the technical content. 2/11/2011 4.0 Major Updated and revised the technical content. 3/25/2011 5.0 Major Updated and revised the
technical content. 5/6/2011 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 5.1 Minor Clarified the meaning of the technical content. 9/23/2011 5.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 6.0 Major Updated and revised the technical content. 3/30/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 7.0 Major Updated and revised the technical content.
1/31/2013 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Major Updated and revised the technical content. 11/14/2013 8.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 8.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 8.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 9.0 Major Significantly changed the technical content. 10/16/2015 9.0 None No changes to the meaning, language, or formatting of the technical content.
Index A 16 7 B Bitmap 21 17 22 C 8 29 20 D 16 E 17 25 F 8 G 5 H 16 I 27 27 6 16 5 L 17 M Messages 9 9 9 9 N 5 NSCodec bitmap 21 17 22 20 18 9 9 9 14 13 13 O 6 P 27 7 7 28 R 5 6 5 7 18 S Security 27 27 17 8 T 17 16 29 9 16 9 V 8 8
Revision Summary Date Revision History Revision Class Comments 4/23/2010 0.1 Major First Release. 6/4/2010 0.1.1 Editorial Changed language and formatting in the technical content. 7/16/2010 1.0 Major Updated and revised the technical content. 8/27/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 2.0 Updated and revised the technical content. 11/19/2010 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 3.0 Major Updated and revised the technical content. 2/11/2011 4.0 Major Updated and revised the technical content. 3/25/2011 5.0 Major Updated and revised the
1/31/2013 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Major Updated and revised the technical content. 11/14/2013 8.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 8.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 8.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 9.0 Significantly changed the technical content. 10/16/2015 9.0 None No changes to the meaning, language, or formatting of the technical content.
7/14/2016 9.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 9.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 10.0 Major Significantly changed the technical content.
Change Tracking This section identifies changes that were made to this document since the last release. Changes are classified as Major, Minor, or None. The revision class Major means that the technical content in the document was significantly revised. Major changes affect protocol interoperability or implementation. Examples of major changes are: A document revision that incorporates changes to interoperability requirements. A document revision that captures changes to protocol functionality. The revision class Minor means that the meaning of the technical content was clarified. Minor changes do not affect protocol interoperability or implementation. Examples of minor changes are updates to clarify ambiguity at the sentence, paragraph, or table level. The revision class None means that no new technical changes were introduced. Minor editorial and formatting changes may have been made, but the relevant technical content is identical to the last released version. The changes made to this document are listed in the following table. For more information, please contact . Section Description Revision class Appendix A: Product Behavior Added Windows Server operating system to the list of applicable products. Major
Index A 16 7 B Bitmap 21 17 22 C 8 29 20 D 16 E 17 25 F 8 G 5 H 16 I 27 27 6 16 5 L 17 M Messages 9 9 9 9 N 5 NSCodec bitmap 21 17 22 20 18 9 9 9 14 13 13 O 6 P 27 7 7 28 R 5 6 5 7 18 S Security 27 27 17 8 T 17 16 29 9 16 9 V 8 8
Revision Summary Date Revision History Revision Class Comments 4/23/2010 0.1 Major First Release. 6/4/2010 0.1.1 Editorial Changed language and formatting in the technical content. 7/16/2010 1.0 Major Updated and revised the technical content. 8/27/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 2.0 Major Updated and revised the technical content. 11/19/2010 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 3.0 Major Updated and revised the technical content. 2/11/2011 4.0 Major Updated and revised the technical content. 3/25/2011 5.0 Major Updated and revised the
technical content. 5/6/2011 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 5.1 Clarified the meaning of the technical content. 9/23/2011 5.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 6.0 Major Updated and revised the technical content. 3/30/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 7.0 Major Updated and revised the technical content.
7/14/2016 9.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 9.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 10.0 Major Significantly changed the technical content. 9/12/2018 11.0 Significantly changed the technical content.
Message Description RDWebService_GetRDPFiles_InputMessage Contains a GetRDPFiles element. A message MUST NOT contain anything in the . RDWebService_GetRDPFiles_OutputMessage The response to a GetRDPFilesSoapIn message, which contains a GetRDPFilesResponse element. A message that either MUST NOT contain anything if no resources are available to connect to or MUST contain resource-specific in the SOAP body for resources to connect to. RDWebService_GetRDPFiles_InputMessage Message A WSDL message containing the request for GetRDPFiles WSDL operation. The SOAP action value is: The SOAP body contains GetRDPFiles element. <wsdl:message name="RDWebService_GetRDPFiles_InputMessage"> <wsdl:part name="GetRDPFiles" element="tns:GetRDPFiles"/> </wsdl:message> The GetRDPFilesSoapIn message contains a GetRDPFiles element, as specified in section . RDWebService_GetRDPFiles_OutputMessage Message A WSDL message containing the response for GetRDPFiles WSDL operation. The SOAP action value is: http://schemas.microsoft.com/ts/2010/09/rdweb/GetRDPFiles The SOAP body contains GetRDPFilesResponse element. <wsdl:message name="RDWebService_GetRDPFiles_OutputMessage"> <wsdl:part name="GetRDPFilesResponse" element="tns:GetRDPFilesResponse"/> </wsdl:message>
Index A Abstract data model 15 11 8 10 9 C 8 28 Client 15 15 16 15 15 15 15 10 9 D Data model - abstract 15 11 E Events 16 15 15 15 F 8 25 G 5 10 I 24 24 7 Initialization 15 11 5 L Local events 16 15 M Message processing 15 11 Messages 10 9 10 9 9 9 10 9 9 9 9 N 9 6 O Operations 11 7 P 24 7 7 27 R 6 7 6 7 S Security 24 24 Sequencing rules 15 11 Server 11 11 11 15 11 11 15 11
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 1.0 None Significantly changed the technical content. 10/25/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content.
2/13/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 2.0 Major Significantly changed the technical content. 10/16/2015 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 2.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 15 11 8 10 9 C 8 28 Client 15 16 16 16 16 16 15 10 9 D Data model - abstract 15 11 E Events 16 15 16 15 F 8 25 G 5 10 I 24 24 7 Initialization 16 11 5 L Local events 16 15 M Message processing 16 11 Messages 10 9 10 9 9 9 10 9 9 9 9 N 9 6 O Operations 11 7 P 24 7 7 27 R 6 7 6 7 S Security 24 24 Sequencing rules 16 11 Server 11 11 11 15 11 11 15 11
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 1.0 None Significantly changed the technical content. 10/25/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content.
2/13/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 2.0 Major Significantly changed the technical content. 10/16/2015 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 2.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 3.0 Significantly changed the technical content.
Index A Abstract data model 15 11 8 10 9 C 8 28 Client 15 16 16 16 16 16 15 10 9 D Data model - abstract 15 11 E Events 16 15 16 15 F 8 25 G 5 10 I 24 24 7 Initialization 16 11 5 L Local events 16 15 M Message processing 16 11 Messages 10 9 10 9 9 9 10 9 9 9 9 N 9 6 O Operations 11 7 P 24 7 7 27 R 6 7 6 7 S Security 24 24 Sequencing rules 16 11 Server 11 11 11 15 11 11
meaning, language, or formatting of the technical content. 6/10/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 2.0 Major Significantly changed the technical content. 4/11/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.1 Minor Clarified the meaning of the technical content. 2/11/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 2.1 None No changes to the
meaning, language, or formatting of the technical content. 7/15/2016 3.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 3.0 None No changes to the meaning, language, or formatting of the technical content. 4/27/2018 4.0 Major Significantly changed the technical content.
Index A Abstract data model 16 14 11 14 15 15 C 11 45 15 13 14 14 D Data - abstract 16 E Events 34 34 Examples 35 35 36 F 11 38 G 17 35 19 21 8 15 15 I 37 37 10 Initialization 16 8 25 L Local events 34 M Message processing 16 Messages 14 14 15 15 15 13 13 13 15 15 13 14 13 13 N 13 9 O Operations 17 19 21 25 27 28 30 32 10 P 37 11 11 44 Protocol Details 16 R 9 10 9 11 S Security 37
Revision Summary Date Revision History Revision Class Comments 3/31/2010 0.1 Major Initial Availability 4/30/2010 0.2 Editorial Revised and edited the technical content 6/7/2010 0.3 Editorial Revised and edited the technical content 6/29/2010 0.4 Editorial Changed language and formatting in the technical content. 7/23/2010 0.4 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 1.0 Major Significantly changed the technical content. 11/15/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 1.0 None No changes to the
meaning, language, or formatting of the technical content. 6/10/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 2.0 Major Significantly changed the technical content. 4/11/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.1 Clarified the meaning of the technical content. 2/11/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 2.1 None No changes to the
A Abstract data model 15 13 10 13 14 14 C 10 44 14 12 13 13 D Data model - abstract 15 E Events 33 33 Examples 34 34 35 F 10 37 G 16 34 18 20 7 14 14 I 36 36 9 Initialization 15 7 24 L events 33 M Message processing 15 Messages 13 13 14 14 14 12 12 12 14 14 12 13 12 12 N 12 8 O Operations 16 18 20 24 26 27 29 31 9 P 36 10 10 43 Protocol Details 15 R 8 9 8 10 S Security 36
ObjectId (4 bytes): An INT32 value ( section 2.2.22) that uniquely identifies the object in the serialization stream. An implementation MAY use any algorithm to generate the unique IDs. If the ObjectId is referenced by a record elsewhere in the serialization stream, the ObjectId MUST be positive. If the ObjectId is not referenced by any MemberReference in the serialization stream, then the ObjectId SHOULD be positive, but MAY be negative. ClassName (48 bytes): A LengthPrefixedString identifying the class name. Its value MUST be "System.Collections.Specialized.StringCollection". MemberCount (4 An INT32 value ([MS-DTYP] section 2.2.22) that specifies the number of members in this type. Its value MUST be 0x00000001. MemberName1 (5 bytes): A LengthPrefixedString containing the first member name. The value MUST be "data". BinaryTypeEnum1 (1 byte): A value that specifies the binary type of the first member value. The value MUST be 0x03 (SystemClass). AdditionalInfo1 (29 bytes): A LengthPrefixedString containing the name of the class of the first member value. The value MUST be "System.Collections.ArrayList". LibraryId (4 bytes): An INT32 value ([MS-DTYP] section 2.2.22) that references a record by its library ID. A BinaryLibrary record with the LibraryId MUST appear earlier in the serialization stream. DictionaryNode The DictionaryNode record defines a node in a . 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 RecordTypeEnum ObjectId ... ClassName (61 bytes) ... ... ... MemberCount ... MemberName1 ... MemberName2 ... MemberName3 ... BinaryTypeEnum1 BinaryTypeEnum2 BinaryTypeEnum3 AdditionalInfo3TypeName (61 ...
is either offered by or known to the responding server. FindServiceLocations The FindServiceLocations operation provides a mechanism for a requestor to retrieve a URL for a specified service that is either offered by or known to the responding server. Figure : FindServiceLocations message sequence diagram <wsdl:operation name="FindServiceLocations"> The SOAP operation is defined as follows. <soap:operation soapAction= "http://microsoft.com/DRM/ServerService/FindServiceLocations" /> Request Validation: The responding server MUST validate the input parameters upon receiving a FindServiceLocations request. The FindServiceLocations request MUST follow the schema specified in section . Parameter Description ServiceType MUST be a valid service type from the following list: LicensingService, CertificationService, DrmRemoteDirectoryServices, GroupExpansionService, LicensingInternalService, CertificationInternalService. Other service types are not supported. A single request MAY request URLs for multiple service types by including multiple <ServiceTypes> in the as defined in section 3.2.4.1.3.1. Data Processing: For a successful request, the responding server MUST return the appropriate service location URL. For an unsuccessful request, the server MUST return a code. The following table describes the URL expected for each service type.
Revision Summary Date Revision History Revision Comments 11/19/2010 1.0 New Released new document. 1/7/2011 2.0 Major Updated and revised the technical content. 2/11/2011 2.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 2.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 3.0 Major Updated and revised the technical content. 9/23/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 4.0 Major Updated and revised the
technical content. 3/30/2012 5.0 Updated and revised the technical content. 7/12/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 6.0 Major Updated and revised the technical content. 11/14/2013 6.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 6.0 None No changes to the meaning, language, or formatting of the
technical content. 5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 7.0 Major Significantly changed the technical content. 10/16/2015 8.0 Major Significantly changed the technical content. 9/26/2016 8.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 9.0 Major Significantly changed the technical content.
A Accessing the server for advanced scenarios 49 perform 48 48 48 29 Activating the RMS servers 43 43 Actors 22 22 42 17 18 21 B 26 C 41 52 42 18 18 19 19 20 20 19 20 19 20 19 19 19 20 20 19 20 19 20 5 Considerations 42 42 Consuming protected content client bootstrapping 47 47 47 48 33 D 36 Dependencies 19 19 20 20 19 20 19 20 19 Design intent 22 21 22 22 22 22 use case descriptions 29 26 33 36 25 34 find service locations for 28 35 perform 38 40 publish protected content 32 30 37 27 22 E 25 18 41 Examples accessing the server for advanced scenarios 49 perform 48 48 48 activating the RMS servers 43 43 consuming protected content client bootstrapping 47 47 47 48 43
offline publishing to protect content client bootstrapping 45 44 44 45 43 45 45 using online publishing to protect content 46 45 publishing license 46 47 46 34 Extensibility 50 41 19 F Find service locations for 28 35 Functional requirements 17 11 17 overview ( 9, 11) 9 17 12 9 G 5 H 41 I 50 42 7 21 5 M 50 O Overview 17 11 17 5 11 9 17 18 9 12 5 P Perform 38 40 21 50 Publish protected content 32 30 R 7 37 Requirements 17 11 42 17 41 11 9 21 9 17 12 RMS dependencies 18 with other systems 19 20 20 19 20 19 20 19 41 22 requirements 17 11 17 11 9 9 17 12 use cases 22 descriptions 29 26 33
Revision Summary Date Revision History Revision Class Comments 6/30/2015 1.0 New Released new document. 10/16/2015 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 1.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 26 21 9 C 9 39 Client 26 26 26 28 19 20 30 28 19 20 30 26 D Data model - abstract 26 21 F 9 G 5 H Higher-layer triggered events 26 22 I 32 7 Initialization 26 22 5 M Message processing 28 19 20 24 19 20 Messages 10 10 10 12 12 11 17 11 N 7 O Other local events 30 26 8 P 32 9 9 33 R 6 7 7 8 S Security 32 32 Sequencing rules 28 19 20 24 19 20 Server 21 22 22 24 19 20 26 24 19 20 26 22
6/30/2015 8.0 Significantly changed the technical content. 10/16/2015 9.0 Major Significantly changed the technical content. 7/14/2016 10.0 Major Significantly changed the technical content. 6/1/2017 10.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 11.0 Significantly changed the technical content. 12/1/2017 11.0 None No changes to the meaning, language, or formatting of the technical content.
A 16 9 C 9 38 D 16 13 E 29 Examples 29 29 33 32 30 31 F 9 G 5 H 17 I 34 34 6 17 5 L 27 M 20 Messages 13 13 11 11 12 12 11 11 N 11 12 5 O 6 P 34 33 32 30 31 8 8 36 R 5 6 5 7 S Security 34 34 20 9 11 T 27 17 38 11 17 V 9 9
Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces. Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire. The changes made to this document are listed in the following table. For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type Appendix A: Product Behavior Added Windows 10 and .NET 4.6 to applicability list. Y Content update. 6 Appendix A: Product Behavior Updated product behavior notes for Windows 10 and Windows Server 2016 Technical Preview. Y Product behavior note updated.
Index A Abstract data model 15 19 10 C 10 30 Client 15 16 16 18 17 18 15 17 18 16 D Data - abstract 15 19 F 10 G 6 H Higher-layer triggered events 16 20 I 27 27 8 Initialization 16 20 6 L Local events 18 22 M Message processing 17 21 Messages 11 14 13 11 11 N 7 18 18 O Other local events 18 22 8 8 P 27 10 10 28 R 7 8 7 9
A Abstract data 15 19 10 C 10 30 Client 15 16 16 18 17 18 15 17 18 16 D Data model - abstract 15 19 F 10 G 6 H Higher-layer triggered events 16 20 I 27 27 8 Initialization 16 20 6 L Local events 18 22 M Message processing 17 21 Messages 11 14 13 11 11 N 7 18 18 O Other local events 18 22 8 8 P 27 10 10 28 R 7 8 7 9 S Security 27 27 Sequencing rules 17 21 Server 19 20 20 22 21 22 19 21 22 20 11 11 SMTP client messages ( 14, 17) 14 13
Revision Summary Date Revision History Revision Class Comments 7/20/2007 0.1 Major MCPP Milestone 5 Initial Availability 9/28/2007 0.1.1 Editorial Changed language and formatting in the technical content. 10/23/2007 0.2 Minor Updated to use data types in MS-DTYP. 11/30/2007 0.2.1 Editorial Changed language and formatting in the technical content. 1/25/2008 0.2.2 Editorial Changed language and formatting in the technical content. 3/14/2008 0.2.3 Editorial Changed language and formatting in the technical content. 5/16/2008 1.0 Major Updated and revised the technical content. 6/20/2008 2.0 Updated and revised the technical content. 7/25/2008 2.1 Minor Clarified the meaning of the technical content.
the technical content. 11/6/2009 7.0 Major Updated and revised the technical content. 12/18/2009 8.0 Major Updated and revised the technical content. 1/29/2010 8.1 Minor Clarified the meaning of the technical content. 3/12/2010 8.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 8.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 9.0 Major Updated and revised the technical content. 7/16/2010 10.0 Major Updated and revised the technical content. 8/27/2010 10.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 11.0 Updated and revised
the technical content. 11/19/2010 11.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 11.1 Minor Clarified the meaning of the technical content. 2/11/2011 11.1 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 11.2 Minor Clarified the meaning of the technical content. 5/6/2011 11.2 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 11.3 Clarified the meaning of the technical content. 9/23/2011 11.3 None No changes to the meaning, language, or formatting of the technical content.
12/16/2011 12.0 Major Updated and revised the technical content. 3/30/2012 13.0 Major Updated and revised the technical content. 7/12/2012 14.0 Major Updated and revised the technical content. 10/25/2012 15.0 Major Updated and revised the technical content. 1/31/2013 15.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 16.0 Major Updated and revised the technical content. 11/14/2013 16.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 16.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 16.0 None No changes to the
meaning, language, or formatting of the technical content. 6/30/2015 17.0 Major Significantly changed the technical content. 10/16/2015 17.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 17.0 None No changes to the meaning, language, or formatting of the technical content. 3/16/2017 18.0 Major Significantly changed the technical content.
Revision Summary Date Revision History Revision Class Comments 8/8/2013 1.0 New Released new document. 11/14/2013 2.0 Major Updated and revised the technical content. 2/13/2014 2.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 2.0 None No changes to the meaning, language, or formatting of the technical content.
Messages Message Description Network information discovery request The User Datagram Protocol (UDP) broadcast packages are sent from protocol clients to discover protocol servers within the broadcast scope. Network information discovery response The UDP packages are sent from protocol servers to protocol clients to respond to the discovery package and to the protocol server network information. Directory Service Schema Elements None.
Protocol Examples Network Information Discovery Request 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 0x00000000 0x01 Network Information Discovery Response 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 0xFFFFFF s v r n a m e \0 0x0000 0x0100 0x0000 0x0100 0x00 0x0004 … 0x0006 … The example response package's IPv4_DNS_ADDRESS field contains four elements of structure SOCKADDR_STORAGE, and the IPv6_DNS_ADDRESS field contains six elements of structure SOCKADDR_STORAGE.