zilongwang/ReadingBank huggingface dataset:
Revision Summary Date Revision History Revision Class Comments 12/5/2008 0.1 Major Initial Availibility 1/16/2009 0.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.1.3 Editorial Changed language and formatting in the technical content. 5/22/2009 0.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 1.0 Updated and revised the technical content. 8/14/2009 2.0 Major Updated and revised the technical content. 9/25/2009 3.0 Major Updated and revised the technical content. 11/6/2009 3.0.1 Editorial Changed language and formatting in the
technical content. 12/18/2009 3.0.2 Editorial Changed language and formatting in the technical content. 1/29/2010 3.1 Minor Clarified the meaning of the technical content. 3/12/2010 3.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 3.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 4.0 Major Updated and revised the technical content. 7/16/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 4.0 None No changes to the meaning,
language, or formatting of the technical content. 11/19/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 5.0 Major Updated and revised the technical content. 2/11/2011 5.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 5.0 None No changes to the meaning, language, or formatting of 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 6.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 6.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 6.1 Minor Clarified the meaning of the technical content. 11/14/2013 6.1 None No changes to the meaning,
Index A Abstract data 20 22 10 Assertion element 14 14 25 B BinarySecurityToken element 13 13 24 Binding extensions 19 18 18 18 18 C 10 35 Client 20 20 20 21 20 21 20 31 31 29 29 30 30 D Data model - abstract 20 22 E Examples 25 24 31 31 29 29 30 30 27 27 24 25 27 24 F 11 G 6 H Higher-layer triggered events 20 22 I 32 32 8 Initialization 20 22 6 27 27 M Messages 17 12 12 12 N 7 O Other local events 21 23 9 P 32 10 10 33 R
Index A Abstract data model 12 13 13 13 13 6 C 7 23 Client 12 12 12 13 12 13 12 12 13 12 D Data model - abstract 12 13 13 13 13 E 17 F 7 G 5 H Higher-layer triggered events 12 14 application 15 14 14 14 I 19 19 6 Initialization 12 13 5 L Local events 13 16 M 8 8 Message processing 12 15 Messages 8 8 8 8 N 5 O Other local events 13 16 6 P
5/6/2011 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 2.1 Minor Clarified the meaning of the technical content. 9/23/2011 2.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 2.1 None No changes to the meaning, language, or formatting of the technical content. 3/30/2012 2.1 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 2.1 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.1 None No changes to the meaning, language, or formatting
Added 0x1FCC 0x1FC3 GREEK SMALL LETTER ETA WITH PROSGEGRAMMENI Subtracted 0x1FCC 0x1FCC GREEK CAPITAL LETTER ETA WITH PROSGEGRAMMENI Ignored any code point > 0xFFFF same value (itself)
Revision Summary Date Revision History Revision Class Comments 6/30/2015 1.0 New Released new document. 10/16/2015 2.0 Major Significantly changed the technical content. 7/14/2016 3.0 Major Significantly changed the technical content. 3/16/2017 4.0 Major Significantly changed the technical content. 6/1/2017 4.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 5.0 Major Significantly changed the technical content.
</s:header> <s:body> <s:code> <s:subcode> <s:value>s:authorization</s:value> </s:subcode> </s:code> <s:reason> <s:text xml:lang="en-us">This User is not authorized to enroll</s:text> </s:reason> </s:fault> </s:body> </s:envelope> Subcode Error Description HRESULT s: MessageFormat Message format is bad. 80180001 s: Authentication User not recognized. 80180002 s: Authorization User not allowed to enroll. 80180003 s: CertificateRequest Failed to get certificate. 80180004 s: EnrollmentServer 80180005 a: InternalServiceFault The server hit an unexpected issue. 80180006 a: InvalidSecurity Cannot parse the security header. 80180007 Here is an example of deviceenrollmentserviceerror element: <s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing"> <s:header> <a:action <activityid correlationid="2493ee37-beeb-4cb9-833c-cadde9067645" <a:relatesto>urn:uuid:urn:uuid:0d5a1441-5891-453b-becf-a2e5f6ea3749</a:relatesto> </s:header> <s:body> <s:fault> <s:code>
Index A Abstract data model 49 13 16 16 C 13 101 16 D Data model - abstract 49 Events 53 53 F 13 G 6 16 I 96 96 10 Initialization 49 6 L events 53 M Message processing 49 Messages 16 16 16 16 15 16 15 16 15 15 N 15 9 O Operations 49 10 P 96 13 13 99 R 9 10 9 13 S Security 96 96 Sequencing 49 Server 49 49 49 53 49 49 53 49 16 14 Syntax 15 T Timer events 53 Timers 49 101 15 Types 16 16
Revision Summary Date Revision History Revision Class Comments 6/30/2015 1.0 New Released new document. 10/16/2015 2.0 Major Significantly changed the technical content. 7/14/2016 3.0 Major Significantly changed the technical content. 3/16/2017 4.0 Major Significantly changed the technical content. 6/1/2017 4.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 5.0 Major Significantly changed the technical content. 12/1/2017 6.0 Major Significantly changed the technical content.
Change Tracking This section identifies changes that were made to this document 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 OSEdition Enumeration #defines to the end of the enumeration list. Major DiscoveryResponse 8286 : Added missing angle bracket to first xsd:element statement, RequestSecurityToken using Federated Authentication 8218 : Added normative definitions of UXInitiated, ExternalMgmtHint, DomainName, and BootstrapDomainJoin.. Major RequestSecurityToken using Certificate Authentication 8218 : Added normative definitions of UXInitiated, ExternalMgmtHint, and DomainName, and updated behavior note. RequestSecurityToken On-Premise Authentication 8218 : Added normative definitions of UXInitiated, ExternalMgmtHint, and DomainName, and updated behavior note. Major
Index A Abstract data 49 13 16 16 C 13 102 16 D Data model - abstract 49 Events 53 53 F 13 G 6 16 I 97 97 10 Initialization 49 6 L events 53 M Message processing 49 Messages 16 16 16 16 15 16 15 16 15 15 N 15 9 O Operations 49 10 P 97 13 13 100 R 9 10 9 13 S Security 97 97 Sequencing rules 49 Server 49 49 49 53 49 49 53 49 16 14 Syntax 15 T events 53 Timers 49 102 15 Types 16 16
Revision Summary Date Revision History Revision Class Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 Major Significantly changed the technical content. 5/15/2014 3.0 Major Significantly changed the technical content. 6/30/2015 3.0 None No changes to the meaning, language, or formatting of the technical content. 10/16/2015 4.0 Major Significantly changed the technical content. 7/14/2016 5.0 Major Significantly changed the technical content. 6/1/2017 5.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 17 12 14 14 C 12 50 13 D Data model - abstract 17 E Events 21 21 F 12 47 G 5 14 I 46 46 8 Initialization 17 5 L Local events 21 M Message processing 17 Messages 14 14 13 13 13 14 13 14 13 13 N 13 8 O Operations 17 9 P 46 12 12 49 R 8 8 8 11 S Security 46 46 Sequencing rules 17 Server 17 17 17 21 17 17 21 17 14 12 Syntax 13 T events 21 Timers 17 50 13 13 14
Revision Summary Date Revision History Revision Class Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 Major Significantly changed the technical content. 5/15/2014 3.0 Major Significantly changed the technical content. 6/30/2015 3.0 None No changes to the meaning, language, or formatting of the technical content. 10/16/2015 4.0 Significantly changed the technical content. 7/14/2016 5.0 Major Significantly changed the technical content. 6/1/2017 5.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 17 12 14 14 C 12 50 13 D Data model - abstract 17 E Events 21 21 F 12 47 G 5 14 I 46 46 8 Initialization 17 5 L Local events 21 M Message processing 17 Messages 14 14 13 13 13 14 13 14 13 13 N 13 8 O Operations 17 9 P 46 12 12 49 R 8 8 8 11 S Security 46 46 Sequencing rules 17 Server 17 17 17 21 17 17 21 17 14 12 Syntax 13 T Timer events 21 Timers 17 50 13 13 14
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 B: Product Behavior Added Windows 10 to the applicability list. Y Content update.
Index A 26 9 C 9 38 32 25 Common 26 26 26 31 31 26 D 18 26 E 17 18 18 18 32 F 9 G 5 H 26 I 35 35 6 26 5 18 L 31 M Messages 20 12 17 16 11 19 11 10 18 36 N 11 5 O 6 P 35 9 9 37 Protocol Details 25 R References 6 5 8
Index A 26 9 C 9 38 32 25 Common 26 26 26 31 31 26 D 18 26 E 18 18 18 19 32 F 9 G 5 H 26 I 35 35 6 26 5 18 L 31 M Messages 21 12 18 17 11 19 11 10 19 36 N 11 5 O 6 P 35 9 9 37 Protocol Details 25 R References 6 5 8 S Security 35 35 25 9 SyncML 27 30 T 31 26 38 10 18 11 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 Transport Updated for Windows 10. Y Content update. 2.1 Transport 73068 : Added details on GenericAlert, as specified in Y Content update. Meta Updated for Windows 10. Y Content update. Alert Updated for Windows 10. Y Content update. 2.2.7.2 Alert 73068 : Added details on GenericAlert, as specified in Y Content update. Triggered Events 6602 : Added details of management sessions Y New content added.
Index A 26 9 C 9 38 32 25 Common 26 26 26 31 31 26 D 18 26 E 18 18 18 19 32 F 9 G 5 H 26 I 35 35 6 26 5 18 L 31 M Messages 21 12 18 17 11 19 11 10 19 36 N 11 5 O 6 P 35 9 9 37 Protocol Details 25 R References 6 5 8 S Security 35 35 25 9 SyncML 27 30 T 31 26 38 10 18 11 V 9 9
Revision Summary Date Revision History Revision Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 Major Updated and revised the technical content. 5/15/2014 3.0 Updated and revised the technical content. 6/30/2015 4.0 Major Significantly changed the technical content. 10/16/2015 5.0 Significantly changed the technical content. 7/14/2016 6.0 Significantly changed the technical content. 6/1/2017 6.0 None No changes to the meaning, language, or formatting of the technical content.
Index A 26 9 C 9 38 32 25 Common 26 26 26 31 31 26 D 18 26 E 18 18 18 19 32 F 9 G 5 H 26 I 35 35 6 26 5 18 L 31 M Messages 21 12 18 17 11 19 11 10 19 36 N 11 5 O 7 P 35 9 9 37 Protocol Details 25 R References 6 5 8 S Security 35 35 25 9 SyncML 27 30 T 31 26 38 10 18 11 V 9 9
Revision Summary Date Revision History Revision Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 Major Updated and revised the technical content. 5/15/2014 3.0 Major Updated and revised the technical content. 6/30/2015 4.0 Major Significantly changed the technical content. 10/16/2015 5.0 Major Significantly changed the technical content. 7/14/2016 6.0 Major Significantly changed the technical content. 6/1/2017 6.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 7.0 Major Significantly changed the technical content.
Attributes: None. Replace The Replace element specifies the SyncML command to replace data items. The element has the following syntax: <Replace>(CmdID, Meta?, Item+)</Replace> Parent Elements: , Restrictions: The element type is required and specifies the unique identifier for the command in the . The element is optional. When Meta is present, it specifies the meta-information to be used for the command. One or more element types MUST be specified. The Item elements contain the data items to replace. Content Model: (CmdID, Meta?, Item+) Attributes: None. Results The Results element specifies the SyncML command to return the results of a command. The element has the following syntax: MsgRef?, CmdRef, Cmd, Meta?, Item+)</Results> Parent Elements: Restrictions: The element type is required and specifies the unique identifier for the command in the SyncML message. The element is optional. When MsgRef is present, it specifies the MsgID of the associated SyncML request from the originator. When MsgRef is not present in a Results element type, MsgRef MUST be processed as having a value of "1". The element type specifies the CmdID of the associated SyncML request from the originator. When CmdRef is not present in a Results element type, the response status code is associated with a CmdID value of "1". The element type specifies the Cmd of the associated SyncML request from the originator. One or more element types MUST be specified to contain the results. The element specified within the Item element SHOULD be a relative corresponding to the command sent by the originator. The element specified within the Item element SHOULD be a property corresponding to the Get command sent by the originator. The element specified within the Item element SHOULD be the value for the property specified in the LocURI element.
Index A 28 9 C 9 40 34 27 Common 28 28 28 33 33 28 D 19 28 E 19 19 20 20 34 F 9 G 5 H 28 I 37 37 6 28 5 20 L 33 M Messages 22 13 19 18 13 21 13 11 20 38 N 13 5 O 7 P 37 9 9 39 Protocol Details 27 R References 6 5 8 S Security 37 37 27 10 SyncML 29 32 T 33 28 40 11 19 13 V 9 9
Revision Summary Date Revision History Revision Class Comments 7/16/2010 1.0 New First Release. 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 2.0 None No changes to the meaning, language, or formatting of 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.
7/14/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 6.0 Major Significantly changed the technical content. 9/15/2017 7.0 Major Significantly changed the technical content. 12/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content.
Subtracted 0x03DF 0x03DE GREEK LETTER KOPPA Subtracted 0x03E1 0x03E0 GREEK LETTER SAMPI Subtracted 0x0450 0x0400 CYRILLIC CAPITAL LETTER IE WITH GRAVE Subtracted 0x045D 0x040D CYRILLIC CAPITAL LETTER I WITH GRAVE Subtracted 0x048D 0x048C CYRILLIC CAPITAL LETTER SEMISOFT SIGN Subtracted 0x048F 0x048E CYRILLIC CAPITAL LETTER ER WITH TICK Subtracted 0x04ED 0x04EC CYRILLIC CAPITAL LETTER E WITH DIAERESIS Added 0x03C2 0x03A3 GREEK CAPITAL LETTER SIGMA Subtracted 0x03C2 0x03C2 SMALL LETTER FINAL SIGMA For Windows and later and for Windows Server 2008 and later, the compound file implementation conforms to the Unicode 5.0 Default Case Conversion Algorithm, simple case folding , with the following exceptions. or subtracted from Unicode 5.0 Lowercase UTF-16 code Uppercase UTF-16 code Uppercase Unicode name
Index A 12 C 44 13 23 22 23 20 17 21 39 D 13 Details 13 22 Directory sectors 23 27 23 28 27 E 31 31 31 32 32 33 33 36 36 37 37 31 F 20 12 39 G 6 H Header ( 17, 31) I 9 5 L 12 M 21 N 9 O 13 9 P 40 R 29 28 9 9 9 11 27 S 32 32 33 33 36 36 37 37 15 Security 39 39 39 Security considerations 39 39 29 Structures 13 T 31 44 U
Revision Summary Date Revision History Revision Class Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 Major Updated and revised the technical content. 5/15/2014 3.0 Updated and revised the technical content. 6/30/2015 4.0 Major Significantly changed the technical content. 10/16/2015 5.0 Major Significantly changed the technical content. 7/14/2016 6.0 Major Significantly changed the technical content. 6/1/2017 6.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 7.0 Significantly changed the technical content.
Attributes: None. SyncBody The SyncBody element type serves as the container for the body or contents of the . The element type has the following syntax: <SyncBody>((Atomic | Exec | Get | Results | Status | Add | Replace | Delete)+, Final?)</SyncBody> Parent Element: Restrictions: None. Content (( | | | | | | | )+, ?) Attributes: None. Data Description Elements Data description elements are used as container elements for data exchanged in a message. Data The Data element type provides a container for discrete SyncML data. The element type has the following syntax: <Data>(#PCDATA)</Data> Parent Elements: , Restrictions: Data can either be parsable character content or markup content. If Data contains any markup content, the namespace for the element types MUST be declared on the element types in the content. When Data is specified in an Item, the element type specifies the item data. When Data is specified in a Status, the element type specifies the request status code type. Content Model: (#PCDATA) Attributes: None. Item The Item element type provides a container for item data. The element type has the following syntax: <Item>(#PCDATA)</Item> Parent Elements: , , , , , , Restrictions: When the source URI for the item data is an external entity, the element is not present and the recipient retrieves the data from the specified network location. When Data is present in Item, it MUST be the last element in Item. The element type can be a relative URL when used in the or element types for any of the SyncML commands. Note that this restriction is not captured by the SyncML DTD.
A 28 9 C 9 40 34 27 Common 28 28 28 33 33 28 D 19 28 E 19 19 20 20 34 F 9 G 5 H 28 I 37 37 6 28 5 20 L 33 M Messages 22 13 19 18 13 21 13 11 20 38 N 13 5 O 7 P 37 9 9 39 Protocol Details 27 R References 6 5 8 S Security 37 37 27 10 SyncML 29 32 T 33 28 40 11 19 13 V 9 9
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 Capability Attribute Editorial revision to the description for Length - 'Is' to 'is'. Minor WSC Vendor Extension Attribute Example 7384 : Revised representation for Capability in example to match definition. Minor 4.1 WSC Vendor Extension Attribute Example 7385 : Revised UTF-8 coding of bytes to match HostName in example - 'WfdSurfaceHub' to 'WFDSurfaceHub'. Minor
Index A Abstract data model 19 20 10 Attributes 17 16 18 17 B 17 C 16 10 25 18 E Examples 22 22 22 F 10 14 G 5 H Higher-layer triggered events 19 20 17 I 23 7 Initialization 19 20 5 M Message processing events 19 20 Messages 14 12 15 15 15 13 13 12 16 12 Miracast Sink 19 7 Miracast Source 20 7 15 N 6 O Other local events 19 21 7 P 10 10 24 Protocol examples 22 22 22 R 7 6 7 6 10 15 S 23 7 Sequencing Rules 19 20 7 15 13 22 10
Revision Summary Date Revision History Revision Class Comments 3/16/2017 1.0 New Released new document. 6/1/2017 1.1 Minor Clarified the meaning of the technical content. 3/16/2018 2.0 Major Significantly changed the technical content.
HostName (variable): The Miracast Sink host name string, encoded in . The host name is not fully qualified. A Sink having a host name that contains the period ('.') character MUST NOT be used for Miracast over Infrastructure connections. BSSID Attribute The attribute specifies the for the associated with the wireless network. This attribute is optional in the Vendor Extension attribute, but it MUST NOT appear more than once. 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 AttributeID Length BSSID ... AttributeID (2 The BSSID attribute ID, which is 0x2003. Length (2 bytes): The length of the BSSID field, in bytes, which is 0x0006. BSSID (6 bytes): The BSSID for the associated . Connection Preference Attribute The Connection Preference attribute indicates the preference of transports for the connection of the Miracast Sink to the Miracast Source. The Sink MAY include a Connection Preference attribute in the Vendor Extension attribute, but it MUST NOT appear more than once. 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 AttributeID Length ConnectionPreferenceList AttributeID (2 bytes): The Connection Preference attribute ID, which is 0x2004. Length (2 bytes): The length of the ConnectionPreferenceList field, in bytes, which is 0x0004. ConnectionPreferenceList (4 bytes): A packed array with room for 8 connection transport IDs, in descending order of preference. The following IDs are defined. Transport ID Transport 0x1 Miracast over Infrastructure 0x2 The following is an example of a preference list buffer with Miracast over Infrastructure preferred over WFD. 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
Receive Connection Request 8371 : Added Receive Connection Request section. Major Message Processing Events and Sequencing Rules 8317 : Added support for skipping source name resolution. Major Receive Beacon with Vendor Extension Attribute 8371 : Added Receive Beacon with Vendor Extension Attribute section. Major Receive Probe Response with Vendor Extension Attribute 8371 : Added Receive Probe Response with Vendor Extension Attribute section. Major Host Name Resolution Complete 8371 : Added Host Name Resolution Complete section. Major Miracast Connection Complete 8371 : Added Miracast Connection Complete section. Major RTSP Connection Accepted 8371 : Added RTSP Connection Accepted section. Major
Index A Abstract data model 20 21 10 Attributes 17 16 17 16 B 17 C 16 11 27 17 E Examples 24 24 24 F 11 14 G 5 H Higher-layer triggered events 21 22 16 I 25 8 Initialization 20 22 5 M Message processing events Miracast Sink ( 21, 22) Messages 13 12 12 13 13 12 15 21 20 20 Message processing events and sequencing rules ( 21, 22) 21 20 20 Miracast Source 21 22 22 23 23 22 21 Miracast TLVs 14 14 15 13 N 7 O local events 23 8 P 10 10 26 Protocol Details 19 Protocol examples 24 24 24 R 7 8 7 10 14 S
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 chunkLen MID hr playIncarnation packetPayloadSize funnelName (variable) ... chunkLen (4 Length in chunks of the message. A chunk is 8 bytes. MID (4 Message ID. For this message, the value MUST be 0x00040002. hr (4 A 32-bit field. MUST be set to 0x00000000. playIncarnation (4 bytes): A 32-bit field. SHOULD be set to 0x00000000. It MUST be ignored by the receiver.<6> packetPayloadSize (4 A 32-bit field. SHOULD be set to 0x00000000. It MUST be ignored by the receiver.<7> funnelName (variable): A variable size array of Unicode characters. MUST be set to the Unicode character string "Funnel Of The Gods".<8> LinkMacToViewerReportDisconnectedFunnel The LinkMacToViewerReportDisconnectedFunnel message is sent by the server in response to a message from the client when there is an error processing the 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 chunkLen MID hr playIncarnation chunkLen (4 bytes): Length in chunks of the message. A chunk is 8 bytes. MID (4 bytes): Message ID. For this message, the value MUST be 0x00040003. hr (4 bytes): Result of processing the LinkViewerToMacConnectFunnel (section 2.2.4.18) message. For HRESULT codes, see .
Index A Abstract data model 49 67 9 ASF data packets ( 66, 76) ASF file header ( 64, 69, 74) Authentication sequence example 91 92 91 C 9 100 Client 49 52 51 67 58 67 49 58 67 51 11 13 55 D 17 Data model - abstract 49 67 17 11 11 E Examples 91 91 82 92 84 86 84 87 87 F 10 57 G 82 7 H Higher-layer triggered events 52 69 I 94 94 8 Initialization 51 68 7 L 69 64 20 58 20 60 23 60 23 66 59 24 62 26 63 28 61 29 65 30 65 31 67 31 64 62 32 75 34 78 35 LinkViewerToMacConnect ( 52, 70) 35 71 37 71 38 78 38 72
39 78 40 LinkViewerToMacReadBlock ( 62, 73) 41 73 42 LinkViewerToMacStartPlaying ( 53, 75) 43 LinkViewerToMacStartStriding ( 54, 77) 44 77 46 75 46 Local events 67 79 M Message processing 58 70 19 Messages 17 11 11 19 47 sending 58 70 11 18 11 19 84 N 55 8 33 O Other local events 67 8 P Packet - receiving ( 58, 70) 84 86 84 63 94 87 56 9 9 95 95 R 8 8 8 9 24 77 47 47 57 52 S Security 94 94 87 Sequencing rules 58 70 Server 67 69 68 79 70 70 events 79 79 68 10 53 56 47 11 11 19 T 79 86 18 18 Timer events 67 server 79 79 Timers 51 68 100 11 Triggered events - higher-layer 52 69 19 U
technical content. 11/6/2009 13.0 Updated and revised the technical content. 12/18/2009 14.0 Major Updated and revised the technical content. 1/29/2010 15.0 Major Updated and revised the technical content. 3/12/2010 15.0.1 Editorial Changed language and formatting in the technical content. 4/23/2010 16.0 Major Updated and revised the technical content. 6/4/2010 16.0.1 Editorial Changed language and formatting in the technical content. 7/16/2010 16.0.1 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 16.0.1 None No changes to the meaning, language, or formatting of the technical content.
Packets of type joiner, lock, and wsgroup send MUST be present as fixed-length data structures. The operation packet length varies per operation message type. The operation packet length MUST be used to determine whether a variable-length data packet follows. Each data packet MUST begin with an unsigned 32-bit integer length field. For more information on each packet type, refer to sections specified by the table below. The late joiner protocol is defined as a subset of NetMeeting Object Manager messages. For more information, to . Packet Name Packet Type Description of Packet Function joiner Requests user ID discovery. joiner Replies to OMNET_HELLO. lock Requests a lock on a /object. lock Grants a lock on a workset/object. lock Denies a lock on a workset/object. lock Sends notification granting a lock request. lock Unlocks a workset/object. wsgroup send Requests the current contents of a after a late join. wsgroup send Notifies a late joiner that it knows about all worksets currently in use. wsgroup send Notifies the late joiner that all workset group contents have been sent. wsgroup send Denies a late joiner catch-up request. operation Requests that an Object
Index A 157 30 30 155 12 17 17 52 52 153 146 B 14 82 14 15 C 55 55 55 55 150 13 183 113 113 113 56 56 14 60 60 36 37 37 36 37 37 34 34 17 17 31 31 32 32 D 157 64 65 65 E 66 66 174 69 69 F 13 113 113 41 41 G 38 38 38 38 8 35 35 H 157 43 43 I 44 44 45 177 177 11 157 43 43 8 L 73 73 173 M 75 75 78 78 157 Messages 17 153 113 14
Revision Summary Date Revision History Revision Class Comments 7/20/2007 0.1 Major MCPP Milestone 5 Initial Availability 9/28/2007 1.0 Major Updated and revised the technical content. 10/23/2007 1.0.1 Editorial Changed language and formatting in the technical content. 11/30/2007 2.0 Updated and revised the technical content. 1/25/2008 2.0.1 Editorial Changed language and formatting in the technical content. 3/14/2008 2.1 Minor Clarified the meaning of the technical content. 5/16/2008 2.1.1 Editorial Changed language and formatting in the technical content. 6/20/2008 2.1.2 Editorial Changed language and formatting in the technical content. 7/25/2008 2.1.3 Editorial Changed language and formatting
in the technical content. 8/29/2008 3.0 Major Updated and revised the technical content. 10/24/2008 3.0.1 Editorial Changed language and formatting in the technical content. 12/5/2008 3.0.2 Editorial Changed language and formatting in the technical content. 1/16/2009 3.0.3 Editorial Changed language and formatting in the technical content. 2/27/2009 3.0.4 Editorial Changed language and formatting in the technical content. 4/10/2009 3.0.5 Editorial Changed language and formatting in the technical content. 5/22/2009 4.0 Major Updated and revised the technical content. 7/2/2009 4.1 Minor Clarified the meaning of the technical content.
8/14/2009 4.1.1 Editorial Changed language and formatting in the technical content. 9/25/2009 4.2 Minor Clarified the meaning of the technical content. 11/6/2009 5.0 Major Updated and revised the technical content. 12/18/2009 5.0.1 Editorial Changed language and formatting in the technical content. 1/29/2010 5.1 Minor Clarified the meaning of the technical content. 3/12/2010 5.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 5.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 5.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 6.0 Major Updated and revised the
9/23/2011 10.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 10.1 None No changes to the meaning, language, or formatting of the technical content. 3/30/2012 10.1 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 10.2 Minor Clarified the meaning of the technical content. 10/25/2012 11.0 Major Updated and revised the technical content. 1/31/2013 11.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 12.0 Major Updated and revised the technical content. 11/14/2013 12.0 None No changes to the meaning, language,
Revision Summary Date Revision History Revision Class Comments 7/20/2007 0.1 MCPP Milestone 5 Initial Availability 9/28/2007 1.0 Major Updated and revised the technical content. 10/23/2007 1.0.1 Editorial Changed language and formatting in the technical content. 11/30/2007 2.0 Major Updated and revised the technical content. 1/25/2008 2.0.1 Editorial Changed language and formatting in the technical content. 3/14/2008 2.1 Minor Clarified the meaning of the technical content. 5/16/2008 2.1.1 Editorial Changed language and formatting in the technical content. 6/20/2008 2.1.2 Editorial Changed language and formatting in the technical content. 7/25/2008 2.1.3 Editorial Changed language and formatting
in the technical content. 8/29/2008 3.0 Major Updated and revised the technical content. 10/24/2008 3.0.1 Editorial Changed language and formatting in the technical content. 12/5/2008 3.0.2 Editorial Changed language and formatting in the technical content. 1/16/2009 3.0.3 Editorial Changed language and formatting in the technical content. 2/27/2009 3.0.4 Editorial Changed language and formatting in the technical content. 4/10/2009 3.0.5 Editorial Changed language and formatting in the technical content. 5/22/2009 4.0 Major Updated and revised the technical content. 7/2/2009 4.1 Minor Clarified the meaning of the technical content.
8/14/2009 4.1.1 Editorial Changed language and formatting in the technical content. 9/25/2009 4.2 Minor Clarified the meaning of the technical content. 11/6/2009 5.0 Major Updated and revised the technical content. 12/18/2009 5.0.1 Editorial Changed language and formatting in the technical content. 1/29/2010 5.1 Minor Clarified the meaning of the technical content. 3/12/2010 5.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 5.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 5.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 6.0 Major Updated and revised the
or formatting of the technical content. 2/13/2014 12.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 12.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 13.0 Significantly changed the technical content. 10/16/2015 13.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 13.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 13.0 None No changes to the meaning, language, or formatting of the technical content.
VT_I1 The of a VT_I1 type property MUST be a 1-byte signed integer. 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 Value VT_UI1 The value of a VT_UI1 type property MUST be a 1-byte unsigned integer. 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 Value VT_UI2 The value of a VT_UI2 type property MUST be a 2-byte unsigned integer. It MUST be formatted in little-endian byte order. 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 Value VT_UI4 The value of a VT_UI4 type property MUST be a 4-byte unsigned integer. It MUST be formatted in little-endian byte order. 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 Value VT_I8 The value of a VT_I8 type property MUST be an 8-byte signed integer. It MUST be formatted in byte order.
Index A Abstract data client ( 21, 28) 23 23 overview ( 21, 23) 23 10 C 10 17 40 Client abstract data model ( 21, 28) 29 29 33 message processing ( 23, 30) 33 sequencing ( 23, 30) 33 29 D 21 Data model - abstract client ( 21, 28) 23 23 overview ( 21, 23) 23 20 E 20 34 F 10 G 6 11 11 H Higher-layer triggered events 29 24 I 36 36 9 Initialization 29 24 6 L 23 Local events 33 28 M 34 Mapping 21 22 21 Message processing client ( 23, 30) server ( 23, 24) Messages 17 11 17 18 11 12 syntax 11 17 11 12 11 N 8
17 17 18 17 18 O Other local events 33 28 9 P 36 10 10 37 11 11 11 12 12 Q 22 21 R 8 9 8 9 S 20 Security 36 36 Sequencing rules client ( 23, 30) server ( 23, 24) Server 23 23 overview ( 21, 23) 23 24 24 28 message processing ( 23, 24) 28 sequencing rules ( 23, 24) 28 24 Shared data elements 29 23 10 Syntax 11 17 11 12 T Timer events 33 28 Timers 29 24 40 11 Triggered events - 29 24 V 10 10 15 13 16 16 13 13 13 14 15 16 14 14 14 16 15
Index A Abstract data model client ( 21, 28) 23 23 overview ( 21, 23) 23 10 C 10 17 40 Client abstract data model ( 21, 28) 29 29 33 message processing ( 23, 30) 33 sequencing rules ( 23, 30) 33 29 D 21 Data model - abstract client ( 21, 28) 23 23 overview ( 21, 23) 23 20 E 20 34 F 10 G 6 11 11 H triggered events 29 24 I 36 36 9 Initialization 29 24 6 L 23 Local events 33 28 M 34 Mapping 21 22 21 Message processing client ( 23, 30) server ( 23, 24) Messages 17 11 17 18 11 12 syntax 11 17 11 12 11 N 8 17 17 18 17 18 O Other local events 33 28 9 P 36 10 10 37 11 11 11
Index A Abstract data model 27 18 12 C 12 35 Client 27 28 28 28 28 28 27 13 D Data model - abstract 27 18 13 13 17 14 E 17 14 Events 28 27 28 27 29 29 29 F 12 32 G 6 I 32 31 31 9 Initialization 28 19 Interfaces - server 18 6 L Local events 28 27 M 15 15 Message processing 28 19 Messages 13 13 13 Methods 25 19 14 14 14 N 8 O 14 9 9 P
"MACHINE" else If rOpenQueueDescriptor.QueueReference.QueueType EQUALS Connector then "CONNECTOR". PROPID_MGMT_QUEUE_LOCATION If rOpenQueueDescriptor.QueueReference is of type OutgoingQueue then "REMOTE" else VT_LPWSTR PROPID_MGMT_QUEUE_XACT If EQUALS True then "YES" else "NO" VT_LPWSTR PROPID_MGMT_QUEUE_FOREIGN If QueueManager.DirectoryOffline is True If rOpenQueueDescriptor.QueueReference.QueueType is Private "NO" else "Unknown" else If QueueManager.ForeignSystem is True "YES" else "NO" VT_LPWSTR to the number of MessagePosition elements in the that are not in the Deleted state. VT_UI4 rOpenQueueDescriptor.QueueReference.TotalBytes. VT_UI4 If rOpenQueueDescriptor.QueueReference. JournalQueueReference EQUALS NULL else The number of elements in the rOpenQueueDescriptor.QueueReference. JournalQueueReference.MessagePositionList. VT_UI4 If rOpenQueueDescriptor.QueueReference.Journaling EQUALS True then rOpenQueueDescriptor.QueueReference. JournalQueueReference.TotalBytes.. VT_UI4 PROPID_MGMT_QUEUE_STATE If rOpenQueueDescriptor.QueueReference is not of type OutgoingQueue then "LOCAL CONNECTION" else If EQUALS Connected then VT_LPWSTR
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 B: Product Behavior Windows 10 to applicability list. Y Content update.
Index A Abstract data 37 17 10 11 C Canceling 46 46 46 11 57 Client 37 46 46 46 38 47 38 38 43 39 42 44 41 38 47 38 Closing 46 46 46 46 13 Cursor 46 43 44 17 D Data model - abstract 37 17 14 13 16 E 16 Events 47 37 47 36 Examples 48 49 48 F 12 51 G 6 I 51 50 50 50 8 Initialization 38 18 6 L Local events 47 37 M Message processing 38 18 Messages 13 overview ( 9, 13) 46 43 39 48 46
29 30 24 28 19 30 33 N 8 O 38 38 8 8 P 50 50 37 37 43 39 Peeking messages 46 43 39 11 11 53 Protocol Details 17 49 42 Purging ( 42, 49) Q 9 Queues 46 38 9 purging ( 42, 49) 17 R 48 44 41 48 46 44 41 8 8 8 10 27 27 26 26 25 25 22 22 29 29 30 30 24 24 28 28 19 19 30 30 33 33 14 14 16 S 16 50 50 50 Sequencing rules 38 18 Server 17 18 37 18 27 26 25 22 29 30 24 28 19 30 33 18 36 18 12 14 T Timer events 47 36 Timers 38 18 57
and formatting in the technical content. 7/25/2008 1.0.8 Editorial Changed language and formatting in the technical content. 8/29/2008 2.0 Major Updated and revised the technical content. 10/24/2008 3.0 Major Updated and revised the technical content. 12/5/2008 4.0 Major Updated and revised the technical content. 1/16/2009 4.1 Minor Clarified the meaning of the technical content. 2/27/2009 4.2 Minor Clarified the meaning of the technical content. 4/10/2009 4.2.1 Editorial Changed language and formatting in the technical content. 5/22/2009 4.2.2 Editorial Changed language and formatting in the technical content. 7/2/2009 5.0 Major Updated and revised
the technical content. 8/14/2009 6.0 Updated and revised the technical content. 9/25/2009 7.0 Major Updated and revised the technical content. 11/6/2009 8.0 Major Updated and revised the technical content. 12/18/2009 9.0 Major Updated and revised the technical content. 1/29/2010 10.0 Major Updated and revised the technical content. 3/12/2010 10.0.1 Editorial Changed language and formatting in the technical content. 4/23/2010 10.0.2 Editorial Changed language and formatting in the technical content. 6/4/2010 11.0 Major Updated and revised the technical content. 7/16/2010 11.0 None No changes to the meaning, language, or formatting
of the technical content. 8/27/2010 12.0 Major Updated and revised the technical content. 10/8/2010 13.0 Updated and revised the technical content. 11/19/2010 13.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 13.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 14.0 Major Updated and revised the technical content. 3/25/2011 15.0 Major Updated and revised the technical content. 5/6/2011 16.0 Major Updated and revised the technical content. 6/17/2011 16.1 Minor Clarified the meaning of the technical content. 9/23/2011 16.1 None No changes to the
meaning, language, or formatting of the technical content. 12/16/2011 17.0 Major Updated and revised the technical content. 3/30/2012 17.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 17.1 Minor Clarified the meaning of the technical content. 10/25/2012 18.0 Major Updated and revised the technical content. 1/31/2013 18.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 19.0 Major Updated and revised the technical content. 11/14/2013 19.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 37 17 10 11 C Canceling 46 46 46 11 56 Client 37 46 46 46 38 47 38 38 43 39 42 44 41 38 47 38 Closing 46 46 46 46 13 Cursor 46 43 44 17 D Data - abstract 37 17 14 13 16 E 16 Events 47 37 47 36 Examples 48 49 48 F 12 51 G 6 I 51 50 50 50 8 Initialization 38 18 6 L Local events 47 37 M Message processing 38 18 Messages 13 overview ( 9, 13) 46 43 39 48 46 44 41 13 Methods 46 46 46 38 39 43 42 41 44 27 26
29 16 Messages 14 14 14 Methods 73 74 74 71 67 70 66 67 71 71 44 35 33 34 46 62 30 47 30 49 35 51 61 36 52 68 72 70 70 N 9 O 66 10 11 10 10 10 10 11 P 80 80 71 67 12 12 84 71 Q 10 10 R 44 44 35 35 33 33 34 34 46 46 62 62 30 30 47 47 30 30 49 49 35 35 51 51 61 61 36 36 52 52 72 68 76 77 76 77 8 9 9 70 12 S 26 25 25 80
Index A Abstract data model 67 28 11 12 B 76 76 C 74 13 92 67 74 75 75 72 68 67 75 67 71 67 72 68 72 73 69 71 67 75 67 75 75 14 21 72 D Data model - abstract 67 28 14 14 24 27 E 27 68 Events 75 75 Examples 76 76 76 77 78 77 78 24 22 F 13 82 G 6 I 82 81 81 81 9 Initialization 67 30 6 L Local events 75 65 M Message processing 67 30 16 Messages 14 14 14 Methods 74 75 75 72 68 71 67 68 72 72 45 36 34
35 47 63 31 48 31 50 36 52 62 37 53 69 73 71 71 N 9 O 67 10 11 10 10 11 10 12 P 81 81 72 68 12 12 85 72 Q 11 10 R 45 45 36 36 34 34 35 35 47 47 63 63 31 31 48 48 31 31 50 50 36 36 52 52 62 62 37 37 53 53 73 69 77 78 77 78 9 9 9 71 12 S 27 25 26 81 81 81 Sequencing rules 67 30 Server 28 30 65 30 45 36 34 35 47 63 31 48 31 50 36 52 62 37 53 30 29 20 13 23
Index A Abstract data 14 14 14 14 19 19 19 19 9 C 9 27 Client 14 14 14 14 15 15 events 18 18 message processing 16 16 sequencing rules 16 16 18 15 D Data - abstract 14 14 14 14 19 19 19 19 13 E 13 21 F 9 G 6 H Higher-layer triggered events 15 19 I 23 23 8 Initialization 15 19 6 L events client 18 18 20 M Message processing client 16 16 server 20 20 Messages 10 10 10 11 10 N 8 O Other local events 20 8 P 23 9 9 24 R 7 8 8
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 Versioning, Capability Negotiation, and Extensibility Added content for Windows 10. Y Content update. Microsoft Implementations Added Windows 10 to applicability list. Y Content update.
A 36 19 13 23 C 34 52 36 20 22 22 22 13 5 Considerations 36 36 D Dependencies with other systems ( 22, 22) 22 Design intent 33 31 24 25 26 30 28 Discover media server urls - media player client 33 E 20 36 37 Extensibility 51 51 34 22 22 F 13 13 G 10 H 36 I 51 36 11 23 5 L Log statistics to servers - media player client 31 M 51 O Overview 19 13 5 P 23 51 Publish content to media server - encoder 25 Publish secure content to media server - encoder 26 R
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 Normative References : Updated reference to "WS Addressing" to [WSA]. N Content update. Relationship to Other Protocols : Updated reference to "WS Addressing" to [WSA]. N Content update. wsignin1.0 Request Message 69636 : Updated description of wreply and wtrealm. Y Content update. 2.2.3 wsignin1.0 Request Message Updated content for Windows 10 and Windows Server 2016 Technical Preview operating systems. Y Content update. High-Level Format of wresult Parameter 69635 : Updated reference to "WS Addressing" to [WSA]. N Content update. Subject Element 70824 : Updated description of the Subject element. Y Content update. Requestor IP/STS Security Updated content for Windows 10 Y Content update.
Realm Discovery and Windows Server 2016 Technical Preview operating systems. Message Transmission Updated content for Windows 10 and Windows Server 2016 Technical Preview operating systems. Y Content update. Message Validation 69636 : Updated description of wreply and wtrealm. Y Content update. Appendix A: Product Behavior Updated product behavior notes to include Windows Server 2016 Technical Preview operating system. Y Content update. 6 Appendix A: Product Behavior Updated product applicability list and product behavior notes to reflect the removal of the client SKU. Y Content update.