zilongwang/ReadingBank huggingface dataset:
10/24/2008 2.0.2 Editorial Changed language and formatting in the technical content. 12/5/2008 3.0 Major Updated and revised the technical content. 1/16/2009 3.0.1 Editorial Changed language and formatting in the technical content. 2/27/2009 3.0.2 Editorial Changed language and formatting in the technical content. 4/10/2009 3.0.3 Editorial Changed language and formatting in the technical content. 5/22/2009 3.0.4 Editorial Changed language and formatting in the technical content. 7/2/2009 4.0 Updated and revised the technical content. 8/14/2009 4.0.1 Editorial Changed language and formatting in the technical content. 9/25/2009 4.1 Minor Clarified the meaning of the technical content. 11/6/2009 4.1.1 Editorial Changed language and formatting in
formatting of the technical content. 7/12/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 6.0 Major Updated and revised the technical content. 11/14/2013 6.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 7.0 Significantly changed the technical content.
10/16/2015 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 7.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 8.0 Major Significantly changed the technical content.
A 10 10 7 C 7 22 8 D 10 10 8 8 E Events 16 16 Examples 17 17 F 7 19 G 5 I 19 18 18 6 10 10 5 K 15 15 L 16 16 M 10 10 Messages 8 8 8 Methods 15 13 12 14 11 N 6 O 7 P 18 7 7 20 Protocol Details 10 R 13 13 6 6 6 7 S Security 18 18 10 10 8 Server 10 10 15 16 10 13 10 12 14 11 16 10 7 12
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 Updated product behavior note for Windows 10. Y Product behavior note updated. 7 Appendix B: Product Behavior Updated product behavior note for Windows Server 2016 Technical Preview. Y Product behavior note updated.
Index A Abstract data model client ( 71, 85, 88, 113) 85 75 88 85 71 28 server ( 28, 75, 85, 89, 95, 97, 103) 36 36 90 90 95 95 91 91 93 93 92 92 13 94 94 91 91 B 48 48 76 114 114 76 C 13 135 52 52 19 20 Client abstract data model ( 71, 85, 88, 113) initialization ( 71, 85, 88, 113) 113 local events ( 75, 85, 89, 113) message processing ( 85, 88) 74 74 74 72 72 73 72 sequencing rules ( 85, 88) timer events ( 74, 85, 88, 113) timers ( 71, 85, 88, 113) 35 35 15 21 44 44 37 37 97 97 100 100 D Data model - abstract client ( 71, 85, 88, 113) 85 75 88 85 71 28 server ( 28, 75, 85, 89, 95, 97, 103) 15 15 42 42 99 99 100 100 51 51 39 39 40 40 38 38 E 20 18 50 50 101 101 77 114 114
28 29 71 29 29 71 29 120 12 Initialization client ( 71, 85, 88, 113) 85 75 88 86 71 29 server ( 29, 75, 86, 89, 95, 97, 103) InstanceName (Set) (Opnum 10) method ( 105, 113) 105 8 106 106 106 106 L Local events client ( 75, 85, 89, 113) 85 85 89 88 75 71 server ( 71, 85, 88, 95, 96, 103, 112) M Message processing client ( 85, 88) 85 75 88 86 72 29 server ( 29, 75, 86, 89, 95, 97, 103) Messages 15 15 15 21 23 24 Methods 36 90 95 91 93 92 94 91 48 76 52 35 44 37 97 100 42 99 100 51 39 40 38 50 101 77 46 79 111 107 86 53 55 56 56 102 57 80 108 109 InstanceName (Set) (Opnum 10) ( 105, 113) 106 106 34 R_EnumData (Opnum 12) ( 47, 74) R_GetAllData (Opnum 13) ( 58, 74) R_GetData (Opnum 10) ( 60, 74) 62 R_KeyExchangePhase1 (Opnum 26) ( 62, 72) R_KeyExchangePhase2 (Opnum 27) ( 64, 72) R_SetData (Opnum 9) ( 65, 73) 102 66 67 82 83 69 72 69 31 70 N 11
enrollment and property retrieval. ICertPassage Remote Protocol This protocol is a subset of the WCCE Protocol used for certificate enrollment over RPC by clients that do not support DCOM. WS-Trust Enrollment Extensions This protocol is based on SOAP. It provides Web certificate enrollment, renewal, and pending certificate retrieval. The profile enables X.509 certificate enrollment. Certificate Services Administration Protocols: Protocols in the following table enable remote administration of the certificate services. Protocol name Description Short name Certificate Services Remote Administration Protocol This protocol is responsible for CA administration, and it enables administrative to configure the state and policy of a CA on a server. Certificate Enrollment Policy (CEP) Protocols:
Protocols in the following table enable . Protocol name Description Short name X.509 Certificate Enrollment Policy Protocol This protocol is based on SOAP. It enables the client to retrieve enrollment policies. Certificate Templates Structure Certificate templates are stored in Active Directory and are used when the CA operates as an enterprise CA. They contain details about requesting and issuing certificates. Policy algorithms on the CA use certificate templates to determine how to respond to certificate requests. [MS-CRTD] defines attributes that are accessed by using the Lightweight Directory Access Protocol (LDAP). Environment The following sections identify the context in which the system exists. This includes the systems that use the interfaces provided by this system of protocols, other systems that depend on this system, and, as appropriate, how components of the system communicate.
A Actors 23 23 33 21 21 23 C 26 29 30 29 29 29 Certificate authority ( 6, 14) denied 51 50 enrollment 7 24 revocation 47 7 6 56 30 22 22 22 22 22 6 Considerations 33 30 CA 31 32 31 32 certificate 31 31 32 30 key 32 32 32 30 33 33 D Dependencies 22 22 Design intent 23 26 24 23 E Enrollment 38 16 37 35 42 34 22 30 Examples certificate denied 51 50 47 enrollment 38 37 35 42 34 34 44 Extensibility 30 29 29 55 29 22 F Functional requirements 21 14 16 12 21 system 13
13 12 G 7 H 30 I 55 30 CA 31 32 31 32 certificate 31 31 32 30 key 32 32 32 30 33 33 10 23 6 M 55 O Overview 21 14 6 16 21 21 12 system 13 13 6 P 23 44 55 6 R 10 Required information certificate 6 7 7 6 6 Requirements 30 30 12 23 system 21 14 13 16 13 21 S 30 CA 31 32 31 32 certificate 31 31 32 30 key 32 32 32 30 33 33 21 summary 23 System dependencies 22 22 22 30 overview
A Abstract data model 21 16 13 C 13 31 Client 21 21 21 21 21 21 21 15 D Data model - abstract 21 16 15 15 23 22 23 23 E Events 21 21 21 20 22 22 23 22 F 14 29 G 20 17 17 6 I 29 16 22 16 28 28 9 Initialization 21 16 Interfaces - server 16 6 12 18 12 19 L Local events 21 21 M Message processing 21 16 Messages 15 15 15 Methods 16 18 19 N 8 O
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.1 Minor Clarified the meaning of the technical content. 11/30/2007 2.0 Major Clarified the state requirements of .NET object versioning. 1/25/2008 2.0.1 Editorial Changed language and formatting in the technical content. 3/14/2008 3.0 Major Updated and revised the technical content. 5/16/2008 4.0 Major Updated and revised the technical content. 6/20/2008 5.0 Major Updated and revised the technical content. 7/25/2008 6.0 Major Updated and revised the technical content. 8/29/2008 6.0.1 Editorial Fix capitalization issues 10/24/2008 7.0 Major Updated and revised the technical content.
A Abstract data model 20 15 12 C 12 30 Client 20 20 20 20 20 20 20 14 D Data model - abstract 20 15 14 14 22 21 22 22 E Events 20 20 20 19 21 21 22 21 F 13 28 G 19 16 16 6 I 28 15 21 15 27 27 8 Initialization 20 15 Interfaces - server 15 6 12 17 12 18 L Local events 20 20 M Message processing 20 15 Messages 14 14 14 Methods 15 17 18 N 8 O 21 8 8 P 27 12 12 29 Protocol Details 15 R 8 8 8 12 17 18
certificate requests. defines attributes that are accessed by using the Lightweight Directory Access Protocol (LDAP). X.509 Certificate Enrollment Policy Protocol This protocol is based on SOAP. It enables clients to retrieve enrollment policies. WS-Trust Enrollment Extensions This protocol is on SOAP. It provides Web services-based certificate enrollment, renewal and pending certificate retrieval. The WS-Trust profile enables X.509 certificate enrollment. The Certificate Services protocols are grouped according to their primary purpose. Certificate enrollment protocols: Protocols in the following table enable certificate enrollment. Protocol name Description Short name Windows Client Certificate Enrollment Protocol This protocol is based on DCOM. It is responsible for certificate enrollment, and it enables clients to request various services from a CA,
Certificate Enrollment Policy (CEP) Protocols: Protocols in the following table enable certificate enrollment policy. Protocol name Description Short name X.509 Certificate Enrollment Policy Protocol This protocol is based on SOAP. It enables the client to retrieve enrollment policies. Certificate Templates Structure Certificate templates are stored in Active Directory and are used when the CA operates as an enterprise CA. They contain details about requesting and issuing certificates. Policy algorithms on the CA use certificate templates to determine how to respond to certificate requests. [MS-CRTD] defines attributes that are accessed by using the Lightweight Directory Access Protocol (LDAP).
Index A Actors 24 24 34 22 22 24 C 27 30 31 30 30 30 Certificate authority ( 6, 15) denied 52 51 enrollment 7 25 revocation 48 7 6 57 31 23 23 23 23 23 6 Considerations 34 31 CA 32 33 32 33 certificate 32 32 33 31 key 33 33 33 31 34 34 D Dependencies 23 23 Design intent 24 27 25 24 E Enrollment 39 17 38 36 43 35 23 31 Examples certificate denied 52 51 48 enrollment 39 38 36 43 35 35 45 Extensibility 31 30 30 56 30 23 F Functional requirements 22 15 17 13 22 system 14 14 13 G 7 H 31
I 56 31 CA 32 33 32 33 certificate 32 32 33 31 key 33 33 33 31 34 34 11 24 6 M 56 O Overview 22 15 6 17 22 22 13 system 14 14 6 P 24 45 56 6 R 11 Required information certificate 6 7 7 6 6 Requirements 31 31 13 24 system 22 15 14 17 14 22 S 31 CA 32 33 32 33 certificate 32 32 33 31 key 33 33 33 31 34 34 22 summary 24 System dependencies 23 23 23 31 overview certificate 6 7 7 6 6 6 6 22 requirements 22 15 14 17 13 14 22 use cases 24 27 25 23 23 23
9/23/2011 5.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 6.0 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 7.0 Major Updated and revised the technical content. 10/25/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Major Updated and revised the technical content. 11/14/2013 8.0 None No changes to the meaning, language,
or formatting of the technical content. 2/13/2014 8.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 8.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 9.0 Major Significantly changed the technical content. 10/16/2015 9.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 9.0 None No changes to the meaning, language, or formatting of the technical content.
18 7 P 20 25 8 8 26 Protocol Details 12 R 6 7 6 7 S Security 25 25 Sequencing client 15 15 16 15 15 server 17 17 18 17 Server 16 17 17 17 17 17 17 17 local events 19 19 19 message processing 17 17 18 17 18 sequencing rules 17 17 18 17 18 17 23 9 11 T Timer events 16 18 Timers 14 17 27 10 Triggered events client 15 15 15 server 17 17 17 Triggered events - 15 17 V 9 9
Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces. Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire. The changes made to this document are listed in the following table. For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type Appendix B: Product Behavior Updated the product behavior notes to include Windows 10. Y Product behavior note updated. 7 Appendix B: Product Behavior Updated the product behavior notes to include the Windows Server 2016 Technical Preview operating system. Y Product behavior note updated.
A Abstract data model 30 30 9 C 9 58 10 10 D Data model - abstract 30 30 10 10 E Events 44 44 45 45 F 9 27 47 G 6 H 30 I 47 28 29 28 46 46 10 10 10 10 10 10 10 10 21 20 11 17 15 15 17 16 18 16 16 10 14 10 10 10 18 19 30 8 Initialization 30 30 Interfaces - server 30 6 L Local events 44 44 27 28 29 28 21 20 11 17 15 15 17 16 18 16
16 14 18 19 24 M Message processing 30 30 Messages 10 10 10 Methods 42 41 43 43 38 38 34 36 39 34 33 37 35 36 40 39 N 8 O 8 P 46 9 9 54 Protocol Details 30 R 42 42 41 41 43 43 43 43 38 38 38 38 34 34 36 36 39 39 34 34 33 33 37 37 35 35 36 36 40 40 39 39 8 8 8 9 S Security 46 46 Sequencing rules 30 30 Server 30 30 30 30 44 30 30 42 41 43 43 38 38 34 36 39 34 33 37 35
Index A Abstract data 9 10 6 C 6 20 Client 9 9 9 message processing 9 receiving KDC_PROXY_MESSAGE ( 10, 10) 10 9 sequencing rules 9 receiving KDC_PROXY_MESSAGE ( 10, 10) 10 9 D Data model - abstract 9 10 E Examples 13 15 F 6 G 4 H Higher-layer triggered events 9 11 I 18 18 5 Initialization 9 11 4 K 8 M Message processing client 9 receiving KDC_PROXY_MESSAGE ( 10, 10) server 11 11 Messages 8 8 8 8 8 N 8 5 O 13 15 local events 10 12 6 P 18 6 6 19 R 5 5 5 6 S Security 18 18 Sequencing rules client 9 receiving KDC_PROXY_MESSAGE ( 10, 10) server 11 11 Server 10
Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 1.1 Minor Clarified the meaning of the technical content. 10/25/2012 1.1 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 1.2 Minor Clarified the meaning of the technical content. 8/8/2013 2.0 Major Significantly changed the technical content. 11/14/2013 2.1 Minor Clarified the meaning of the technical content. 2/13/2014 3.0 Major Significantly changed the technical content. 5/15/2014 3.1 Minor Clarified the meaning of the technical content.
The Kerberos client processes the KRB_AS_REP and calls ProxyMessage with a KRB_TGS_REQ. The client sends a KDC_PROXY_MESSAGE containing the KRB_TGS_REQ to the KKDCP server. The KKDCP server finds the KDC and sends the KRB_TGS_REQ to the KDC. The KDC returns a KRB_TGS_REP to the KKDCP server. The KKDCP server sends a KDC_PROXY_MESSAGE containing the KRB_TGS_REP to the KKDCP client. The KKDCP client returns the KRB_TGS_REP and SUCCESS to the Kerberos client. The Kerberos client processes the KRB_TGS_REP and sends a KRB_AP_REQ to the Kerberos application server. The Kerberos application server processes the KRB_AP_REQ and sends a KRB_AP_REP to the Kerberos client.
Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 1.1 Minor Clarified the meaning of the technical content. 10/25/2012 1.1 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 1.2 Minor Clarified the meaning of the technical content. 8/8/2013 2.0 Significantly changed the technical content. 11/14/2013 2.1 Minor Clarified the meaning of the technical content. 2/13/2014 3.0 Major Significantly changed the technical content. 5/15/2014 3.1 Minor Clarified the meaning of the technical content.
Security Security Considerations for Implementers Because is typically used in the Internet, messages are only protected when is used, and the KKDCP server’s certificate is valid. When using HTTP, the KKDCP client is sending clear text messages, which are vulnerable to attacks discussed in Kerberos V5 ( section 10), unless FAST is used. When the server relays messages from Internet KKDCP clients to the , it opens unauthenticated access to the KDC from the Internet, unless client authentication is required. KKDCP servers can also provide some level of protection by only relaying valid Kerberos messages, and by throttling messages. KKDCP servers open KDCs to the Internet, exposing them to denial-of-service attacks (using Kerberos messages) that were previously only possible via other authentication protocols, such as NTLM. Index of Security Parameters None.
Index A Abstract data 9 10 6 C 6 20 Client 9 9 9 message processing 9 receiving KDC_PROXY_MESSAGE ( 10, 10) 10 9 sequencing rules 9 receiving KDC_PROXY_MESSAGE ( 10, 10) 10 9 D Data model - abstract 9 10 E Examples 13 15 F 6 G 4 H Higher-layer triggered events 9 11 I 18 18 5 Initialization 9 11 4 K 8 M Message processing client 9 receiving KDC_PROXY_MESSAGE ( 10, 10) server 11 11 Messages 8 8 8 8 8 N 8 5 O 13 15 Other local events 10 12 6 P 18 6 6 19 R 5 5 5 6 S Security 18 18 Sequencing rules client 9 receiving KDC_PROXY_MESSAGE ( 10, 10) server 11 11 Server 10
Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 1.1 Minor Clarified the meaning of the technical content. 10/25/2012 1.1 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 1.2 Minor Clarified the meaning of the technical content. 8/8/2013 2.0 Major Significantly changed the technical content. 11/14/2013 2.1 Minor Clarified the meaning of the technical content. 2/13/2014 3.0 Significantly changed the technical content. 5/15/2014 3.1 Minor Clarified the meaning of the technical content.
6/30/2015 4.0 Significantly changed the technical content. 10/16/2015 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 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.
Index A Abstract data model 9 10 6 C 6 20 Client 9 9 9 message processing 9 receiving KDC_PROXY_MESSAGE ( 10, 10) 10 9 sequencing rules 9 receiving KDC_PROXY_MESSAGE ( 10, 10) 10 9 D Data - abstract 9 10 E Examples 13 15 F 6 G 4 H Higher-layer triggered events 9 11 I 18 18 5 Initialization 9 11 4 K 8 M Message processing client 9 receiving KDC_PROXY_MESSAGE ( 10, 10) server 11 11 Messages 8 8 8 8 8 N 8 5 O 13 15 Other local events 10 12 6 P 18 6 6 19 R 5 5 5 6 S Security 18 18 Sequencing rules client 9 receiving KDC_PROXY_MESSAGE ( 10, 10) server 11 11
Revision Summary Date Revision History Revision Comments 6/17/2011 1.0 New Released new document. 9/23/2011 2.0 Major Updated and revised the technical content. 12/16/2011 2.0 None No changes to the meaning, language, or formatting of 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 Major 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. 9/26/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
Enrollment Extensions This protocol is on SOAP. It provides Web services-based certificate enrollment, renewal and pending certificate retrieval. The WS-Trust profile enables X.509 certificate enrollment. The Certificate Services protocols are grouped according to their primary purpose. Certificate enrollment protocols: Protocols in the following table enable certificate enrollment. Protocol name Description Short name Windows Client Certificate Enrollment Protocol This protocol is on DCOM. It is responsible for certificate enrollment, and it enables clients to request various services from a CA, such as certificate enrollment and property retrieval. ICertPassage Remote Protocol This protocol is a subset of the WCCE Protocol used for certificate enrollment over RPC by clients that do not
30 I 55 30 CA 31 32 30 31 certificate 31 31 31 30 key 32 32 32 30 33 32 11 23 5 M 55 O Overview 21 14 5 16 21 21 12 system 13 13 5 P 23 44 55 5 R 11 Required information certificate 5 6 6 5 5 Requirements 30 30 12 23 system 21 14 13 16 13 21 S 30 CA 31 32 30 31 certificate 31 31 31 30 key 32 32 32 30 33 32 21 summary 23 System dependencies 22 22 22 30 overview certificate 5 6 6 5 5 5 5 21 requirements 21 14 13 16 12 13 21 use cases 23 26 24 22
Index A 8 C 8 22 D 12 E Examples 18 F 8 20 G 5 I 19 19 7 5 J 20 K Key provisioning server 14 14 14 14 17 16 14 M Messages 9 N 6 O 7 P 19 7 7 21 Protocol examples 18 R References 7 6 7 S Security 19 19 8 T 22 9 12 V 8 8
Index A 15 12 api-version ( 11, 12) 9 11 C 9 24 10 12 D 15 13 13 E 13 12 Examples 20 20 F 9 22 G 5 H 15 10 12 11 11 10 11 11 I 21 21 8 15 5 J 22 K Key provisioning client 18 19 19 19 19 19 19 Key provisioning server 15 15 15 15 18 18 15 M Message processing 15 15 15 Messages 12 10 10 12 14 N 7 O 18 8 P 21 8 8 23 Protocol examples 20 8 20 R References 8 7 8 11 11
Revision Summary Date Revision History Revision Class Comments 7/14/2016 1.0 New Released new document. 6/1/2017 2.0 Major Significantly changed the technical content. 6/13/2017 3.0 Major Significantly changed the technical content. 9/15/2017 4.0 Major Significantly changed the technical content. 12/1/2017 4.0 None No changes to the meaning, language, or formatting of the technical content.
} } } code: A server-generated string representing a machine readable error. message: A string explaining the error. response: The client action to be taken when this error is received. This value MUST be set to "ERROR_FAIL". target: A string representing the resource being acted upon. clientrequestid: A GUID in standard string representation (see section 3 for the format). time: The -formatted time that is assigned by the key provisioning server. trace: MUST be "null". context: MUST be "null". Directory Service Schema Elements This protocol use of the Directory Service schema classes and attributes that are listed in the following table. For the syntax of <Class> or <Class><Attribute> pairs, refer to , , and . Class Attribute User ms-DS-Key-Credential-Link, User-Principal-Name ms-DS-Device ms-DS-Device-ID ms-DS-Device-Registration-Service-Container ms-DS-Device-Registration-Service ms-DS-Issuer-Certificates, ms-DS-Issuer-Certificates The ms-DS-Issuer-Certificates attribute is a multivalued OCTET_STRING attribute (see section 3.1.1.2.2.2, the String(Octet) syntax). Each value of the attribute is stored as a binary blob containing the following formatted data: [time]:[binary value of an X.509 certificate] where [time] is the timestamp formatted as an integer representing the number of 100-nanosecond intervals that have elapsed since 12:00:00 midnight, January 1, 0001, , and [binary value of an X.509 certificate] is the contents of an X.509 certificate stored as an encrypted binary blob. ms-DS-Issuer-Public-Certificates The ms-DS-Issuer-Public-Certificates attribute is a multivalued OCTET_STRING attribute (see section 3.1.1.2.2.2, the syntax). Each value of the attribute is stored as a binary blob containing an X.509 certificate .
Index A 15 12 api-version ( 11, 12) 9 11 C 9 24 10 12 D 15 13 13 E 13 12 Examples 20 20 F 9 22 G 5 H 15 10 12 11 11 10 11 11 I 21 21 8 15 5 J 22 K Key provisioning client 18 19 19 19 19 19 19 Key provisioning server 15 15 15 15 18 18 15 M Message processing 15 15 15 Messages 12 10 10 12 14 N 7 O 18 8 P 21 8 8 23 Protocol examples 20 8 20 R References 8 7 8 11 11 S
Index A Abstract data model 25 21 6 C 6 35 Client 25 26 26 26 26 27 26 27 26 8 D Data model – abstract 25 21 E 28 F 6 30 G 5 H Higher-layer triggered events 26 22 7 I 29 29 6 Initialization 26 21 5 L events 27 25 M Message processing 26 27 26 22 Messages 8 7 15 7 N 5 O 6 P 29 6 6 34 R References 6 5 6 S Security 29 29 Sequencing rules 26 22 Server 21 22 21 22 25 22 25 21 15 6 T Timer events
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.
A Abstract data model 26 22 6 C 6 36 Client 26 27 27 27 27 28 27 28 27 8 D Data model – abstract 26 22 E 29 F 6 31 G 5 H Higher-layer triggered events 27 23 7 I 30 30 6 Initialization 27 22 5 L Local events 28 26 M Message processing 27 28 27 23 Messages 8 7 16 7 N 5 O 6 P 30 6 6 35 R References 6 5 6 S Security 30 30 Sequencing 27 23 Server 22 23 22 23 26 23 26 22 16 6 T
Messages Transport The Key Protection Service Protocol uses or secure as transport, as specified in and . Common Data Types HTTP Methods This protocol defines the following common in addition to the existing set of standard HTTP methods. Method Section Description RollTransportKey Extracts the TransportKey from the IngressProtector, generates a new transport key, creates the EgressProtector and returns both transport keys to the caller. GetMetaData Returns the metadata content containing the guardian information to the client. RollTransportKey The RollTransportKey method validates that the IngressProtector defined in section is performs Key Protection Service (KPS) checks by using an encryption algorithm in an implementation-specific manner, and generates the EgressProtector. This method is invoked from the following URI: http://<server>/keyprotection/service/{version}/rolltransportkey GetMetaData The GetMetaData method provides the list of KPS-supported certificates, are used in validating that the KeyProtector was properly signed by KPS or to create a new protector and encrypt the transport keys. This method is invoked from the following URI with HTTP GET request: http://<server>/keyprotection/service/metadata/2014-07/metadata.xml
A Abstract data model 26 22 6 C 6 36 Client 26 27 27 27 27 28 27 28 27 8 D Data model – abstract 26 22 E 29 F 6 31 G 5 H triggered events 27 23 7 I 30 30 6 Initialization 27 22 5 L Local events 28 26 M Message processing 27 28 27 23 Messages 8 7 16 7 N 5 O 6 P 30 6 6 35 R References 6 5 6 S Security 30 30 Sequencing rules 27 23 Server 22 23 22 23 26 23 26 22 16 6 T events
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. 3/16/2018 4.0 Major Significantly changed the technical content. 9/12/2018 5.0 Significantly changed the technical content.
Index A Abstract data model 29 24 6 C 6 38 Client 29 29 29 30 30 30 30 30 29 8 D Data model – abstract 29 24 E 31 F 6 33 G 5 H Higher-layer triggered events 29 25 7 I 32 32 6 Initialization 29 24 5 L events 30 29 M Message processing 30 30 30 25 Messages 8 7 16 7 N 6 O 6 P 32 6 6 37 R References 6 6 6 S Security 32 32 Sequencing rules 30 25 Server 24 25 24 25 29 25 29 24 16 6 T
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. 9/26/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
Index A Actors 25 25 35 23 23 25 C 28 31 31 31 31 31 Certificate authority ( 5, 16) denied 55 54 enrollment 6 26 revocation 51 6 5 60 32 24 24 24 24 24 5 Considerations 35 32 CA 33 34 32 33 certificate 33 33 33 32 key 34 34 34 32 35 34 D Dependencies 24 24 Design intent 25 28 26 25 E Enrollment 42 18 41 39 46 36 24 32 Examples certificate denied 55 54 51 enrollment 42 41 39 46 36 36 48 Extensibility 31 31 31 59 31 24 F Functional requirements 23 16 18 14 23 system 16 15 14 G 8 H
32 I 59 32 CA 33 34 32 33 certificate 33 33 33 32 key 34 34 34 32 35 34 12 25 5 M 59 O Overview 23 16 5 18 23 23 14 system 16 15 5 P 25 48 59 5 R 12 Required information certificate 5 6 6 5 5 Requirements 32 32 14 25 system 23 16 16 18 15 23 S 32 CA 33 34 32 33 certificate 33 33 33 32 key 34 34 34 32 35 34 23 summary 25 System dependencies 24 24 24 32 overview certificate 5 6 6 5 5 5 5 23 requirements 23 16 16 18 14 15 23 use cases 25 28 26 24
Revision Summary Date Revision History Revision Comments 10/24/2008 0.1 New Version 0.1 release 12/5/2008 0.1.1 Editorial Editorial Update. 1/16/2009 1.0 Major Updated and revised the technical content. 2/27/2009 1.1 Clarified the meaning of the technical content. 4/10/2009 1.2 Minor Clarified the meaning of the technical content. 5/22/2009 1.3 Minor Clarified the meaning of the technical content. 7/2/2009 1.4 Minor Clarified the meaning of the technical content. 8/14/2009 1.4.1 Editorial Changed language and formatting in the technical content. 9/25/2009 1.5 Clarified the meaning of the technical content. 11/6/2009 2.0 Major Updated and revised the technical content. 12/18/2009 2.0.1 Editorial Changed language and
formatting of the technical content. 1/7/2011 4.1 Minor Clarified the meaning of the technical content. 2/11/2011 4.2 Minor Clarified the meaning of the technical content. 3/25/2011 4.2 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 4.2 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 4.3 Minor Clarified the meaning of the technical content. 9/23/2011 4.3 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 5.0 Major Updated and revised the technical content. 3/30/2012 5.0 None No changes to the meaning,
language, or formatting of the technical content. 7/12/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 6.0 Major Updated and revised the technical content. 11/14/2013 6.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 6.0 None No changes to the meaning, language, or formatting of the technical content.
5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 7.0 Significantly changed the technical content. 10/16/2015 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 7.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 8.0 Major Significantly changed the technical content.
Index A Abstract data model 14 14 11 15 15 8 C 8 29 Client 14 14 14 15 14 14 14 14 14 14 15 15 14 14 14 14 14 14 15 15 14 D Data model - abstract 14 14 11 15 15 E 17 F 8 G 6 H Higher-layer triggered events 14 14 11 15 15 I 24 24 7 Initialization 14 14 11 15 15 6 L 9 9 10 10 9 LAC/client 14 14 14 15 message processing 14 14 14 14 14 15 sequencing rules 14 14 14 14 14 15 15 14 LAC/LNS 11 11 11 14 message processing 13 12 11 13 11 13 13 13
Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. Release 7 Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. Release 8 Windows 8, Windows Server 2012, Windows 8.1, and Windows Server 2012 R2. Release 8.1 Windows 8.1 and Windows Server 2012 R2. Release 9 Windows 10 and Windows Server 2016 Technical Preview Language Location (or type) Language ID Language tag Supported version Afar 0x1000 aa Release 9 Afar Djibouti 0x1000 aa-DJ Release 9 Afar Eritrea 0x1000 aa-ER Release 9 Afar Ethiopia 0x1000 aa-ET Release 9
French Haiti 0x3c0c fr-HT Release 8.1 French Luxembourg 0x140c fr-LU Release A French Madagascar 0x1000 fr-MG Release 9 French Mali 0x340c fr-ML Release 8.1 French Martinique 0x1000 fr-MQ Release 9 French Mauritania 0x1000 fr-MR Release 9 French Mauritius 0x1000 fr-MU Release 9 French Mayotte 0x1000 fr-YT Release 9 French Morocco 0x380c fr-MA Release 8.1 French New Caledonia 0x1000 fr-NC Release 9 French Niger 0x1000 fr-NE Release 9 French Principality of Monaco 0x180c fr-MC Release A French Reunion 0x200c fr-RE Release 8.1 French Rwanda 0x1000 fr-RW Release 9 French Saint Barthélemy 0x1000 fr-BL Release 9 French Martin 0x1000 fr-MF Release 9 French Saint Pierre and Miquelon 0x1000 fr-PM Release 9 French Senegal 0x280c fr-SN Release 8.1 French Seychelles 0x1000 fr-SC Release 9 French Switzerland 0x100c fr-CH Release A French 0x1000 fr-SY Release 9 French Togo 0x1000 fr-TG Release 9 French Tunisia 0x1000 fr-TN Release 9 French Vanuatu 0x1000 fr-VU Release 9 French Wallis and Futuna 0x1000 fr-WF Release 9 Frisian 0x0062 fy Release 7
Mozambique 0x1000 mgh-MZ Release 9 Makonde 0x1000 kde Release 9 Makonde Tanzania 0x1000 kde-TZ Release 9 Malagasy 0x1000 mg Release 8.1 Malagasy Madagascar 0x1000 mg-MG Release 8.1 Malay 0x003e ms Release 7 Brunei Darussalam 0x083e ms-BN Release C Malay Malaysia 0x043e ms-MY Release C Malayalam 0x004c ml Release 7 Malayalam India 0x044c ml-IN Release E1 Maltese 0x003a mt Release 7 Maltese Malta 0x043a mt-MT Release E1 Manx 0x1000 gv Release 9 Manx Isle of Man 0x1000 gv-IM Release 9 Maori 0x0081 mi Release 7 New Zealand 0x0481 mi-NZ Release E1 Mapudungun 0x007a arn Release 7 Mapudungun Chile 0x047a arn-CL Release E2 Marathi 0x004e mr Release 7 Marathi India 0x044e mr-IN Release C Masai 0x1000 mas Release 9 Masai Kenya 0x1000 mas-KE Release 9 Masai Tanzania 0x1000 mas-TZ Release 9 Meru 0x1000 mer Release 9 Meru Kenya 0x1000 mer-KE Release 9 Meta' 0x1000 mgo Release 9 Meta' Cameroon 0x1000 mgo-CM Release 9 Mohawk 0x007c moh Release 7 Mohawk Canada 0x047c moh-CA Release E2
Revision Summary Date Revision History Revision Comments 5/24/2012 1.0 New Released new document. 6/29/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/23/2012 2.0 Major Updated and revised the technical content. 3/26/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/11/2013 2.0 None No changes to the meaning, language, or formatting of the technical content.
8/8/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 12/5/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2014 3.0 Major Updated and revised the technical content. 5/20/2014 3.0 None No changes to the meaning, language, or formatting of the technical content. 5/10/2016 4.0 Major Significantly changed the technical content. 8/16/2017 5.0 Major Significantly changed the technical content. 5/24/2018 6.0 Major Significantly changed the technical content.
Index A 18 7 29 18 25 21 23 21 22 18 19 24 24 B 26 C 44 8 Complex types 18 18 25 21 23 21 22 18 19 24 24 24 21 8 8 22 19 21 17 19 24 D 8 Details 8 E 21 Examples 29 33 31 8 8 8 F 35 7 36 G 33 8 5 I 35 35 6 5 L 7 M 22 19 31 N 8 28 6 O 6 P 21 43 R 5 6 6 6 S Security 35 35 Simple
11/6/2009 2.1.1 Editorial Changed language and formatting in the technical content. 12/18/2009 2.1.2 Editorial Changed language and formatting in the technical content. 1/29/2010 2.2 Minor Clarified the meaning of the technical content. 3/12/2010 2.2.1 Editorial Changed language and formatting in the technical content. 4/23/2010 2.2.2 Editorial Changed language and formatting in the technical content. 6/4/2010 2.2.3 Editorial Changed language and formatting in the technical content. 7/16/2010 2.2.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 2.2.3 None No changes to the meaning, language, or formatting
of the technical content. 10/8/2010 2.2.3 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 2.2.3 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 3.0 Major Updated and revised the technical content. 2/11/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 3.1 Minor Clarified the meaning of
the technical content. 9/23/2011 3.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 4.0 Updated and revised the technical content. 3/30/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 5.0 Major Updated and revised the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.1 Clarified the meaning of the technical content. 8/8/2013 6.0 Major Updated and revised the technical content. 11/14/2013 6.0 None No changes to the meaning, language,
Index A Abstract data model 10 9 6 C 6 18 D Data model - abstract 10 9 E 12 F 7 G 5 H Higher-layer triggered events 11 9 I 16 16 6 Initialization 11 9 5 L Local events 11 10 M Message processing 11 9 Messages 8 8 N 5 O 6 P 16 6 6 17 R 5 6 5 6 Responder 10 11 11 11 11 10 11 11 10 S Security 16 16 Sender 9 9 9 10 9 9 9 10 9 Sequencing rules 11 9 7 8 T Timer events 11 10 Timers 10 9 18
Index A 11 C 43 12 22 21 22 19 16 20 38 D 12 Details 12 21 Directory sectors 22 26 22 27 26 E 30 30 30 31 31 32 32 35 35 36 36 30 F 19 11 38 G 5 H Header ( 16, 30) I 8 4 L 11 M 20 N 8 O 12 8 P 39 R 28 27 8 8 8 10 26 S
Revision Summary Date Revision History Revision Class Comments 10/24/2008 0.2 New Version 0.2 release 12/5/2008 1.0 Major Updated and revised the technical content. 1/16/2009 1.1 Minor Clarified the meaning of the technical content. 2/27/2009 1.1.1 Editorial Changed language and formatting in the technical content. 4/10/2009 2.0 Major Updated and revised the technical content. 5/22/2009 2.0.1 Editorial Changed language and formatting in the technical content. 7/2/2009 2.0.2 Editorial Changed language and formatting in the technical content. 8/14/2009 2.0.3 Editorial Changed language and formatting in the technical content. 9/25/2009 2.1 Minor Clarified the meaning of the technical content.
of the technical content. 10/8/2010 2.2.3 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 2.2.3 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 3.0 Major Updated and revised the technical content. 2/11/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 3.1 Minor Clarified the meaning of
the technical content. 9/23/2011 3.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 4.0 Updated and revised the technical content. 3/30/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 5.0 Major Updated and revised the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.1 Clarified the meaning of the technical content. 8/8/2013 6.0 Updated and revised the technical content. 11/14/2013 6.0 None No changes to the meaning, language,
or formatting of the technical content. 2/13/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 7.0 Major Significantly changed the technical content. 10/16/2015 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 7.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 10 9 6 C 7 18 D Data - abstract 10 9 E 12 F 7 G 5 H Higher-layer triggered events 11 9 I 16 16 6 Initialization 11 9 5 L Local events 11 10 M Message processing 11 9 Messages 8 8 N 5 O 6 P 16 6 6 17 R 5 6 5 6 Responder 10 11 11 11 11 10 11 11 10 S Security 16 16 Sender 9 9 9 10 9 9 9 10 9 Sequencing rules 11 9 7 8 T Timer events 11 10 Timers 10
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 Type Length Physical Medium ... Type (1 byte): This field MUST be set to 0x03. Length (1 byte): This field MUST be set to 0x04. Physical Medium (4 bytes): This field MUST be set to the physical medium type of the network interface that the responder is using. The values are published by the Internet Assigned Numbers Authority (IANA) for the ifType object, as specified in . Wireless Mode The Wireless Mode attribute identifies how an Institute of Electrical and Electronics Engineers (IEEE) 802.11, as specified in , network interface connects to the network. Implementations with responders in 802.11 stations MUST include this attribute in all Hello frames. 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 Type Length Mode Type (1 byte): This field MUST be set to 0x04. Length (1 byte): This field MUST be set to 0x01. Mode (1 byte): This specifies the method by which a responder's IEEE 802.11 network interface connects to the network. The following table shows valid values. Value Meaning 0x00 802.11 IBSS or ad-hoc mode, as specified in [IEEE802.11-2007]. 0x01 802.11 infrastructure mode, as specified in [IEEE802.11-2007]. 802.11 BSSID The 802.11 BSSID attribute specifies an IEEE 802.11 network interface's associated AP. Implementations with responders in 802.11 stations MUST include this attribute in all Hello frames. 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 Type Length ... Type (1 byte): This field MUST be set to 0x05. Length (1 byte): This field MUST be set to 0x06.
Index A Abstract data model 67 51 56 62 88 92 72 79 33 60 17 19 29 30 B 35 35 Block timer ( 54, 76) 33 22 34 C 18 108 21 82 86 87 33 30 32 analysis 68 69 Cross-traffic analysis initiator 67 68 68 70 69 67 69 69 68 D Data model - abstract 67 51 56 62 88 92 72 79 19 35 32 29 27 74 37 75 E 75 83 87 38 20 Enumerator 51 52 52 55 53 50 53 54 52 Enumerator as mapper ( 53, 54) 62 Examples 96 99 96 103 F 18 60 41 31 27 G 9 H 31 27 frame ( 53, 75) 77 38 Higher-layer triggered events 68 52 57 64 89 94 74
82 20 I 31 25 105 92 105 12 Initialization 68 52 57 64 89 93 73 81 9 23 23 L 31 31 57 32 34 95 25 75 Local events 70 55 62 67 92 95 77 87 M 26 Mapper 56 57 57 62 60 55 60 62 56 24 95 disconnect event ( 77, 87, 92) Message processing 69 53 60 65 89 94 74 82 19 Messages 35 19 31 19 47 43 36 19 36 19 N 74 75 96 99 Network test session ( 64, 65) 57 11 O 12 P 105 77 24 69 66 67 67 67 62 69 21 28 17 17 85 106 Protocol Details 50 Q QoS controller 62 64 64 67 65 62 65 66 63 QoS diagnostics
14 network test ( 14, 43) 47 QoS sink 88 89 89 92 89 88 89 92 89 28 47 43 66 47 94 49 69 48 94 48 66 47 89 44 QosProbe frame ( 65, 90) 44 91 66 46 66 44 91 85 86 42 61 42 60 40 Quick discovery ( 13, 36) 53 52 Quiescent state ( 77, 87) R 11 12 11 17 103 30 69 75 Responder (QoS cross-traffic) 92 94 93 95 94 92 94 95 93 Responder (quick discovery) 72 74 73 77 74 70 74 76 73 Responder (topology discovery) 79 82 81 87 82 78 82 86 81 25 S Security 105 105 105 29 Sequencing rules 69 53 60 65 89 94 74 82 76 59 95 23 18 57 26 19 35 19 31 47 43 36 36 T 59 events 69 54 62 66
References Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the . Normative References We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact . We will assist you in finding the relevant information. [MS-DTYP] Microsoft Corporation, "". [RFC2119] Bradner, S., "Key for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, [UNICODE3.0.1] The Unicode Consortium, "Unicode Default Case Conversion Algorithm 3.0.1", August 2001, [UNICODE5.0.0] The Unicode Consortium, "Unicode Default Case Conversion Algorithm 5.0.0", March 2006, Informative References [MS-OLEDS] Microsoft Corporation, "". [MS-OLEPS] Microsoft Corporation, "". [MSDN-SS] Microsoft Corporation, "Structured Storage", Overview A compound file (2) is a structure that is used to a hierarchy of storage objects and stream objects into a single file or memory buffer. A storage object is analogous to a file system directory. Just as a directory can contain other directories and files, a storage object can contain other storage objects and stream objects. Also like a directory, a storage object tracks the locations and sizes of the child storage object and stream objects that are nested beneath it. A stream object is analogous to the traditional notion of a file. Like a file, a contains that is stored as a consecutive sequence of bytes. The hierarchy is defined by a / relationship. cannot contain child objects. Storage objects can contain stream objects and/or other storage objects, each of which has a name that uniquely identifies it among the child objects of its parent storage object. The has no parent object. The root storage object also has no name. Because names are used to identify child objects, a name for the root storage object is unnecessary and the file format does not provide a representation for it. Figure : Example of a structured storage compound file
Index A 11 C 43 12 22 21 22 19 16 20 38 D 12 Details 12 21 Directory sectors 22 26 22 27 26 E 30 30 30 31 31 32 32 35 35 36 36 30 F 19 11 38 G 5 H Header ( 16, 30) I 8 4 L 11 M 20 N 8 O 12 8 P 39 R 28 27 8 8 8 10 26 S 31 31 32 32 35 35 36 36 14 Security 38 38 38 Security considerations 38 38 28 Structures 12 T 30 43 U