631
[MS-DHCPM]: Microsoft Dynamic Host Configuration Protocol (DHCP) Server Management Protocol Intellectual Property Rights Notice for Open Specifications Documentation § Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. § Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. § No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. § Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise . If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected] . § Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks . § Fictitious Names. The example companies, organizations, products, domain names, e- mail addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have 1 / 631 [MS-DHCPM] - v20150630 Microsoft Dynamic Host Configuration Protocol (DHCP) Server Management Protocol Copyright © 2015 Microsoft Corporation Release: June 30, 2015

Introduction - Microsoft Web viewOptions can be of type BYTE, WORD, DWORD ... Access Protection (NAP) ". [MS-DTYP ... it received the message or the IP address of the relay agent in

Embed Size (px)

Citation preview

[MS-DHCPM]:

Microsoft Dynamic Host Configuration Protocol (DHCP) Server Management Protocol

Intellectual Property Rights Notice for Open Specifications Documentation

Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies.

Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications.

No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.

Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].

Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.

Fictitious Names. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.

Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise.

Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.

Revision Summary

Date

Revision History

Revision Class

Comments

1/25/2008

0.1

Major

MCPP Milestone RSAT Initial Availability

3/14/2008

1.0

Major

Updated and revised the technical content.

5/16/2008

1.0.1

Editorial

Changed language and formatting in the technical content.

6/20/2008

2.0

Major

Updated and revised the technical content.

7/25/2008

2.1

Minor

Clarified the meaning of the technical content.

8/29/2008

2.2

Minor

Clarified the meaning of the technical content.

10/24/2008

3.0

Major

Updated and revised the technical content.

12/5/2008

4.0

Major

Updated and revised the technical content.

1/16/2009

4.1

Minor

Clarified the meaning of the technical content.

2/27/2009

5.0

Major

Updated and revised the technical content.

4/10/2009

6.0

Major

Updated and revised the technical content.

5/22/2009

7.0

Major

Updated and revised the technical content.

7/2/2009

8.0

Major

Updated and revised the technical content.

8/14/2009

8.1

Minor

Clarified the meaning of the technical content.

9/25/2009

9.0

Major

Updated and revised the technical content.

11/6/2009

10.0

Major

Updated and revised the technical content.

12/18/2009

11.0

Major

Updated and revised the technical content.

1/29/2010

12.0

Major

Updated and revised the technical content.

3/12/2010

13.0

Major

Updated and revised the technical content.

4/23/2010

14.0

Major

Updated and revised the technical content.

6/4/2010

15.0

Major

Updated and revised the technical content.

7/16/2010

16.0

Major

Updated and revised the technical content.

8/27/2010

17.0

Major

Updated and revised the technical content.

10/8/2010

18.0

Major

Updated and revised the technical content.

11/19/2010

19.0

Major

Updated and revised the technical content.

1/7/2011

20.0

Major

Updated and revised the technical content.

2/11/2011

21.0

Major

Updated and revised the technical content.

3/25/2011

22.0

Major

Updated and revised the technical content.

5/6/2011

22.0

None

No changes to the meaning, language, or formatting of the technical content.

6/17/2011

22.1

Minor

Clarified the meaning of the technical content.

9/23/2011

23.0

Major

Updated and revised the technical content.

12/16/2011

24.0

Major

Updated and revised the technical content.

3/30/2012

24.0

None

No changes to the meaning, language, or formatting of the technical content.

7/12/2012

25.0

Major

Updated and revised the technical content.

10/25/2012

26.0

Major

Updated and revised the technical content.

1/31/2013

26.0

None

No changes to the meaning, language, or formatting of the technical content.

8/8/2013

27.0

Major

Updated and revised the technical content.

11/14/2013

28.0

Major

Updated and revised the technical content.

2/13/2014

28.0

None

No changes to the meaning, language, or formatting of the technical content.

5/15/2014

28.0

None

No changes to the meaning, language, or formatting of the technical content.

6/30/2015

29.0

Major

Significantly changed the technical content.

Table of Contents

1Introduction12

1.1Glossary12

1.2References18

1.2.1Normative References18

1.2.2Informative References19

1.3Overview19

1.4Relationship to Other Protocols21

1.5Prerequisites/Preconditions26

1.6Applicability Statement26

1.7Versioning and Capability Negotiation26

1.8Vendor-Extensible Fields27

1.9Standards Assignments27

2Messages28

2.1Transport28

2.1.1Server Security Settings28

2.1.2DHCPM Client Security Settings28

2.2Common Data Types28

2.2.1DHCP RPC Common Messages29

2.2.1.1Datatypes, Enumerations, and Constants29

2.2.1.1.1DHCP_ATTRIB_ID29

2.2.1.1.2DHCP_SUBNET_STATE29

2.2.1.1.3DHCP_SEARCH_INFO_TYPE30

2.2.1.1.4DHCP_OPTION_SCOPE_TYPE30

2.2.1.1.5DHCP_OPTION_SCOPE_TYPE631

2.2.1.1.6DHCP_OPTION_TYPE31

2.2.1.1.7DHCP_SUBNET_ELEMENT_TYPE32

2.2.1.1.8DHCP_SUBNET_ELEMENT_TYPE_V632

2.2.1.1.9DHCP_FORCE_FLAG33

2.2.1.1.10DHCP_OPTION_DATA_TYPE33

2.2.1.1.11QuarantineStatus34

2.2.1.1.12DHCP_SEARCH_INFO_TYPE_V635

2.2.1.1.13DHCP_SCAN_FLAG35

2.2.1.1.14DHCP_RESUME_IPV6_HANDLE35

2.2.1.1.15LPWSTR36

2.2.1.1.16LPWSTR_RPC_STRING36

2.2.1.1.17DHCP_FILTER_LIST_TYPE36

2.2.1.1.18DHCP_FAILOVER_MODE36

2.2.1.1.19DHCP_FAILOVER_SERVER37

2.2.1.1.20FSM_STATE37

2.2.1.1.21DHCP_POLICY_FIELDS_TO_UPDATE38

2.2.1.1.22DHCP_POL_COMPARATOR38

2.2.1.1.23DHCP_POL_ATTR_TYPE39

2.2.1.1.24DHCP_POL_LOGIC_OPER39

2.2.1.1.25DHCP_MAX_FREE_ADDRESSES_REQUIRED40

2.2.1.1.26DHCP_PROPERTY_TYPE40

2.2.1.1.27DHCP_PROPERTY_ID40

2.2.1.2Structures41

2.2.1.2.1DHCP_IP_ADDRESS41

2.2.1.2.2DHCP_IP_MASK41

2.2.1.2.3DHCP_OPTION_ID41

2.2.1.2.4DHCP_SRV_HANDLE41

2.2.1.2.5DHCP_CLIENT_UID41

2.2.1.2.5.1Representing a DHCPv4 Client-Identifier42

2.2.1.2.5.2Representing a DHCPv4 Client Unique ID42

2.2.1.2.5.3Representing a DHCPv6 Client-Identifier43

2.2.1.2.5.4Representing a MADCAP Lease Identifier43

2.2.1.2.6DHCP_RESUME_HANDLE43

2.2.1.2.7DHCP_HOST_INFO44

2.2.1.2.8DHCP_SUBNET_INFO44

2.2.1.2.9DHCP_BINARY_DATA45

2.2.1.2.10DHCP_IP_RESERVATION45

2.2.1.2.11DATE_TIME45

2.2.1.2.12DHCP_CLIENT_INFO45

2.2.1.2.13DHCP_CLIENT_INFO_ARRAY46

2.2.1.2.14DHCP_CLIENT_INFO_V446