zilongwang/ReadingBank huggingface dataset:
{ "id": "PayloadErrorReply", "description": "Payload Error reply from server", [{ "type": "object", "properties": { "__type": { "enum": ["PayloadErrorReply:#Microsoft.Windows.RemoteAttestation.Core"] "required": true } } } },{ "$ref": "[MS-HGSA]#/ErrorReply" }] } PolicyEvaluationErrorReply PolicyEvaluationErrorReply structure defines the error due to failure in the policy. { "id": "PolicyEvaluationErrorReply", "description": "Policy Evaluation Error reply from server", "allOf": [{ "type": "object", "properties": { "__type": { "enum": ["PolicyEvaluationErrorReply:#Microsoft.Windows.RemoteAttestation.Core"] "required": true }, "Reasons": { "type": "array", "items": { "$ref": "[MS-HGSA]#/EvaluationLog" }, "required": true } } },{ "$ref": "[MS-HGSA]#/ErrorReply" }] } EvaluationLog: Policy evaluation log specified in section . ProtocolReplyBase ProtocolReplyBase structure represents the base type of attestation protocol replies from the server. { "id": "ProtocolReplyBase", "description": "Protocol reply from server", "type": "object", "properties": {} }
A Abstract data 26 22 Active attestation 28 24 7 C 7 32 Client 26 27 26 message processing 28 28 27 28 28 26 9 Common data types 9 8 E 8 28 F 7 G 25 5 H Higher-layer triggered events 27 23 I 30 30 6 Initialization 26 22 5 M Messages 8 N 5 O 6 P 30 6 6 31 R References 6 5 6 S Security 30 30 Server 22 23 22 message processing 24 25 23 23 26 26 22 7 T Timers 26 22 TPM-based attestation 27 23 32 8 Triggered events 27 23 V
Revision Summary Date Revision History Revision Class Comments 3/16/2017 1.0 New Released new document. 6/1/2017 2.0 Major Significantly changed the technical content. 9/15/2017 3.0 Major Significantly changed the technical content. 12/1/2017 3.0 None No changes to the meaning, language, or formatting of the technical content.
Protocol Details Server Details Abstract Data Model This section describes a conceptual of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document. Global SecurityGroup: List of domain-joined hosts that are known to be secure. AttestationHealthCertificate: The health certificate as an X509Certificate2. SupportedFunctionalLevels: An of integers representing the supported functional levels of the server. Per Attestation Request SecurityIdentifier: A unique value of variable length used to identify a client. isauthorized: A Boolean that determines whether the client is authorized or not. RtpmNewContext: A base64Binary string representing the Remote context, as defined in section , received from the server in response to initial TPM request. EvaluationLog: A log containing the result of policy evaluation after performing attestation as specified in section . AttestationOperationMode: The mode of operation of the Attestation Service as defined in section . FunctionalLevel: An integer representing the functional level of the server. Timers None. Initialization The server MUST implement the following: Isauthorized: MUST be set to zero. EvaluationLog: MUST be set to empty. AttestationHealthCertificate: MUST be set to NULL. RtpmNewContext: MUST be set to NULL. AttestationOperationMode: MUST be set to configured operation mode on the server. FunctionalLevel: MUST be set to the current highest functional level.
A Abstract data model 26 22 Active Directory–based attestation 28 24 7 C 7 32 Client 26 27 26 message processing 28 28 27 28 28 26 9 Common data 9 8 E 8 28 F 7 G 25 5 H Higher-layer triggered events 27 23 I 30 30 6 Initialization 26 22 5 M Messages 8 N 5 O 6 P 30 6 6 31 R References 6 5 6 S Security 30 30 Server 22 23 22 message processing 24 25 23 23 26 26 22 7 T Timers 26 22 TPM-based attestation 27 23 32 8 Triggered events 27 23 V 7 7
Revision Summary Date Revision History Revision Class Comments 3/16/2017 1.0 New Released new document. 6/1/2017 2.0 Significantly changed 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. 3/16/2018 4.0 Major Significantly changed the technical content.
"enum": ["OperationModeErrorReply:#Microsoft.Windows.RemoteAttestation.Core"] "required": true }, "ExpectedOperationMode": { "type": { "$ref": "[MS-HGSA]#/AttestationOperationMode" "required": true } } } },{ "$ref": "[MS-HGSA]#/ErrorReply" }] } ExpectedOperationMode: Expected mode of operation from the server; possible modes of operation are specified in section . PayloadErrorReply PayloadErrorReply structure defines the in which a request sent by the client is not supported by the server. { "id": "PayloadErrorReply", "description": "Payload Error reply from server", [{ "type": "object", "properties": { "__type": { "enum": ["PayloadErrorReply:#Microsoft.Windows.RemoteAttestation.Core"] "required": true } } } },{ "$ref": "[MS-HGSA]#/ErrorReply" }] } PolicyEvaluationErrorReply PolicyEvaluationErrorReply structure defines the error due to failure in the policy. { "id": "PolicyEvaluationErrorReply", "description": "Policy Evaluation reply from server", "allOf": [{ "type": "object", "properties": { "__type": { "enum": ["PolicyEvaluationErrorReply:#Microsoft.Windows.RemoteAttestation.Core"] "required": true }, "Reasons": { "type": "array", "items": { "$ref": "[MS-HGSA]#/EvaluationLog" }, "required": true } }
Index A Abstract data model 28 24 Active attestation 30 26 7 C 7 35 Client 28 29 28 message processing 30 30 29 31 30 28 10 Common data types 10 8 E 8 30 F 7 G 27 5 H Higher-layer triggered events 29 25 I 33 33 6 Initialization 28 24 5 M Messages 8 N 5 O 6 P 33 6 6 34 R References 6 5 6 S Security 33 33 Server 24 25 24 message processing 26 27 25 25 28 28 24 7 T Timers 28 24 TPM-based attestation 29 25 35 8 Triggered events 29 25 V
Revision Summary Date Revision History Revision Comments 10/24/2008 0.1 New Version 0.1 release 12/5/2008 0.2 Minor Clarified the meaning of the technical content. 1/16/2009 0.2.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.2.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.2.3 Editorial Changed language and formatting in the technical content. 5/22/2009 0.2.4 Editorial Changed language and formatting in the technical content. 7/2/2009 0.2.5 Editorial Changed language and formatting in the technical content. 8/14/2009 0.2.6 Editorial Changed language and formatting in the technical content. 9/25/2009 1.0 Major Updated and revised
the technical content. 11/6/2009 1.0.1 Editorial Changed language and formatting in the technical content. 12/18/2009 1.0.2 Editorial Changed language and formatting in the technical content. 1/29/2010 1.1 Minor Clarified the meaning of the technical content. 3/12/2010 1.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 1.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 1.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 1.1.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 1.1.3 None No changes to the
or formatting of the technical content. 6/17/2011 1.2 Minor Clarified the meaning of the technical content. 9/23/2011 1.2 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 2.0 Major Updated and revised the technical content. 3/30/2012 3.0 Major Updated and revised the technical content. 7/12/2012 3.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 3.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 3.0 None No changes to the meaning, language, or formatting of the
technical content. 8/8/2013 4.0 Updated and revised the technical content. 11/14/2013 4.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 10/16/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 5.0 None No changes to the meaning, language, or formatting of the
Revision Summary Date Revision History Revision Class Comments 10/24/2008 0.1 New Version 0.1 release 12/5/2008 0.2 Clarified the meaning of the technical content. 1/16/2009 0.2.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.2.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.2.3 Editorial Changed language and formatting in the technical content. 5/22/2009 0.2.4 Editorial Changed language and formatting in the technical content. 7/2/2009 0.2.5 Editorial Changed language and formatting in the technical content. 8/14/2009 0.2.6 Editorial Changed language and formatting in the technical content. 9/25/2009 1.0 Major Updated and revised
the technical content. 11/6/2009 1.0.1 Editorial Changed language and formatting in the technical content. 12/18/2009 1.0.2 Editorial Changed language and formatting in the technical content. 1/29/2010 1.1 Clarified the meaning of the technical content. 3/12/2010 1.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 1.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 1.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 1.1.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 1.1.3 None No changes to the
meaning, language, or formatting of the technical content. 10/8/2010 1.1.3 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 1.1.3 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 1.1.3 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 1.1.3 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 1.1.3 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 1.1.3 None No changes to the meaning, language,
technical content. 8/8/2013 4.0 Updated and revised the technical content. 11/14/2013 4.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Significantly changed the technical content. 10/16/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 5.0 None No changes to the meaning, language, or formatting of the
Prerequisites/Preconditions Peers have to be able to communicate with one of our in order to obtain information about other devices singed in with the same . In order to fully establish a channel with this protocol, two devices have to be signed-in with the same Microsoft Account. This is a restriction that can be later loosened within the protocol’s implementation. Applicability Statement The Connected Devices Platform Service Protocol provides a way for devices such as PCs and smartphones to discover and send messages between each It provides a transport-agnostic means of building connections among all of a user's devices, whether available through available transports. Versioning and Capability Negotiation This document is focused on the version of the protocol (V3)—the protocol version is contained in the header of the messages. Vendor-Extensible Fields None. Standards Assignments None
Package Name Length UINT16 Length of Package Name Package Name array[UINT8] Package Name of the app that hosts the app service (Chars) AppServiceName Length UINT16 Length of App Service Name App Service Name array[UINT8] Name of App Service (Chars) Data array[UINT8] List of parameters sent to App Service for execution App Services Result This returns the result of the App Services API call from the second device. 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 App Services Result Result URI Return Data (variable) ... ... Directory Service Schema Elements None.
Index A 8 C 8 51 9 D 23 E 23 F 8 G 5 I 49 49 7 5 M Messages 9 9 9 N 9 6 O 7 P 49 8 8 50 R 6 7 6 8 S 23 Security 49 49 8 T 51 9 V 8 8
Revision Summary Date Revision History Revision Class Comments 6/30/2015 1.0 New Released new document. 10/16/2015 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 1.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 1.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 2.0 Major Significantly changed the technical content. 9/12/2018 3.0 Major Significantly changed the technical content.
Messages Transport Messages are transported as specified in sections including, but not limited to, 3, 4, and 5. Message Syntax The syntax is as specified in sections including, but not limited to, 6 and 7. One additional setting value is defined in this section. The TLS_RENEG_PERMITTED Setting This document defines a new setting in HTTP/2, TLS_RENEG_PERMITTED, with code 0x10 and an initial value of 0x00. The thirty-two bits of the setting value are interpreted as follows: 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 Reserved MinorVersion S C The defined bits are: C: If set, client-initiated renegotiation is acceptable to the sender. S: If set, server-initiated renegotiation is acceptable to the sender. All other bits are undefined, and MUST be zero when sent and ignored upon receipt.
Index A Abstract data model 8 9 5 C 6 17 Client 8 8 8 9 9 8 9 9 8 D Data model - abstract 8 9 F 6 G 4 H Higher-layer triggered events 8 10 I 15 15 5 Initialization 8 9 4 M Message processing 9 10 Messages 7 7 N 4 O Other local events 9 10 5 P 15 5 5 16 R 4 5 4 5 S Security 15 15 Sequencing rules 9 10 Server 9 10 9 10 10 9 10 10 9 6 T 7 Timer events 9 10 Timers 8 9 17 7 Triggered events - 8 10 V
Revision Summary Date Revision History Revision Comments 11/14/2013 1.0 New Released new document. 2/13/2014 2.0 Major Updated and revised the technical content. 5/15/2014 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 3.0 Major Significantly changed the technical content. 10/16/2015 3.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/16/2017 4.0 Significantly changed the technical content.
Server Details Abstract Data This section describes a conceptual of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document. CodePage: The that the server is configured to use. See section 2.2.1 for more details. Timers None beyond what is specified in . Initialization None beyond what is specified in . Higher-Layer Triggered Events None beyond what is specified in . Message Processing Events and Sequencing Rules Receiving an HTTP Request When an Request message is received, the HTTP server MUST validate it and process it as specified in , except as follows. If the Request-URI contains a query component that does not conform to the standard syntax, but does conform to the extended syntax specified in section , the server MUST interpret it as being encoded in the server's CodePage (see section 3.1.5.1.1.3 for details). If the Request-URI contains a query component containing a percent (%) character, the server SHOULD interpret it as being escaped as specified in section 2.4.1. The server MAY<4> instead interpret it literally; that is, where the percent character represents itself rather than indicating the beginning of an escape sequence. The Host header MUST be validated the extended syntax specified in section . If the value contains characters that would not be valid in the standard syntax, the server SHOULD interpret it as follows: attempt to interpret it as and if it is not a valid UTF-8 sequence, then interpret it in as being encoded in the server's CodePage (see [MS-UCODEREF] section 3.1.5.1.1.3 for details). The server MAY<5> instead reverse the order of checks; that is, first attempt to interpret it as being encoded in the server's CodePage and if it is not a valid string in that CodePage, then interpret it as being encoded in UTF-8. Timer Events None beyond what is specified in . Other Local Events None beyond what is specified in .
Index A Abstract data model 9 10 7 C 7 15 Client 9 9 9 9 9 9 9 9 D Data model - abstract 9 10 E 11 F 7 G 4 H Higher-layer triggered events 9 10 8 I 12 12 6 Initialization 9 10 4 M Message processing 9 10 Messages 8 8 8 8 8 8 N 5 O Other local events 9 10 6 P 12 6 6 13 R 10 5 6 5 6 11 11 8 S Security 12 12 12 Sequencing rules 9 Server 10 10 10 10 10 10 10 7 T events 9 10
Revision Summary Date Revision History Revision Class Comments 11/14/2013 1.0 New Released new document. 2/13/2014 2.0 Major Updated and revised the technical content. 5/15/2014 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 3.0 Major Significantly changed the technical content. 10/16/2015 3.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/16/2017 4.0 Significantly changed the technical content. 6/1/2017 4.0 None No changes to the meaning, language, or formatting of the
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. This document specifies version-specific details in the Microsoft .NET Framework. For information which versions of .NET Framework are available in each released Windows product or as supplemental software, see section 4. Microsoft .NET Framework 2.0 Microsoft .NET Framework 3.5 Microsoft .NET Framework 4.0 Microsoft .NET Framework 4.5 Microsoft .NET Framework 4.6 Microsoft .NET Framework 4.7 Windows 2000 operating system Windows XP operating system Windows Server 2003 operating system Windows Vista operating system Windows Server 2008 operating system Windows 7 operating system Windows Server 2008 R2 operating system Windows 8 operating system Windows Server 2012 operating system Windows 8.1 operating system Windows Server 2012 R2 operating system Windows 10 operating system Windows Server 2016 operating system Windows Server operating system 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. <1> Section 2.2.2: Except in Windows 10, servers in applicable Windows Server releases that are configured to select certificates using server name indication (SNI) returned a status code of 400 to a
Index A Abstract data model 9 10 7 C 7 15 Client 9 9 9 9 9 9 9 9 D Data model - abstract 9 10 E 11 F 7 G 4 H Higher-layer triggered events 9 10 8 I 12 12 6 Initialization 9 10 4 M Message processing 9 10 Messages 8 8 8 8 8 8 N 5 O Other local events 9 10 6 P 12 6 6 13 R 10 5 6 5 6 11 11 8 S Security 12 12 12 Sequencing rules 9 Server 10 10 10 10 10 10 10 7 T events 9 10
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 3.0 Major Significantly changed the technical content. 12/1/2017 3.0 None No changes to the meaning, language, or formatting of the technical content.
EndpointType2Data ... HostEndpoints: A length-prefixed list of endpoint structures (see following) that are provided by each transport on the host device. Metadata: Transport defined data that is size prefixed for each transport endpoint type available on the device. The overall section is also prefixed with the size to indicate how many such endpoint mappings are present. as 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 Host data Length Host data ... Service data Length Service data ... Endpoint Type Host: Length-prefixed data that defines the name of the host. Service: Length-prefixed data that defines the name of the service on the host. EndpointType (2 bytes): An enumeration that defines the type of endpoint. See section for values. Upgrade Finalization This message transport the upgrade finalization 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 Metadata Length EndpointType1 EndpointType1Data Length EndpointType1Data ... EndpointType2 EndpointType2Data Length
ChannelID = 0 0x00, 0x00, 0x00, 0x00 0x00, 0x00, 0x00, 0x00 EndAdditionalHeaders = 0x00, 0x00 PayloadSize = 0x00, 0x00, 0x00, 0x03 ConnectionMode = Proximal 0x00, 0x01 MessageType = AuthDoneRequest Padding = 7 0x07 Padding = 7 0x07 Padding = 7 0x07 Padding = 7 0x07 Padding = 7 0x07 Padding = 7 0x07 Padding = 7 0x07 This new payload is then encrypted by using AES 128-bit CBC using the encryption key and the aforementioned initialization vector (an input of the algorithm). The changes are in bold. Encrypted 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 Signature = 0x30, 0x30 MessageLength = 58 bytes 0x00, 0x3A Version = 0x03 MessageType = Connect 0x02 MessageFlags = None 0x00, 0x00 SequenceNumber = 0 0x00, 0x00, 0x00, 0x00 RequestID = 0 0x00, 0x00, 0x00, 0x00 0x00, 0x00, 0x00, 0x00
EndAdditionalHeaders = 0x00, 0x00 ConnectionMode = Proximal 0x00, 0x01 MessageType = ConnectResponse 0x01 Status= Pending 0x01 HMACSize = 32 0x00, 0x20 Nonce = 0x18, 0x8A, 0xCB, 0xE0, 0x9F, 0x20, 0x3B, 0x71 MessageFragmentSize = 16384 0x00, 0x00, 0x40, 0x00 PublicKeyXLength = 32 0x00, 0x20 PublicKeyX = 0x66, 0xD5, 0x2E, 0x11, 0x99, 0xB2, 0xA4, 0x91 ... PublicKeyYLength = 32 0x00, 0x20 PublicKeyY = 0xB4, 0x13, 0xFA, 0xAA, 0x67, 0x1E, 0xE5, 0x92 ... Device Authentication Request MessageLength = 500 bytes. 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
Index A 33 8 Authentication 36 36 55 56 C 8 60 9 Common header 9 16 Connected Devices Platform service 36 33 Connection 16 42 16 8 46 48 D 33 49 51 32 Discovery 42 12 7 44 45 E 32 Encryption 37 36 Examples 37 44 F 8 G 5 H Header - common 9 16 42 I 58 58 7 36 5 M Message processing 42 42 42 43 Messages 9 16 12 9 session 26 27 9 N 9 7 O Object 34 33 35 Overview 33 8 7 36 33 44 7 7 P 58 8 8 59 33 44 R
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 Major Significantly changed the technical content.
Revision Summary Date Revision History Revision Class Comments 3/31/2010 0.1 Major Initial Availability 4/30/2010 0.2 Editorial Revised and edited the technical content 6/7/2010 0.3 Editorial Revised and edited the technical content 6/29/2010 0.4 Editorial Changed language and formatting in the technical content. 7/23/2010 0.4 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 1.0 Major Significantly changed the technical content. 11/15/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 1.0 None No changes to the
meaning, language, or formatting of the technical content. 6/10/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 2.0 Major Significantly changed the technical content. 4/11/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.0.1 Editorial Changed language and formatting in the technical content. 2/11/2013 2.0.1 None No changes to the meaning, language, or formatting of the technical content.
7/30/2013 2.1 Clarified the meaning of the technical content. 11/18/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 2.1 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 2.2 Minor Clarified the meaning of the technical content. 7/31/2014 2.3 Minor Clarified the meaning of the technical content. 10/30/2014 2.3 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 3.0 Major Significantly changed the technical content. 9/4/2015 3.0 None No changes to the meaning, language, or formatting of the
meaning, language, or formatting of the technical content. 6/10/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 2.0 Major Significantly changed the technical content. 4/11/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.0.1 Editorial Changed language and formatting in the technical content. 2/11/2013 2.0.1 None No changes to the meaning, language, or formatting of the technical content.
7/30/2013 2.1 Minor Clarified the meaning of the technical content. 11/18/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 2.1 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 2.2 Minor Clarified the meaning of the technical content. 7/31/2014 2.3 Minor Clarified the meaning of the technical content. 10/30/2014 2.3 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 3.0 Major Significantly changed the technical content. 9/4/2015 3.0 None No changes to the meaning, language, or formatting of the
technical content. 7/15/2016 3.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 3.0 None No changes to the meaning, language, or formatting of the technical content. 4/27/2018 4.0 Major Significantly changed the technical content. 7/24/2018 5.0 Major Significantly changed the technical content.
Index A 16 13 C 14 31 16 D 16 16 E 22 F 14 G 7 H 16 18 17 18 17 18 17 16 I 29 29 29 10 16 7 L 21 M 19 20 20 15 Messages 15 15 15 15 N 10 O 10 P 29 13 13 30 R 10 10 10 13 S Security 29 29 29 19 20 20 14 15 T 21 21 21 16 31 15 16 18 17 18 17 18 17 16 15 V 14 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 For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type Appendix A: Product Behavior Updated list of supported products. Y Content updated due to protocol revision.
Index A 19 15 C 15 38 19 D 19 19 E Events 29 29 29 29 30 F 16 G 6 H 19 22 21 21 20 20 21 20 20 I 18 35 35 35 35 35 35 10 19 6 L 29 M Message processing 28 27 27 Messages 18 17 17 18 17 17 N 9 O 10 P 35 14 14 36 R References 10 9 14 S Security 35 35 35 35 35 35 Sequencing rules 28 27 27 16 17 17 18 T events 29 29
or formatting of the technical content. 7/31/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 5.0 Major Significantly changed the technical content. 9/4/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/1/2016 6.0 Major Significantly changed the technical content. 8/23/2016 6.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 6.0 None No changes to the meaning, language,
Index A 19 15 C 15 39 19 D 19 19 E Events 29 29 29 30 31 F 16 G 6 H 19 22 21 21 20 20 21 20 20 I 18 36 36 36 36 36 36 10 19 6 L 30 M Message processing 28 27 27 Messages 18 17 17 18 17 17 N 9 O 10 P 36 14 14 37 R 9 10 9 14 S Security 36 36 36 36 36 36 Sequencing 28 27 27 16 17 17 18 T Timer events 29 29 29 30
Revision Summary Date Revision History Revision Comments 12/12/2008 1.0 New Initial version 2/13/2009 1.01 Revised and edited the technical content. 3/13/2009 1.02 Minor Revised and edited the technical content. 7/13/2009 1.03 Revised and edited the technical content 8/28/2009 1.04 Editorial Revised and edited the technical content 11/6/2009 1.05 Editorial Revised and edited the technical content 2/19/2010 1.06 Editorial Revised and edited the technical content 3/31/2010 1.07 Major Updated and revised the technical content 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 4.0.1 Editorial Changed language and formatting in the technical content. 2/11/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 4.1 Minor Clarified the meaning of the technical content. 11/18/2013 4.2 Minor Clarified the meaning of the technical content. 2/10/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 4.2 None No changes to the meaning, language,
or formatting of the technical content. 7/31/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 5.0 Major Significantly changed the technical content. 9/4/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/1/2016 6.0 Major Significantly changed the technical content. 8/23/2016 6.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 6.0 None No changes to the meaning, language,
or formatting of the technical content. 6/20/2017 7.0 Significantly changed the technical content. 9/15/2017 8.0 Major Significantly changed the technical content. 4/27/2018 9.0 Major Significantly changed the technical content.
Index A 20 16 C 16 40 20 D 20 20 E Events 30 30 30 31 32 F 17 G 7 H 20 23 22 22 21 21 22 21 21 I 19 37 37 37 37 37 37 11 20 7 L 31 M Message processing 29 28 28 Messages 19 18 18 19 18 18 N 10 O 11 P 37 15 15 38 R 10 11 10 15 S Security 37 37 37 37 37 37 Sequencing rules 29 28 28 17 18 18 19 T Timer events 30 30
Revision Summary Date Revision History Revision Class Comments 12/12/2008 1.0 New Initial version 2/13/2009 1.01 Minor Revised and edited the technical content. 3/13/2009 1.02 Revised and edited the technical content. 7/13/2009 1.03 Major Revised and edited the technical content 8/28/2009 1.04 Editorial Revised and edited the technical content 11/6/2009 1.05 Editorial Revised and edited the technical content 2/19/2010 1.06 Editorial Revised and edited the technical content 3/31/2010 1.07 Major Updated and revised the technical content 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 Major 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 4.0.1 Editorial Changed language and formatting in the technical content. 2/11/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 4.1 Minor Clarified the meaning of the technical content. 11/18/2013 4.2 Minor Clarified the meaning of the technical content. 2/10/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 4.2 None No changes to the meaning, language,
or formatting of the technical content. 6/20/2017 7.0 Major Significantly changed the technical content. 9/15/2017 8.0 Major Significantly changed the technical content. 4/27/2018 9.0 Significantly changed the technical content. 7/24/2018 10.0 Significantly changed the technical content. 8/28/2018 11.0 Major Significantly changed the technical content.
A 19 15 C 15 39 19 D 19 19 E Events 29 29 29 30 31 F 16 G 6 H 19 22 21 21 20 20 21 20 20 I 18 36 36 36 36 36 36 10 19 6 L 30 M Message processing 28 27 27 Messages 18 17 17 18 17 17 N 9 O 10 P 36 14 14 37 R 9 10 9 14 S Security 36 36 36 36 36 36 Sequencing rules 28 27 27 16 17 17 18 T Timer events 29 29
formatting in the technical content. 5/22/2009 1.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 1.2 Minor Clarified the meaning of the technical content. 8/14/2009 1.2.1 Editorial Changed language and formatting in the technical content. 9/25/2009 1.2.2 Editorial Changed language and formatting in the technical content. 11/6/2009 1.2.3 Editorial Changed language and formatting in the technical content. 12/18/2009 1.2.4 Editorial Changed language and formatting in the technical content. 1/29/2010 1.2.5 Editorial Changed language and formatting in the technical content. 3/12/2010 1.2.6 Editorial Changed language and
formatting in the technical content. 4/23/2010 1.3 Minor Clarified the meaning of the technical content. 6/4/2010 1.3.1 Editorial Changed language and formatting in the technical content. 7/16/2010 1.3.1 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 2.0 Major Updated and revised the technical content. 10/8/2010 2.0 None No changes to the meaning, language, or formatting of 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
Index A Abstract data model 18 19 10 Application example 21 22 C 10 27 Client 18 18 18 19 18 19 18 19 18 D Data model - abstract 18 19 E 13 Error report 11 17 11 17 Examples application fault 21 22 23 22 21 F 10 G 23 6 H Higher-layer triggered events 18 19 I 25 25 8 Initialization 18 19 6 K 22 L 16 Local events 19 20 M Message processing 18 19 Messages 13 error report 11 17 11 17 16 11 16 11 11 N 11 7 O Other local events 19 20 8 P 25 9 9 26 R 7 8
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 Major 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 4.0.1 Editorial Changed language and formatting in the technical content. 2/11/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 4.0.1 None No changes to the meaning,
Index A 17 14 C Candidates gathering phase 19 25 14 30 17 Connectivity checks 20 28 26 D 17 E 27 F 14 G 7 H 17 19 20 18 22 19 18 18 19 18 17 I ICE keep-alive 26 16 28 28 28 28 28 28 10 17 7 L 26 M Media flow 22 Message processing 22 22 Messages 16 16 16 16 N 10 O 10 P 28 14 14 29 R 9 10 10 13 S Security 28 28 28 28 28 28 Sequencing rules 22 22 15 22 16 T 25
Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial version. 4/25/2008 0.2 Minor Updated the technical content. 6/27/2008 1.0 Major Updated and revised the technical content. 8/15/2008 1.01 Minor Revised and edited the technical content. 12/12/2008 2.0 Major Updated and revised the technical content. 2/13/2009 2.01 Minor Revised and edited the technical content. 3/13/2009 2.02 Minor Revised and edited the technical content. 7/13/2009 2.03 Major Revised and edited the technical content 8/28/2009 2.04 Editorial Revised and edited the technical content 11/6/2009 2.05 Editorial Revised and edited the technical content 2/19/2010 2.06 Editorial Revised and edited the technical content 3/31/2010 2.07 Updated and revised the
technical content 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
Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial version. 4/25/2008 0.2 Updated the technical content. 6/27/2008 1.0 Major Updated and revised the technical content. 8/15/2008 1.01 Minor Revised and edited the technical content. 12/12/2008 2.0 Major Updated and revised the technical content. 2/13/2009 2.01 Minor Revised and edited the technical content. 3/13/2009 2.02 Minor Revised and edited the technical content. 7/13/2009 2.03 Major Revised and edited the technical content 8/28/2009 2.04 Editorial Revised and edited the technical content 11/6/2009 2.05 Editorial Revised and edited the technical content 2/19/2010 2.06 Editorial Revised and edited the technical content 3/31/2010 2.07 Major Updated and revised the
technical content 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 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 4.0.1 Editorial Changed language and formatting in the technical content. 2/11/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 4.0.1 None No changes to the meaning,
language, or formatting of the technical content. 11/18/2013 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 4.0.1 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 4.1 Minor Clarified the meaning of the technical content. 7/31/2014 4.1 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 4.1 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 5.0 Significantly changed the technical content. 9/4/2015 5.0 None No changes to the meaning,
language, or formatting of the technical content. 7/15/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 8/24/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 4/27/2018 6.0 Major Significantly changed the technical content. 7/24/2018 7.0 Major Significantly changed the technical content. 8/28/2018 8.0 Significantly changed the technical content.
Revision Summary Date Revision History Revision Class Comments 3/2/2007 1.0 New Version 1.0 release 4/3/2007 1.1 Minor Version 1.1 release 5/11/2007 1.2 Minor Version 1.2 release 6/1/2007 1.2.1 Editorial Changed language and formatting in the technical content. 7/3/2007 1.2.2 Editorial Changed language and formatting in the technical content. 8/10/2007 2.0 Major IDL was updated. 9/28/2007 2.0.1 Editorial Changed language and formatting in the technical content. 10/23/2007 3.0 Major Converted document to unified format and updated technical content. 1/25/2008 3.0.1 Editorial Changed language and formatting in the technical content. 3/14/2008 3.0.2 Editorial Changed language and formatting in the technical content. 6/20/2008 4.0 Major Updated and revised the technical content.
the technical content. 11/6/2009 6.1.1 Editorial Changed language and formatting in the technical content. 12/18/2009 6.1.2 Editorial Changed language and formatting in the technical content. 1/29/2010 7.0 Major Updated and revised the technical content. 3/12/2010 8.0 Major Updated and revised the technical content. 4/23/2010 9.0 Major Updated and revised the technical content. 6/4/2010 10.0 Major Updated and revised the technical content. 7/16/2010 11.0 Major Updated and revised the technical content. 8/27/2010 12.0 Major Updated and revised the technical content. 10/8/2010 12.1 Minor Clarified the meaning of the technical content. 11/19/2010 13.0 Major Updated and revised the technical content. 1/7/2011 13.0 None No changes to the meaning, language, or formatting of
the technical content. 2/11/2011 13.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 14.0 Major Updated and revised the technical content. 5/6/2011 14.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 14.1 Minor Clarified the meaning of the technical content. 9/23/2011 15.0 Major Updated and revised the technical content. 12/16/2011 16.0 Major Updated and revised the technical content. 3/30/2012 16.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 16.1 Minor Clarified the meaning of the technical content. 10/25/2012 16.1 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 16.1 None No changes to the
Index A Abstract data model 11 11 8 C 9 12 20 Client 11 11 11 11 11 11 11 11 11 11 10 D Data model - abstract 11 11 Data types 10 10 10 E Events local 11 14 11 14 timer 11 14 11 14 15 15 F 9 17 G 5 I icertpassage interface ( 11, 11) 17 16 16 8 Initialization 11 12 Interfaces - client 11 Interfaces - server 11 5 L events 11 14 M Message processing 11 12 Messages 10 10 10 10 10 N 7 O 8 8 P 16 8 8 18 Protocol Details 11 R 7 8 7 8 10 10 S Security
Coded Character Set (UCS) presentation of the written form of the languages of the world as well as additional symbols. ISO/IEC 8859-1:1998 ISO/IEC 8859-8:1999 ISO/IEC 8859-9:1999 ISO/IEC 8859-15:1999 ISO/IEC 8859-16:2001 Information technology -- 8-bit single-byte coded graphic character sets Parts 1, 8, 9, 15 and 16 Specifies the character-encoding scheme for characters such as alphabet no. 1" consisting of 191 characters from the Latin script. Standards in this table enable support of the Microsoft JScript Object Model. Standard Name Description Link ECMA-402 ECMAScript® Internationalization API Specification This Ecma standard defines the application programming interface for ECMAScript objects that support programs that need to adapt to the linguistic and cultural conventions used by different human languages and countries. ECMA-402 ECMAScript® Internationalization API Specification 2nd Edition This Ecma standard defines the application programming interface for ECMAScript objects that support programs that need to adapt to the linguistic and cultural conventions used by different human languages and countries. This is the 2nd edition of the specification. ECMA-262 ECMAScript® Language Specification 3rd Edition ECMAScript is a web page scripting language. This is the 3rd edition of the specification. ECMA-262 ECMAScript® Language Specification 5th Edition ECMAScript is a web page scripting language. This is the 5th edition of the specification. ECMA-262 ECMAScript® Language Specification 5.1 Edition ECMAScript is a web page scripting language. This is edition 5.1 of the specification. ECMA-262 ECMAScript® Language Specification 6th Edition ECMAScript is a web page scripting language. This is the 6th edition of the specification.
Revision Summary Date Revision History Revision Class Comments 2/24/2010 0.1 New Released new document. 3/17/2010 0.2 Minor Clarified the meaning of the technical content. 3/26/2010 1.0 Minor Clarified the meaning of the technical content. 5/26/2010 1.2 None Introduced no new technical or language changes. 6/29/2010 1.21 Editorial Changed language and formatting in the technical content. 9/8/2010 1.3 Major Significantly changed the technical content. 2/10/2011 2.0 Minor Clarified the meaning of the technical content. 12/7/2011 2.1 Minor Clarified the meaning of the technical content. 2/22/2012 3.0 Significantly changed the technical content. 7/25/2012 3.1 Minor Clarified the meaning of the technical content.