zilongwang/ReadingBank huggingface dataset:
4/30/2010 2.08 Editorial Revised and edited the technical content 6/7/2010 2.09 Editorial Revised and edited the technical content 6/29/2010 2.10 Editorial Changed language and formatting in the technical content. 7/23/2010 2.10 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 3.0 Major Significantly changed the technical content. 11/15/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 3.0 None No changes to the meaning, language, or formatting of the
technical content. 6/10/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 4.0 Significantly changed the technical content. 4/11/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 5.0 Significantly changed the technical content. 2/11/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 5.0 None No changes to the meaning, language, or formatting of the
technical content. 11/18/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 5.1 Minor Clarified the meaning of the technical content. 7/31/2014 5.1.1 Editorial Changed language and formatting in the technical content. 10/30/2014 5.2 Minor Clarified the meaning of the technical content. 3/30/2015 6.0 Major Significantly changed the technical content. 9/4/2015 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/15/2016 6.0 None No changes to the meaning,
Obtain a list of 50 Obtain an encryption key 49 Obtain focus factory capabilities 50 Other local events client 37 37 37 40 9 P 56 9 9 57 Q for a list of conferences 46 Query for the details of a conference 48 R 8 9 8 9 19 19 20 21 21 21 22 21 20 22 22 25 27 25 26 28 26 24 S Security 56 56 Sequencing client 35 36 35 35 36 36 35 34 34 35 38 38 39 40 39 39 40 40 39 38 10 T Timer events 36 focus factory 40 Timers 32 37 60 11 Triggered events client 32 delete a conference ( 33, 34) 32 34 34 33 33 Triggered events - 38 U 16 V 10 10
30 SAFERROR_CANTFORMLINKTOUSERSESSION The remote computer could not establish a connection to the specified user session. SAFERROR_RCPROTOCOLERROR A remote control protocol occurred. 33 SAFERROR_RCUNKNOWNERROR An unknown remote control occurred. 34 SAFERROR_INTERNALERROR An internal error occurred. 35 SAFERROR_HELPEERESPONSEPENDING This code is not used. 36 SAFERROR_HELPEESAIDYES This code is not used. 37 SAFERROR_HELPEEALREADYBEINGHELPED The user is already remote control. 38 SAFERROR_HELPEECONSIDERINGHELP This code is not used. 40 SAFERROR_HELPEENEVERRESPONDED The remote user did not accept the remote control request during the time-out period. 41 SAFERROR_HELPEESAIDNO The remote user denied the remote control request. 42 SAFERROR_HELPSESSIONACCESSDENIED The remote user does not have access to the specified connection string, as specified in
[MS-RAI], section 2.2. 43 SAFERROR_USERNOTFOUND The specified remote user was not found. 44 SAFERROR_SESSMGRERRORNOTINIT A remote occurred with the session manager. 45 SAFERROR_SELFHELPNOTSUPPORTED Attempting to control your own session remotely is not supported. 47 SAFERROR_INCOMPATIBLEVERSION An incompatible version was given. This message is only used in version 1. 48 SAFERROR_SESSIONNOTCONNECTED This code is not used. 50 SAFERROR_SYSTEMSHUTDOWN The remote system is shutting down. 51 SAFERROR_STOPLISTENBYUSER The remote system has stopped listening for an incoming connection. 52 SAFERROR_WINSOCK_FAILED A Winsock call has failed. 53 SAFERROR_MISMATCHPARMS A parameter mismatch has occurred. 61 PASSWORDS_DONT_MATCH An invalid password was used. This message is
SAFERROR_NOERROR No error occurred. SAFERROR_HELPEESAIDNO Sent from the novice to the expert when the novice rejects the Remote Assistance connection. This is returned when the novice rejects Remote Assistance by clicking No in the Remote Assistance Acceptance UI dialog box; otherwise, when the novice clicks Yes in this UI dialog box, the novice desktop shadowing completes, and the expert can view the novice screen. SAFERROR_INCOMPATIBLEVERSION The version number in the packet was for an incompatible version. SAFERROR_INVALIDPASSWORD MUST be returned by the novice when the password used produces an invalid Remote Assistance Connection String.
Revision Summary Date Revision History Revision Class Comments 3/2/2007 1.0 Major Updated and revised the technical content. 4/3/2007 1.1 Minor Clarified the meaning of the technical content. 5/11/2007 1.2 Minor Addressed EU feedback 6/1/2007 1.3 Clarified the meaning of the technical content. 7/3/2007 1.3.1 Editorial Changed language and formatting in the technical content. 8/10/2007 1.3.2 Editorial Changed language and formatting in the technical content. 9/28/2007 1.3.3 Editorial Changed language and formatting in the technical content. 10/23/2007 2.0 Major Converted document to unified format. 1/25/2008 2.0.1 Editorial Changed language and formatting in the technical content.
meaning, language, or formatting of the technical content. 3/25/2011 7.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 7.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 7.1 Minor Clarified the meaning of the technical content. 9/23/2011 7.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 8.0 Major Updated and revised the technical content. 3/30/2012 8.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 8.0 None No changes to the
Index A 14 9 C 9 22 15 13 D 14 13 E 13 18 F 9 G 5 H 14 I 19 19 7 14 5 L 17 M 14 Messages 10 12 10 10 N 6 O 7 P 19 9 9 20 Protocol Details 14 R 6 7 6 8 S 13 Security 19 19 14 Server 15 16 SSL_CERT_LOGON_REQ ( 15, 15) 10 10 16 12 12 9 10 T 16 14 22 10 10 14 V 9 9
Index A 6 C 16 Client 11 F 6 G 4 I 14 14 5 4 M Messages 9 9 8 8 8 8 7 7 7 7 7 N 4 O 5 P 14 5 5 15 Proxy 11 R 4 5 4 5 S 9 8 8 7 7 Security 14 14 Server 11 6 T 16 7 V 6
A Abstract data 190 drawing 166 164 157 190 resource 157 159 159 157 167 173 drawing 166 164 157 resource 157 159 159 157 167 16 C 17 211 Channel 62 146 62 146 16 190 190 drawing 166 164 157 190 resource 157 159 159 157 167 triggered events ( 169, 190) 190 overview ( 168, 190) events ( 173, 205) message processing 171 190 203 170 190 171 192 202 194 196 205 sequencing rules 171 190 203 170 190 171 192 202 194 196 timer events ( 172, 205) timers ( 168, 190) 55 55 15 D Data model - abstract 190 drawing 166 164 157 190 resource 157 159 159 157 167 173 drawing 166 164 157 resource 157 159 159 157 167 20 E 20 20 Establishing connection example negotiating protocol version 207 206 206 206 206 206
112 104 105 107 106 107 95 133 131 114 71 127 121 119 111 118 103 100 101 103 104 102 115 63 129 70 146 144 144 145 146 127 70 73 125 113 71 130 99 98 98 97 96 73 124 124 63 62 62 80 79 78 78 81 76 75 80 82 77 81 74 83 76 75 93 91 84 84 92 93 90 85 90 88 87 92 89 88 86 86 39 26 39 26 27 27 60 58 57 61 60 58 59 57 56 56 55 27 27 42 28 48 43 43 28 153 147 150 152 154 149 155 151 152 151 153 147 148 28 29 29 30 44 45 46 46 31 47 32 32
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 to applicability list. Y Content update.
Index A Abstract data client ( 19, 21) server ( 19, 23) Annotated data transfer sequence examples 37 36 36 Annotated format change sequence examples 37 37 37 Annotated initialization sequence examples 31 27 36 31 36 36 27 27 27 11 19 C 11 41 Client ( 19, 21) abstract data model ( 19, 21) higher-layer triggered events ( 19, 21) initialization ( 19, 21) local events ( 21, 23) 21 23 23 21 20 23 21 23 23 21 20 timer events ( 21, 23) timers ( 19, 21) D Data model - abstract client ( 19, 21) server ( 19, 23) Data PDU 25 23 17 Data transfer sequence annotated examples 37 36 36 23 23 23 25 25 25 E 27 annotated data transfer sequence 37 36 36 annotated format change sequence 37 37 37 annotated initialization sequence 31 27 36 31 36 36 27 27 27 F 11 18 Format Change PDU processing 23 server ( 25, 25) sending client ( 22, 23) 25 Format change sequence annotated examples 37 37 37 23 23 23 25 25 25
G 7 H Higher-layer triggered events client ( 19, 21) server ( 19, 24) I 38 Incoming Data PDU processing ( 24, 25) sending ( 22, 23) 38 8 Initialization client ( 19, 21) server ( 19, 24) 12 Initialization sequence annotated examples 31 27 36 31 36 36 27 27 27 21 22 21 21 22 22 22 22 21 24 25 24 25 24 24 25 24 24 7 L Local events client ( 21, 23) server ( 21, 26) M Message processing 21 23 23 21 20 24 25 25 24 20 12 17 18 12 12 syntax 17 18 12 12 12 17 17 13 14 16 MSG_SNDIN_VERSION packet ( 13, 18) N 8 O Open PDU 22 25 Open Reply PDU 25 22 Other local events 23 26 8 9 10 8 8 P
38 PDU (protocol data unit) 25 processing Format Change 23 server ( 25, 25) processing Incoming Data ( 24, 25) 22 25 processing Formats 21 24 processing Version 21 24 23 sending Format Change client ( 22, 23) 25 sending Incoming Data ( 22, 23) 25 22 sending Sound Formats 22 24 sending Version 21 24 10 10 39 Protocol data unit (PDU) 25 processing Format Change 23 server ( 25, 25) processing Incoming Data ( 24, 25) 22 25 processing Sound Formats 21 24 processing Version 21 24 23 sending Format Change client ( 22, 23) 25 sending Incoming Data ( 22, 23) 25 22 sending Sound Formats 22 24 sending Version 21 24 R 19 7 8 8 10 S 38 38 38 Sequencing rules 21 23 23 21 20 24 25 25 24 20 Server ( 19, 23) abstract data model ( 19, 23) triggered events ( 19, 24) initialization ( 19, 24) events ( 21, 26) 24 25 25 24 20 26 24 25 25 24 20 timer events ( 21, 26) timers ( 19, 24) 12 12 Formats PDU processing 21 24 sending 22 24 11 Syntax 17 18 12 12 T Timer events client ( 21, 23) server ( 21, 26) Timers client ( 19, 21)
NonceLen: The byte length of Nonce: A nonce for use in a key agreement operation. FinalizeKeyAgreement When populating this field of the KerbCredIsoRemoteInput structure, the CallId field MUST be set to RemoteCallKerbFinalizeKeyAgreement. struct { KEY_AGREEMENT_HANDLE* KeyAgreementHandle; ULONG KerbEType; ULONG RemoteNonceLen; [size_is(RemoteNonceLen)] PBYTE RemoteNonce; ULONG X509PublicKeyLen; [size_is(X509PublicKeyLen)] PBYTE X509PublicKey; } FinalizeKeyAgreement; KeyAgreementHandle: The key agreement to be finished. KerbEType: The Kerberos encryption type used for encryption. Kerberos parameters are documented in . RemoteNonceLen: The byte length of RemoteNonce. RemoteNonce: The nonce provided by the remote end of the key agreement. X509PublicKeyLen: The byte length of X509PublicKey. X509PublicKey: The server public key. When populating this field of the KerbCredIsoRemoteOutput structure, the CallId field MUST be set to RemoteCallKerbFinalizeKeyAgreement. struct { KERB_RPC_ENCRYPTION_KEY* SharedKey; } FinalizeKeyAgreement; SharedKey: The resulting key from the agreement. NTLM Messages NTLM calls are formatted as NtlmCredIsoRemoteInput objects, and responses are formatted as NtlmCredIsoRemoteOutput objects (section ). The structures, as defined in the IDL, are made primarily of unions. In this way, the single NtlmCredIsoRemoteInput and NtlmCredIsoRemoteOutput structure types represent multiple Input and Output message pairs as documented in the following sections. NegotiateVersion When populating this field of the NtlmCredIsoRemoteInput structure, the CallId field MUST be set to RemoteCallNtlmNegotiateVersion. struct { ULONG MaxSupportedVersion;
Revision Summary Date Revision History Revision Class Comments 7/14/2016 1.0 New Released new document. 3/16/2017 2.0 Major Significantly changed 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. 12/1/2017 3.0 None No changes to the meaning, language, or formatting of the technical content. 9/12/2018 4.0 Major Significantly changed the technical content.
Stop Streams Request The Stop Streams Request message is sent by the server over a to stop all streams of the video capture device associated with the channel. In response the client MUST send either the Success Response (section ) or Error Response (section ) message. 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 Header (2 A SHARED_MSG_HEADER (section ) structure. The Version field MUST be set to the same value as in the Select Version Response (section ) message. The MessageId field MUST be set to StopStreamsRequest (16). Sample Request The Sample Request message is sent by the server over a to request a video from the specified stream on the video capture device associated with the channel. For each Sample Request message received the client MUST send back either a Sample Response (section ) message when a new sample is ready or an Error Response (section ) message if it failed to produce a sample. 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 StreamIndex Header (2 A SHARED_MSG_HEADER (section ) structure. The Version field MUST be set to the same value as in the Select Version Response (section ) message. The MessageId field MUST be set to SampleRequest (17). StreamIndex (1 byte): An 8-bit unsigned integer containing the index of the stream being queried. This index MUST match the index in the STREAM_DESCRIPTION array returned in the Stream List Response (section ) message. Sample Response The Sample Response message is sent by the client over a when a new video is available and there are outstanding Sample Requests (section ). It contains the video sample bits. 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 StreamIndex Sample (variable) ... ... ... Header (2 bytes): A SHARED_MSG_HEADER (section ) structure. The Version field MUST be set to the same value as in the Select Version Response (section ) message. The MessageId field MUST be set to SampleResponse (18).
Index A Abstract data model client ( 30, 31) server ( 30, 37) 12 C 12 50 Client abstract data model ( 30, 31) 31 31 31 36 31 36 31 D Data model - abstract client ( 30, 31) server ( 30, 37) F 12 G 6 H Higher-layer triggered events 31 37 I 48 48 7 Initialization 31 37 6 M Message processing 31 37 Messages 13 13 N 7 O Other local events 36 41 7 P 48 12 12 49 R 6 7 7 12 S Security 48 48 Sequencing rules 31 37 Server abstract data model ( 30, 37) 37 37 37 41 37 41 37 13 12 T Timer events 36 41 Timers 31 37 50 13 Triggered events - higher-layer 31 37 V 12 12
Revision Summary Date Revision History Revision Class Comments 10/25/2012 1.0 New Released new document. 1/31/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 1.1 Clarified the meaning of the technical content. 11/14/2013 1.1 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 1.1 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 1.1 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 2.0 Major Significantly changed the technical content. 9/24/2015 2.1 Minor Clarified the meaning of the
technical content. 10/16/2015 2.1 None No changes to the meaning, language, or formatting of the technical content. 9/26/2016 2.1 None No changes to the meaning, language, or formatting of the technical content.
authentication trust traversal boundaries to transform claims from sending authority into a form acceptable to the receiving authority . Windows Data Types This document contains the Windows data types and algorithms associated with authorization. DAC, CBAC,and COM+ roles Lightweight Directory Access Protocol (LDAP) In CBAC: This protocol enables the applications to configure the claim definitions and the user and devices claims on the Active Directory server. In RBAC: This protocol enables the retrieval of authorization policies from the Active Directory Policy Server. In DAC: section 5.1.3 specifies the authorization rules. DAC, CBAC, and AzMan RBAC Component Object Model Plus (COM+) Remote Administration Protocol With regards to authorization, this protocol enables the administration interface for the role-based security configuration for the COM+ applications. COM+ roles access control
Index A 50 33 22 35 50 rbac model 48 48 C 50 58 50 Communications 34 34 34 22 Considerations 50 50 D 5 6 36 Dependencies 34 34 34 Design intent 48 36 E 34 50 51 51 Extensibility 57 50 57 34 F 22 22 G 17 H 50 I 57 50 50 19 35 5 M 57 O Overview 33 33 22 36 5 P 35 57 R 51 19 Requirements 50 50 22 35 50 S 50 22 34 34 34 50 5 33 22 System use cases 48 36 36 T 33 58 U
A Abstract data model 13 12 7 C 7 18 Client 13 13 13 14 14 13 13 D Data model - abstract 13 12 8 8 DISPLAYCONTROL_MONITOR_LAYOUT packet ( 9, 10) E 15 F 7 G 5 H Higher-layer triggered events 13 12 I 16 16 6 Initialization 13 12 5 M Messages 8 8 N 5 O Other local events 14 13 6 P 16 7 7 17 R 5 6 5 6 S Security 16 16 16 Server 12
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 3.0 Major Updated and revised the technical content. 5/15/2014 3.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 4.0 Major Significantly changed the technical content. 10/16/2015 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 5.0 Significantly changed the technical content.
A Abstract data model 13 12 7 C 7 18 Client 13 13 13 14 14 13 13 D Data model - abstract 13 12 8 8 DISPLAYCONTROL_MONITOR_LAYOUT packet ( 9, 10) E 15 F 7 G 5 H triggered events 13 12 I 16 16 6 Initialization 13 12 5 M Messages 8 8 N 5 O local events 14 13 6 P 16 7 7 17 R 5 6 5 6 S Security 16 16 16 Server 12 12 12 13 12 12 12 7 T Timer events 14 12 Timers 13 12 18 8 8 Triggered events - higher-layer 13 12 V
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 3.0 Major Updated and revised the technical content. 5/15/2014 3.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 4.0 Major Significantly changed the technical content. 10/16/2015 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 5.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 Windows Server operating system to the list of applicable products.
A Abstract data model 13 12 7 C 7 18 Client 13 13 13 14 14 13 13 D Data model - abstract 13 12 8 8 DISPLAYCONTROL_MONITOR_LAYOUT packet ( 9, 10) E 15 F 7 G 5 H Higher-layer triggered events 13 12 I 16 16 6 Initialization 13 12 5 M Messages 8 8 N 5 O Other local events 14 13 6 P 16 7 7 17 R 5 6 5 6 S Security 16 16 16 Server 12 12 12 13 12 12 12 7 T Timer events 14 12 Timers 13 12 18 8 8 Triggered events - higher-layer 13 12 V
Opening a DVC The DVC server manager initiates opening a DVC by exchanging Create PDUs with a DVC client manager. The server sends a PDU to the client, and the client responds with a PDU that indicates the status of the client endpoint creation. DVC Create Request PDU (DYNVC_CREATE_REQ) The DYNVC_CREATE_REQ (section 2.2.2.1) PDU is sent by the DVC server manager to the DVC client manager to request that a channel be opened. 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 Cmd Pri ChannelId (variable) ... ChannelName (variable) ... Cmd (4 bits): MUST be set to 0x01 (Create). Pri (2 bits): Version 1 of the Remote Desktop Protocol: Dynamic Virtual Channel Extension (as specified in section ) does not support priority classes. The client SHOULD ignore this In version 2 of the Remote Desktop Protocol: Dynamic Virtual Channel Extension, this field specifies the priority class for the channel that is being created, with the Pri field values 0, 1, 2, and 3 corresponding to PriorityCharge0, PriorityCharge1, PriorityCharge2, and PriorityCharge3, as specified in section . The method of determining priority class is the same for both client to server data and server to client data. cbChId (2 bits): Indicates the length of the ChannelId field. Value Meaning 0x00 The ChannelId field length is 1 byte. 0x01 The ChannelId field length is 2 bytes. 0x02 The ChannelId field length is 4 bytes. 0x03 Invalid value. ChannelId (variable): A variable-length 8-bit, 16-bit, or 32-bit unsigned integer. This is a identifier for the channel being created. The DVC server manager MUST ensure that this number is unique within a static virtual channel connection. ChannelName (variable): A null-terminated encoded character string. The name of the listener on the TS client with which the TS server application is requesting that a channel be opened.
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 No changes to the meaning, language, or formatting of 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
Index A Abstract data model 8 8 5 C 5 13 Client 8 9 9 9 9 9 9 9 D Data - abstract 8 8 E 10 7 10 7 Examples 10 10 F 6 G 4 H Higher-layer triggered events 9 8 I 11 11 4 Initialization 9 8 4 M Message processing 9 Messages 7 7 7 7 7 N 4 O Other local events 9 8 5 P 11 5 5 12 R 4 4 4 5 S Security 11 11 Sequencing rules 9 Server 8 8 8 8 8 8 6 T Timer events 9 8 Timers 9 8 13 7
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 No changes to the meaning, language, or formatting of 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 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 8 8 5 C 5 13 Client 8 9 9 9 9 9 9 9 D Data model - abstract 8 8 E 10 7 10 7 Examples 10 10 F 6 G 4 H Higher-layer triggered events 9 8 I 11 11 4 Initialization 9 8 4 M Message processing 9 Messages 7 7 7 7 7 N 4 O Other local events 9 8 5 P 11 5 5 12 R 4 4 4 5 S Security 11 11 Sequencing rules 9 Server 8 8 8 8 8 8 6 T Timer events 9 8 Timers 9 8 13
6/30/2015 8.0 Significantly changed the technical content. 10/16/2015 9.0 Significantly changed the technical content. 7/14/2016 10.0 Major Significantly changed the technical content. 3/16/2017 11.0 Major Significantly changed the technical content.
RDPGFX_CAPVERSION_103 0x000A0301 RDPGFX_CAPSET_VERSION103 (section ) The format of the data in the capsData and the length specified in the capsDataLength field are both determined by the version of the capability set. capsDataLength (4 bytes): A 32-bit unsigned integer that specifies the size, in bytes, of the capability set data present in the capsData field. capsData (variable): A variable-length array of bytes that contains data specific to the capability set. The number of bytes in this array is specified by the capsDataLength field. Graphics Messages RDPGFX_WIRE_TO_SURFACE_PDU_1 The RDPGFX_WIRE_TO_SURFACE_PDU_1 message is used to transfer encoded bitmap data from the server to a client-side destination surface. 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 ... surfaceId codecId pixelFormat destRect ... ... bitmapDataLength ... bitmapData (variable) ... ... header (8 bytes): An RDPGFX_HEADER structure (section ). The cmdId field MUST be set to RDPGFX_CMDID_WIRETOSURFACE_1 (0x0001), while the flags field MUST be set to zero. surfaceId (2 A 16-bit unsigned integer that specifies the ID of the destination surface. codecId (2 bytes): A 16-bit unsigned integer that specifies the codec that was used to encode the bitmap data encapsulated in the bitmapData field. Meaning
Index A Abstract data model client ( 69, 87) server ( 69, 77) 13 C 13 132 Client abstract data model ( 69, 87) higher-layer triggered events ( 69, 90) initialization ( 69, 90) 69 message processing 69 93 93 91 93 93 92 91 92 92 92 92 93 92 91 92 91 91 90 90 94 sequencing rules 69 93 93 91 93 93 92 91 92 92 92 92 93 92 91 92 91 91 90 90 events ( 69, 94) timers ( 69, 90) D Data model - abstract client ( 69, 87) server ( 69, 77) 68 E 68 F 14 G 8 H Higher-layer triggered events client ( 69, 90) server ( 69, 78) I 130 130 9 Initialization client ( 69, 90) server ( 69, 78) 8 L Local events 69 69 M Message processing client 69 93 93 91 93 93 92 91 92 92 92 92 93 92 91
92 91 91 90 90 server 69 81 81 79 81 81 79 78 80 80 79 80 80 80 79 80 79 79 78 78 Messages 15 15 N 9 O Other local events 94 82 9 P 130 11 11 131 R 8 9 9 11 S 68 Security 130 130 Sequencing client 69 93 93 91 93 93 92 91 92 92 92 92 93 92 91 92 91 91 90 90 server 69 81 81 79 81 81 79 78 80 80 79 80 80 80 79 80 79 79 78 78 Server abstract data model ( 69, 77) higher-layer triggered events ( 69, 78) initialization ( 69, 78) 69 message processing 69 81 81 79 81 81 79 78 80 80 79 80 80 80 79 80 79 79 78
Revision Summary Date Revision History Revision Class Comments 3/30/2012 1.0 New Released new document. 7/12/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.0 Major Significantly changed the technical content. 1/31/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Significantly changed the technical content. 11/14/2013 4.0 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
0x00000123 = 291 INT32 TopLevelTop – 71000000 0x00000071 = 114 INT32 TopLevelRight – 78040000 0x00000478 = 1144 INT32 TopLevelBottom – CA010000 0x000001CA = 714 UINT32 GeometryType – 02000000 0x00000002 = 2 (GEOMETRY_TYPE_REGION) UINT32 cbGeometryBuffer – 30000000 0x00000030 = 48 (bytes) BYTE pGeometryBuffer[48] – (Cast to RGNDATA) UINT8 Reserved - 00 Geometry Buffer (RGNDATA) UINT32 RGNDATA.rdh.dwSize – 20000000 0x00000020 = 32 (bytes) UINT32 RGNDATA.rdh.iType – 01000000 0x00000001 = 1 (RDH_RECTANGLES) UINT32 RGNDATA.rdh.nCount – 01000000 0x00000001 = 1 UINT32 RGNDATA.rdh.nRgnSize – 00000000 0x00000000 = 0 INT32 RGNDATA.rdh.rcBound.left - 00000000 0x00000000 = 0 INT32 RGNDATA.rdh.rcBound.top – 00000000 0x00000000 = 0 INT32 RGNDATA.rdh.rcBound.right – E0010000 0x000001E0 = 480 INT32 RGNDATA.rdh.rcBound.bottom – F4000000 0x000000F4 = 244 INT32 ((RECT*)RGNDATA.Buffer)[0].left – 00000000
0x00000000 = 0 INT32 TopLevelLeft – 00000000 0x00000000 = 0 INT32 TopLevelTop – 00000000 0x00000000 = 0 INT32 TopLevelRight – 00000000 0x00000000 = 0 INT32 TopLevelBottom – 00000000 0x00000000 = 0 UINT32 GeometryType – 00000000 0x00000000 = 0 UINT32 cbGeometryBuffer – 00000000 0x00000000 = 0 (bytes) UINT8 Reserved - 00
Index A Abstract data model 13 14 6 C 6 21 Client 13 14 13 14 13 14 11 14 13 14 13 D Data model - abstract 13 14 F 7 G 5 H Higher-layer triggered events 14 14 I 19 19 6 Initialization 13 14 5 M Message processing 14 13 14 13 Messages 8 N 5 O local events 14 14 6 P 19 6 6 20 Proxy 11 R 5 6 5 6 S Security 19 19 Sequencing rules 14 13 14 13 Server 14 14 14 14 13 14 11 14 13 14 14 7 T Timer events 14 14 Timers 13
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 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.
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 model - 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
Index A Abstract data model Participant ( 21, 23) Sharing Manager ( 21, 26) 8 Application filter 24 27 23 24 30 24 30 Applications - filtering ( 7, 11) C 8 27 37 10 22 D Data model - abstract Participant ( 21, 23) Sharing Manager ( 21, 26) E Examples 30 30 filter-updated PDU example ( 28, 30) 28 28 32 29 32 32 28 31 31 F 8 Filtering ( 7, 11) Filter-updated PDU example ( 28, 30) 24 G 6 Graphics stream control ( 8, 19, 26) 26 26 H triggered events Participant ( 22, 24) Sharing Manager ( 22, 27) I 33 33 7 Initialization Participant ( 22, 24) Sharing Manager ( 22, 26) 6 L Local events Participant ( 23, 26) Sharing Manager ( 23, 27) M Message processing Participant ( 22, 24) Sharing Manager ( 22, 27) Messages 10 filtering applications and windows ( 7, 11) graphics streams ( 8, 19) 10 participant management ( 7, 15) 10 10 11 N 7 O 12 13 11 19 19 15 17 16 13 14 14 ORDER_HDR packet ( 10, 22) 7 P 33 Participant ( 20, 23) abstract data model ( 21, 23) 26
Protocol Examples Tunnel Create Request PDU The following is an annotated dump of the Tunnel Create Request PDU (section ). 04 07 00 00 00 00 00 00 00 e2 f0 d1 08 ................ 00000010 56 7f b4 3a dc f4 b3 dc 16 92 1e 3a V..:.......: 00 -> RDP_TUNNEL_HEADER::Action and RDP_TUNNEL_HEADER::Flags RDP_TUNNEL_HEADER::Action = 0x0 (RDPTUNNEL_ACTION_CREATEREQUEST) RDP_TUNNEL_HEADER::Flags = 0x0 18 00 -> RDP_TUNNEL_HEADER::PayloadLength = 0x18 = 24 bytes 04 -> RDP_TUNNEL_HEADER::HeaderLength = 0x04 = 4 bytes 07 00 00 00 -> RDP_TUNNEL_CREATEREQUEST::RequestID = 0x00000007 00 00 00 00 -> RDP_TUNNEL_CREATEREQUEST::Reserved e2 f0 d1 08 56 7f b4 3a dc f4 b3 dc 16 92 1e 3a -> RDP_TUNNEL_CREATEREQUEST::SecurityCookie Tunnel Create Response PDU The following is an annotated dump of the Tunnel Create Response PDU (section ). 00000000 01 04 00 04 00 00 00 00 ........ 01 -> RDP_TUNNEL_HEADER::Action and RDP_TUNNEL_HEADER::Flags RDP_TUNNEL_HEADER::Action = 0x1 (RDPTUNNEL_ACTION_CREATERESPONSE) RDP_TUNNEL_HEADER::Flags = 0x0 04 00 -> RDP_TUNNEL_HEADER::PayloadLength = 0x04 = 4 04 -> RDP_TUNNEL_HEADER::HeaderLength = 0x04 = 4 bytes 00 00 00 00 -> RDP_TUNNEL_CREATERESPONSE::HrResponse = 0x00000000
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 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
Index A Abstract data model client ( 15, 18) server ( 15, 16) 10 C 10 22 Client abstract data model ( 15, 18) higher-layer triggered events ( 15, 18) initialization ( 15, 18) 15 other local events ( 16, 18) 15 events ( 16, 18) timers ( 15, 18) D Data model - abstract client ( 15, 18) server ( 15, 16) E Examples 19 19 F 10 G 5 H Higher-layer triggered events client ( 15, 18) server ( 15, 17) I 20 20 6 Initialization client ( 15, 18) server ( 15, 17) 5 M Message processing 15 15 Messages 11 N 5 O Other local events client ( 16, 18) server ( 16, 17) 6 P 20 10 10 21 R 5 6 5 10 S Security 20 20 Sequencing rules 15 15 Server abstract data model ( 15, 16) higher-layer triggered events ( 15, 17) initialization ( 15, 17) 15 other local events ( 16, 17) 15 timer events ( 16, 17) timers ( 15, 17) 10 T Timer events client ( 16, 18) server ( 16, 17) Timers client ( 15, 18) server ( 15, 17) 22 11 Triggered events - higher-layer client ( 15, 18)
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 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 7.0 None No changes to the meaning, language, or formatting of the technical content. 3/2/2016 8.0 Major Significantly changed the technical content. 7/14/2016 8.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model client ( 15, 18) server ( 15, 16) 10 C 10 22 Client abstract data model ( 15, 18) higher-layer triggered events ( 15, 18) initialization ( 15, 18) 15 local events ( 16, 18) 15 timer events ( 16, 18) timers ( 15, 18) D Data model - abstract client ( 15, 18) server ( 15, 16) E Examples 19 19 F 10 G 5 H triggered events client ( 15, 18) server ( 15, 17) I 20 20 6 Initialization client ( 15, 18) server ( 15, 17) 5 M Message processing 15 15 Messages 11 N 5 O Other local events client ( 16, 18) server ( 16, 17) 6 P 20 10 10 21 R 5 6 5 10 S Security 20 20 Sequencing rules 15 15 Server abstract data model ( 15, 16) triggered events ( 15, 17) initialization ( 15, 17) 15 local events ( 16, 17) 15 events ( 16, 17) timers ( 15, 17) 10 T Timer events client ( 16, 18) server ( 16, 17) Timers client ( 15, 18) server ( 15, 17) 22 11 Triggered events - higher-layer client ( 15, 18) server ( 15, 17) 19
Index A Abstract data model client ( 19, 20) server ( 19, 23) 27 26 8 C 19 8 34 Client abstract data model ( 19, 20) higher-layer triggered events ( 19, 20) initialization ( 19, 20) local events ( 20, 23) message processing ( 20, 20) 23 20 sequencing rules ( 20, 20) timer events ( 20, 23) timers ( 19, 20) Client printer 30 26 30 30 9 9 D Data - abstract client ( 19, 20) server ( 19, 23) 9 28 27 12 29 17 30 18 29 16 30 17 28 14 26 10 28 15 27 14 27 12 29 17 30 18 E 26 F 8 G 6 H Higher-layer triggered events client ( 19, 20) server ( 19, 23) I 32 32 7 Initialization client ( 19, 20) server ( 19, 23) 6 L Local events client ( 20, 23) server ( 20, 25) M Message processing client ( 20, 20) server ( 20, 23) Messages 9 9 9 10 9 9 N 7 O Other local events 23 25 7
P 32 8 8 7 26 10 20 23 Processing message 21 23 21 21 21 25 24 21 25 21 21 21 33 Protocol Details 19 R 7 7 7 7 8 28 S Security 32 32 Sending message 24 24 20 24 24 22 21 24 22 24 24 24 Sequencing rules client ( 20, 20) server ( 20, 23) Server abstract data model ( 19, 23) triggered events ( 19, 23) initialization ( 19, 23) local events ( 20, 25) message processing ( 20, 23) 25 23 sequencing rules ( 20, 23) timer events ( 20, 25) timers ( 19, 23) Server printer 29 29 27 29 9 8 9 T events client ( 20, 23) server ( 20, 25) Timers client ( 19, 20) server ( 19, 23) 34 9 Triggered events - higher-layer client ( 19, 20) server ( 19, 23) U 27 V 8 8 X 19
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 For more information, please contact . Section Tracking number (if applicable) and description change (Y or N) Change type Appendix A: Product Behavior Added Windows 10 to applicability list. Y Content update. 6 Appendix A: Product Behavior Updated product behavior note for Windows 10 and Windows Server 2016 Technical Preview. Y Product behavior note updated.
Index A Abstract data model client ( 28, 29) server ( 28, 33) 10 14 C 38 11 45 Client abstract data ( 28, 29) higher-layer triggered events ( 28, 29) initialization ( 28, 29) local events ( 29, 32) message processing ( 28, 29) 32 sequencing rules ( 28, 29) timer events ( 29, 32) timers ( 28, 29) 20 14 27 17 19 13 20 22 D Data model - abstract client ( 28, 29) server ( 28, 33) Device addition/removal messages 30 34 37 20 subprotocol ( 30, 34) 38 E Examples 38 37 38 37 F 11 G 7 H Higher-layer triggered events client ( 28, 29) server ( 28, 33) I 42 42 42 8 Initialization client ( 28, 29) server ( 28, 33) 19 29 device IO sub-protocol ( 30, 34) 33 7 25 25 L Local events client ( 29, 32) 29 M Message processing client ( 28, 29) server ( 28, 33) Messages 18 12 12 12 N
8 O local events 32 36 8 P 42 42 PNP Device I/O subprotocol 30 introduction ( 9, 18) 34 18 PNP Device Info subprotocol 29 14 13 9 12 33 12 37 15 12 10 10 43 R 23 22 8 8 8 10 S 42 42 42 Sequencing rules client ( 28, 29) server ( 28, 33) Server abstract data model ( 28, 33) triggered events ( 28, 33) initialization ( 28, 33) 29 message processing ( 28, 33) 36 sequencing ( 28, 33) events ( 29, 36) timers ( 28, 33) 19 18 13 18 26 11 12 T Timer events client ( 29, 32) server ( 29, 36) Timers client ( 28, 29) server ( 28, 33) 45 12 12 Triggered events - higher-layer client ( 28, 29) server ( 28, 33) V 11 11 W 24 23
and formatting in the technical content. 4/10/2009 4.0 Major Updated and revised the technical content. 5/22/2009 5.0 Major Updated and revised the technical content. 7/2/2009 6.0 Updated and revised the technical content. 8/14/2009 7.0 Major Updated and revised the technical content. 9/25/2009 7.1 Clarified the meaning of the technical content. 11/6/2009 7.1.1 Editorial Changed language and formatting in the technical content. 12/18/2009 8.0 Major Updated and revised the technical content. 1/29/2010 9.0 Major Updated and revised the technical content. 3/12/2010 10.0 Major Updated and revised the technical content.
Index A Abstract data model client ( 28, 29) server ( 28, 33) 10 14 C 38 11 45 Client abstract data model ( 28, 29) higher-layer triggered events ( 28, 29) initialization ( 28, 29) local events ( 29, 32) message processing ( 28, 29) 32 sequencing ( 28, 29) timer events ( 29, 32) timers ( 28, 29) 20 14 27 17 19 13 20 22 D Data - abstract client ( 28, 29) server ( 28, 33) Device addition/removal messages 30 34 37 20 subprotocol ( 30, 34) 38 E Examples 38 37 38 37 F 11 G 7 H triggered events client ( 28, 29) server ( 28, 33) I 42 42 42 8 Initialization client ( 28, 29) server ( 28, 33) 19 29 device IO sub-protocol ( 30, 34) 33 7 25 25 L Local events client ( 29, 32) 29 M Message processing client ( 28, 29) server ( 28, 33) Messages 18 12 12 12 N 8 O Other local events 32 36 8 P 42 42 PNP Device I/O subprotocol 30 introduction ( 9, 18) 34 18 PNP Device Info subprotocol 29 14
Index A Abstract data model 10 11 6 C 6 18 Client 10 10 10 11 10 11 10 10 11 10 D Data - abstract 10 11 E 13 F 6 G 5 H Higher-layer triggered events 10 11 I 14 14 6 Initialization 10 11 5 L Local events 11 12 M Message processing 10 11 Messages 8 8 8 N 5 O Other local events 11 12 6 6 P 14 6 6 15 R 8 RDP_PRECONNECTION_PDU_V1 ( 10, 11)
Processing a Client Close Response Message The server responds to the application with the result of the close response received from the client. Processing a Client Write Response Message The server forwards the result of the write response to the application that requested the write operation. Processing a Client Read Response Message The server forwards the result of the read response to the application that initiated the read operation. Processing a Client Device Control Response Message The server forwards the result of the device control response to the application that initiated the operation. Timer Events There are no timer events. Other Local Events There are no other local events.
Index A Abstract data model client ( 14, 14) server ( 14, 19) 8 C 8 29 Client abstract data model ( 14, 14) 12 12 23 13 15 higher-layer triggered events ( 14, 15) initialization ( 14, 15) local events ( 14, 18) message processing ( 14, 15) 18 12 sequencing rules ( 14, 15) timer events ( 14, 18) timers ( 14, 15) 12 9 17 9 9 16 D Data model - abstract client ( 14, 14) server ( 14, 19) 18 7 10 12 10 13 10 12 10 12 10 12 E Examples 23 23 21 22 F 8 G 6 H Higher-layer triggered events client ( 14, 15) server ( 14, 19) I 26 26 7 Initialization client ( 14, 15) 7 server ( 14, 19) 6 23 L Local events client ( 14, 18) server ( 14, 20) M Message processing client ( 14, 15) server ( 14, 19) Messages 9 9 9 9 9 9 N 6 O local events 18 20 9 7 P 26 20 20 19 20
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 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 to applicability list. Y Content update.
Revision Summary Date Revision History Revision Class Comments 11/14/2013 1.0 New Released new document. 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 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 8 8 5 C 5 13 Client 8 9 8 9 9 9 9 8 D Data model - abstract 8 8 F 5 G 4 H Higher-layer triggered events 9 8 I 11 11 4 Initialization 8 8 4 M Messages 6 6 6 N 4 O Other local events 9 8 4 P 11 5 5 12 10 R 6 9 8 6 4 4 4 5 S Security 11 11 Server 8 8 8 8 8 8 8 8 5 T Timer events 9 8 8 Timers 8 8 13 6 Triggered events - higher-layer 9 8 V
Revision Summary Date Revision History Revision Comments 11/14/2013 1.0 New Released new document. 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 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.
Appendix A: Product Behavior The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products. Windows 8.1 operating system Windows Server 2012 R2 operating system Windows 10 operating system Windows Server 2016 operating system Windows Server 2019 operating system Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription. Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition. Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.
Index A Abstract data 8 8 5 C 5 13 Client 8 9 8 9 9 9 9 8 D Data model - abstract 8 8 F 5 G 4 H Higher-layer triggered events 9 8 I 11 11 4 Initialization 8 8 4 M Messages 6 6 6 N 4 O Other local events 9 8 4 P 11 5 5 12 10 R 6 9 8 6 4 4 4 5 S Security 11 11 Server 8 8 8 8 8 8 8 8 5 T Timer events 9 8 8 Timers 8 8 13 6 Triggered events - 9 8 V