DHCP Service Management Profile

Transcription

1 Document Number: DSP1068 Date: Version: 1.0.0a 5 6 Information for Work-in-Progress version: IMPORTANT: This document is not a standard. It does not necessarily reflect the views of the DMTF or all of its members. Because this document is a Work in Progress, it may still change, perhaps profoundly. This document is available for public review and comment until superseded. Provide any comments through the DMTF Feedback Portal: Supersedes: None Document Type: Specification Document Class: Normative Document Status: Work in Progress Document Language: en-us

2 DSP Copyright Notice Copyright Distributed Management Task Force, Inc. (DMTF). All rights reserved. DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability. Members and non-members may reproduce DMTF specifications and documents, provided that correct attribution is given. As DMTF specifications may be revised from time to time, the particular version and release date should always be noted. Implementation of certain elements of this standard or proposed standard may be subject to third party patent rights, including provisional patent rights (herein "patent rights"). DMTF makes no representations to users of the standard as to the existence of such rights, and is not responsible to recognize, disclose, or identify any or all such third party patent right, owners or claimants, nor for any incomplete or inaccurate identification or disclosure of such rights, owners or claimants. DMTF shall have no liability to any party, in any manner or circumstance, under any legal theory whatsoever, for failure to recognize, disclose, or identify any such third party patent rights, or for such party s reliance on the standard or incorporation thereof in its product, protocols or testing procedures. DMTF shall have no liability to any party implementing such standard, whether such implementation is foreseeable or not, nor to any patent owner or claimant, and shall have no liability or responsibility for costs or losses incurred if a standard is withdrawn or modified after publication, and shall be indemnified and held harmless by any party implementing the standard from any and all claims of infringement by a patent owner for such implementations. For information about patents held by third-parties which have notified the DMTF that, in their opinion, such patent may relate to or impact implementations of DMTF standards, visit Work In Progress Version 1.0.0a

3 DSP CONTENTS Foreword... 5 Introduction Scope Normative references Terms and definitions Symbols and abbreviated terms Synopsis Description Class diagram Security Aspects of DHCP Service Operations Representation of DHCP Service Usage Data (Statistics) Implementation Representing a DHCP service CIM_DHCPServiceCapabilities CIM_ProtocolService.RequestedState CIM_ProtocolService.EnabledState DHCP Service access representation Relationship with Service Port for DHCP Offer DHCP Service Default Configuration UDP Ports Methods Profile conventions for operations CIM_DHCPServiceCapabilities CIM_DHCPServiceProtocolEndpoint CIM_DHCPServiceSettingData CIM_RemoteServiceAccessPoint CIM_ElementCapabilities CIM_ElementSettingData CIM_SAPSAPDependency CIM_HostedAccessPoint CIM_RemoteAccessAvailableToElement Use cases Profile Registration Adding a UDP port for the DHCP Service Obtain DHCP Service Configuration Perform DHCP Service Configuration Determine Which IP address versions Are Supported Obtain DHCP Service Statistics View Default Address Lease Time View Allocation Range and Allocated IP Addresses View all Clients who Request IP address View all Clients offered with IP address CIM Elements CIM_DHCPServiceCapabilities CIM_DHCPServiceProtocolEndpoint CIM_DHCPServiceSettingData CIM_RemoteServiceAccessPoint CIM_RegisteredProfile ANNEX A (informative) Change log Bibliography Version 1.0.0a Work In Progress 3

4 DSP Figures Figure 1 : Class diagram Figure 2 Registered profile Figure 3 UDP port configuration to specific interface Tables Table 1 Referenced profiles Table 2 Operations: CIM_ElementCapabilities Table 3 Operations: CIM_ElementSettingData Table 4 Operations: CIM_SAPSAPDependency Table 5 Operations: CIM_HostedAccessPoint Table 6 Operations: CIM_RemoteAccessAvailableToElement Work In Progress Version 1.0.0a

5 DSP Foreword The (DSP1068) was prepared by the Network Services Management Working Group of the DMTF. DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability Acknowledgments The DMTF acknowledges the following individuals for their contributions to this document: Editors: Bhumip Khasnabish - ZTE Corporation ZhongYu Gu ZTE Corporation Ghazanfar Ali ZTE Corporation Contributors: Ghazanfar Ali ZTE Corporation John Crandall Brocade Communications System ZhongYu Gu ZTE Corporation Bhumip Khasnabish - ZTE Corporation Lawrence Lamers VMware John Parchem DMTF Fellow Shishir Pardikar Citrix Hemal Shah Broadcom Corporation Eric Wells Hitachi Alex Zhdankin Cisco Systems 123 Version 1.0.0a Work In Progress 5

6 DSP Introduction The information in this specification should be sufficient for a provider or consumer of this data to identify unambiguously the classes, properties, methods, and values that shall be instantiated and manipulated to represent and manage Network Services and the associated configuration information. The target audience for this specification is implementers who are writing CIM-based providers or consumers of management interfaces that represent the component described in this document Document conventions Typographical conventions The following typographical conventions are used in this document: Document titles are marked in italics. ABNF rules are in monospaced font Work In Progress Version 1.0.0a

7 DSP Scope The is a profile that specifies the CIM schema and use cases associated with the general and common aspects of DHCP. This profile includes a specification of the DHCP service configuration, DHCP server representation (protocol service, DHCP server protocol endpoint), allocated IP address (List) (each IP address represents a client), DHCP server status, and DHCP server statistics. One of the objectives is to facilitate support of IPv4 and IPv6 addressing simultaneously. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated or versioned references, only the edition cited (including any corrigenda or DMTF update versions) applies. For references without a date or version, the latest published edition of the referenced document (including any corrigenda or DMTF update versions) applies. DMTF DSP0004, CIM Infrastructure Specification 2.6, DMTF DSP0200, CIM Operations over HTTP 1.3, DMTF DSP0223, Generic Operations 1.0, DMTF DSP1001, Management Profile Specification Usage Guide 1.0, DMTF DSP1033, Profile Registration Profile 1.0, DMTF DSP1097, Virtual Ethernet Switch Profile 1.1, DMTF DSP1036 IP Interface Profile 1.1.1, DMTF DSP1116 IP Configuration Profile 1.0.0, DMTF DSP1037 DHCP Client Profile 1.0.3, GIAC report on DHCP Server Security Audit, 2002, IETF RFC1208, A Glossary of Networking Terms, March 1991, IETF RFC1918, Address Allocation for Private Internets, February 1996, IETF RFC2131, Dynamic Host Configuration Protocol, March 1997, Version 1.0.0a Work In Progress 7

8 DSP IETF RFC2132, DHCP Options and BOOTP Vendor Extensions, March 1997, IETF RFC3118, Authentication for DHCP Messages, June 2001, IETF RFC3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6), July 2003, IETF RFC3442, The Classless Static Route Option for DHCPv4, Dec. 2002, IETF RFC3633, IPv6 Prefix Options for DHCP version 6, Dec. 2003, IETF RFC4291, IP version 6 Addressing Architecture, Feb. 2006, IETF RFC4361, Node-specific Client Identifiers for DHCPv4, Feb. 2006, IETF RFC6221, Lightweight DHCPv6 Relay Agent, May 2011, IETF RFC 6603, Prefix Exclude Option for DHCPv6-based Prefix Delegation, May 2012, IETF RFC6842, Client Identifier Option in DHCP Server Replies, January 2013, ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards, 3 Terms and definitions In this document, some terms have a specific meaning beyond the normal English meaning. Those terms are defined in this clause. The terms "shall" ("required"), "shall not", "should" ("recommended"), "should not" ("not recommended"), "may," "need not" ("not required"), "can" and "cannot" in this document are to be interpreted as described in ISO/IEC Directives, Part 2, Annex H. The terms in parenthesis are alternatives for the preceding term, for use in exceptional cases when the preceding term cannot be used for linguistic reasons. Note that ISO/IEC Directives, Part 2, Annex H specifies additional alternatives. Occurrences of such additional alternatives shall be interpreted in their normal English meaning. The terms "clause", "subclause", "paragraph", and "annex" in this document are to be interpreted as described in ISO/IEC Directives, Part 2, Clause 5. The terms "normative" and "informative" in this document are to be interpreted as described in ISO/IEC Directives, Part 2, Clause 3. In this document, clauses, subclauses, or annexes labeled "(informative)" do not contain normative content. Notes and examples are always informative elements. The terms defined in DSP0004, DSP0223, and DSP1001 apply to this document. The following additional terms are used in this document. 3.1 conditional indicates requirements to be followed strictly to conform to the document when the specified conditions are met 8 Work In Progress Version 1.0.0a

9 DSP mandatory indicates requirements to be followed strictly to conform to the document and from which no deviation is permitted 3.3 optional indicates a course of action permissible within the limits of the document 3.4 pending configuration indicates the configuration that will be applied to an IP network connection the next time the IP network connection accepts a configuration 3.5 referencing profile indicates a profile that owns the definition of this class and can include a reference to this profile in its Referenced Profiles table 3.6 unspecified indicates that this profile does not define any constraints for the referenced CIM element or operation 4 Symbols and abbreviated terms The abbreviations defined in DSP0004, DSP0223, and DSP1001 apply to this document. The following additional abbreviations are used in this document. 4.1 IP Internet Protocol 4.2 DHCP Dynamic Host Configuration Protocol 4.3 UDP User Datagram Protocol 5 Synopsis Profile name: Version: Organization: DMTF CIM Schema version: 2.44 Central class: CIM_ProtocolService Scoping class: CIM_ComputerSystem Version 1.0.0a Work In Progress 9

10 DSP The is a profile that specifies the CIM schema and use cases associated with DHCP. This profile includes a specification of the DHCP service configuration, DHCP server representation (protocol service, DHCP server protocol end-point), allocated IP address (List) (each IP address represents a client), DHCP client (remote service access point), DHCP server status, and DHCP server statistics. Table 1 identifies profiles on which this profile has a dependency. Table 1 Referenced profiles Profile Name Organization Version Requirement Description Profile Registration DMTF 1.0 Mandatory None IP Configuration DMTF 1.0 Mandatory DSP1116 IP Interface DMTF Mandatory DSP1036 Network Management DMTF 1.0 Optional None Description The is a profile that will specify the CIM schema and use cases associated with the general and common aspects of DHCP. This profile includes a specification of the DHCP service configuration, DHCP server representation (protocol service, DHCP server protocol endpoint), allocated IP address (List) (each IP address represents a client), DHCP client (remote service access point), DHCP server status, and DHCP server statistics. 10 Work In Progress Version 1.0.0a

11 DSP Class diagram Figure 1 represents the class schema for the. For simplicity, the CIM_ prefix has been removed from the names of the classes. 271 ComputerSystem (see Computer System Profile) 1..* RegisteredProfile (see Profile Registration Profile) * * * ReferencedProfile DHCPServiceCapabilities HostedService 1..* {v4, v6} ElementConformsToProfile ElementCapabilities DHCPServiceProtocolEndpoint * ServiceAffectsElement 1 * 1 1 * ProtocolService 1 1 ServiceAccessBySAP UDPProtocolEndpoint * * BindsTo ElementSettingData StatisticalData (See Core Model) 1..* IPProtocolEndpoint (see IP Interface Profile) {v4, v6} * DHCPServiceStats DomainNameUsed: uint32 ElementStatisticalData DHCPServiceSettingData {v4, v6} * Figure 1 : Class diagram Figure 1 is a class diagram for the DHCP service profile. The following classes are pertinent to represent the management aspects of DHCP service DHCPServiceProtocolEndpoint, ProtocolService, IPAddressAllocationService, DHCPServiceCapabilities, and DHCPServiceSettingData The DHCP Service is represented by an instance of CIM_ProtocolService. The capabilities of the DHCP service are represented by an instance of CIM_DHCPServiceCapabilites. The access to the DHCP service is represented by CIM_DHCPServiceProtocolEndPoint. Each DHCPServiceSettingData request is resolved via an IPAddressAllocationService of the ProtocolService., Version 1.0.0a Work In Progress 11

12 DSP DHCP service typically supports the following capabilities Have a range of IPv4 address (per RFC 1918) with a starting address and a list of exclusions, if applicable, and assign one to a client Allocate a lease period in hours (default is eight days) for an IP address Default gateway address with specific IPv4 address and no-notify options A list of notify DNS servers (primary, secondary, and none) A list of WINS servers (primary, secondary, and none) A list of Domain names (assigned, specific, and none) DHCP service responds to a DHCP-Discover message from the DHCP Relay Agent or DHCP Client with DHCP-Offer message. DHCP service receives to a DHCP-Request message from the DHCP Bridge or DHCP Client and responds with DHCP-Ack message. Support of IPv4 to/from IPv6 and dual (both IPv4 and IPv6) stack may be desirable and increasingly becoming the norm. 6.2 Security Aspects of DHCP Service Operations Note that DHCP server operates by offering (DHCPOFFER) to lease an IP address in response to DHCP clients broadcast discovery messages (DHCPDISCOVER) containing their MAC addresses. The client shall respond (DHCPREQUEST) to the first lease offer it receives and the server shall acknowledge (DHCPACK) the request and shall mark the address as leased in the DHCP database. Because of the simplicity of operation of the DCHP server, there are many authorization and security concerns. These concerns may be addressed via the following practices: Use domain controller based authorization at the first at boot time to verify that the DHCP server s IP address is white-listed. Use pre-authorization and authentication in order to determine which DHCP server may lease IP address to which MAC address holders. Use authentication of DHCP messages per IETF RFC 3118 using either a token-based exchange of messages or a shared symmetric key, which involves additional initial configuration of the DHCP client. Use IPv6 to protect the DHCP traffic; IPv6 has been designed to offer end-to-end security. Routinely audit the database of the DHCP servers in order to verify that only the authorized DHCP clients are leasing addresses from the server (see for example the GIAC report on DHCP Server Security Audit, Representation of DHCP Service Usage Data (Statistics) The DHCP service (server) usage data may include one or more of the following parameters: Maximum, average, and minimum number of clients served over a specific time period (e.g., twenty-four hour) Frequency with which the clients renew their leases Up-time (MTTF or mean time-to-failure), down-time (MTTR or mean-time-to-repair), and sustained overload time of the server Numbers of upstream/downstream servers for which a DHCP server being used as relay and/or bridge server (beyond the scope of this version) Record of failure events and how in terms of response, response time, and capacity the clients' requests were handled The CIM_DHCPServiceProtocollEndpointStats represents statistics of operation of the DHCP service. 12 Work In Progress Version 1.0.0a

13 DSP Implementation This clause details the requirements related to the arrangement of instances and the properties of instances for implementations of this profile. 7.1 Representing a DHCP service Exactly one instance of CIM_ProtcolService shall represent the DHCP service being modeled. In CIM_ProtcolService.Protocol, the Protocol property of the CIM_ProtocolService instance shall have a value of X (DHCP) CIM_DHCPServiceCapabilities Exactly one instance of CIM_DHCPServiceCapabilities shall be associated with the CIM_ProtocolService instance through an instance of CIM_ElementCapabilities. This instance of CIM_DHCPServiceCapabilities shall represent the capabilities of the DHCPservice CIM_DHCPServiceCapabilities.RequestedStatesSupported The RequestedStatesSupported property may contain zero or more of the following values: 2 (Enabled), 3 (Disabled), or 11 (Reset) CIM_ProtocolService.RequestedState When the CIM_ProtocolService.RequestStateChange( ) method is successfully invoked, the value of the RequestedState property shall be the value of the RequestedState parameter. If the method is not successfully invoked, the value of the RequestedState property is indeterminate. The CIM_ProtocolService.RequestedState property shall have one of the values specified in the CIM_DHCPServiceCapabilities.RequestedStatesSupported property or a value of 5 (No Change) CIM_ProtocolService.EnabledState When the RequestedState parameter has a value of 2 (Enabled) or 3 (Disabled) and the CIM_ProtocolService.RequestStateChange( ) method completes successfully, the value of the EnabledState property shall equal the value of the CIM_ProtocolService.RequestedState property. If the method does not complete successfully, the value of the EnabledState property is indeterminate. The EnabledState property shall have the value 2 (Enabled), 3 (Disabled), or 6 (Enabled but Offline). 7.2 DHCP Service access representation The access to DHCP service shall be modeled using at least one instance of CIM_DHCPServiceProtocolEndpoint class Relationship with Service An instance of CIM_ProvidesEndpoint shall associate the CIM_ProtocolService with the CIM_DHCPServiceProtocolEndpoint Port for DHCP Offer An implementation may model the UDP port to which the DHCP resolution session is bound. When the implementation models the UDP port, the following requirements apply. Version 1.0.0a Work In Progress 13

14 DSP CIM_UDPProtocolEndpoint When the UDP port on which the DHCP resolution session is bound is modeled, the UDP port shall be modeled using an instance of CIM_ UDPProtocolEndpoint Relationship to DHCP Offer An instance of CIM_BindsTo shall associate the CIM_DHCPServiceProtocolEndpoint instance with the CIM_UDPProtocolEndpoint. 7.3 DHCP Service Default Configuration The default configuration is the configuration of the DHCP service when it was first installed on the managed system. When an implementation exposes the default configuration, the default configuration shall be represented by an instance of CIM_DHCPerviceSettingData associated with the CIM_ProtocolService through an instance of CIM_ElementSettingData, where the IsDefault property of the CIM_ElementSettingData instance has a value of 1 (Is Default) UDP Ports An implementation may model one or more UDP ports of the DHCP service. When the implementation models the UDP ports, the following requirements shall apply for each UDP port CIM_UDPProtocolEndpoint There shall be an instance of CIM_UDPProtocolEndpoint in which the PortNumber property of the instance indicates the UDP port number on which the DHCP service is accessible Relationship of UDP Port to the DHCP Service An instance of CIM_ServiceAccessBySAP shall associate the CIM_ProtocolService instance with the CIM_UDPProtocolEndpoint instance Managing UDP Ports The implementation may support managing the UDP ports on which the DHCP service is accessible. The access method ( ) method of the CIM_ProtocolService class can be used to add ports on which the DHCP service will be accessible. The AssignUDPPort( ) method of the CIM_ProtocolService class can be used to add UDP ports on which the DHCP service will be accessible. Using the RemoveUDPPort( ) intrinsic operation to remove an instance of CIM_UDPProtocolEndpoint will stop the DHCP service from being accessible. 8 Methods 8.1 Profile conventions for operations For each profile class (including associations), the implementation requirements for operations, including those in the following default list, are specified in class-specific sub-clauses of this clause. The default list of operations is as follows: GetInstance EnumerateInstances EnumerateInstanceNames Associators AssociatorNames 14 Work In Progress Version 1.0.0a

15 DSP References ReferenceNames CIM_DHCPServiceCapabilities All operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. 8.3 CIM_DHCPServiceProtocolEndpoint All operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. 8.4 CIM_DHCPServiceSettingData All operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. 8.5 CIM_RemoteServiceAccessPoint All operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. 8.6 CIM_ElementCapabilities Table 2 lists implementation requirements for operations. If implemented, these operations shall be implemented as defined in DSP0200. In addition, and unless otherwise stated in Table 2, all operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. Table 2 Operations: CIM_ElementCapabilities Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None CIM_ElementSettingData Table 3 lists implementation requirements for operations. If implemented, these operations shall be implemented as defined in DSP0200. In addition, and unless otherwise stated in Table 3, all operations in 444 the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. Table 3 Operations: CIM_ElementSettingData Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None CIM_SAPSAPDependency Table 4 lists implementation requirements for operations. If implemented, these operations shall be implemented as defined in DSP0200. In addition, and unless otherwise stated in Table 4, all operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. Version 1.0.0a Work In Progress 15

16 DSP Table 4 Operations: CIM_SAPSAPDependency Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None CIM_HostedAccessPoint Table 5 lists implementation requirements for operations. If implemented, these operations shall be implemented as defined in DSP0200. In addition, and unless otherwise stated in Table 5, all operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. Table 5 Operations: CIM_HostedAccessPoint Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None CIM_RemoteAccessAvailableToElement Table 6 lists implementation requirements for operations. If implemented, these operations shall be implemented as defined in DSP0200. In addition, and unless otherwise stated in Table 6 all operations in the default list in 8.1 shall be implemented as defined in DSP0200. NOTE Related profiles may define additional requirements on operations for the profile class. Table 6 Operations: CIM_RemoteAccessAvailableToElement Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None Work In Progress Version 1.0.0a

17 DSP Use cases This clause contains object diagrams and use cases for the. 9.1 Profile Registration The object diagram in Figure 2 shows one possible method for advertising profile conformance. The instances of CIM_RegisteredProfile are used to identify the version of the Network Service Management DHCP Server Profile with which an instance of CIM_ProtocolService is conformant. An instance of CIM_RegisteredProfile exists for each profile that is instrumented in the computer system. One instance of CIM_RegisteredProfile identifies the DHCP service profile The other instance identifies the Network Service Management DHCP Server Profile. The CIM_ProtocolService instance is scoped to an instance of CIM_ComputerSystem. ElementConformsToProfile cs : ComputerSystem profile 3 : RegisteredProfile RegisteredOrganization : DMTF RegisteredName : Base Server RegisteredVersion : HostedAccessPoint ReferencedProfile HostedAccessPoint profile 1 : RegisteredProfile RegisteredOrganization : DMTF RegisteredName : DHCP Service RegisteredVersion : ReferencedProfile ip: IPProtocolEndPoint (Protocol: IPv4, IPv6) SAPSAPDependency profile 2 : RegisteredProfile dhcp: DHCPServiceProtocolEndPoint RegisteredOrganization : DMTF RegisteredName : IP Interface RegisteredVersion : (Protocol: DHCPv4, DHCPv6) Figure 2 Registered profile 9.2 Adding a UDP port for the DHCP Service An implementation can support adding and removing bindings between the DHCP service and UDP ports. When an implementation supports adding bindings, a client can configure the service to be accessible on all interfaces or a specific interface. To have the DHCP service accessible on a UDP port across all IP interfaces of the system, the client can invoke the AssignUDPPort method of the CIM_ProtocolService instance, specifying the desired PortNumber. Version 1.0.0a Work In Progress 17

18 DSP To have the DHCP service accessible on a UDP port for a specific interface, the client can invoke the AssignUDPPort( ) method of the CIM_ProtocolService instance, specifying a reference to the CIM_IPProtocolEndpoint instance that represents the specific IP interface. system1 : ComputerSystem dhcpsvccap : DHCPServiceCapabilities MaxEndPoints: Per RFC 1918 SupportedDHCPVersions: DHCPv1 SupportedAllocationPeriod: default, others,... SupportedDHCPServerType:primary, secondary ElementCapabilities HostedService HostedAccessPoint dhcpsvc1 : ProtocolService Protocol : DHCP ServiceAccessBySAP udpprotoendpt1 : UDPProtocolEndpoint PortNumber : 67 BindsTo BindsTo ipprotoendpt1 : IPProtocolEndpoint IPv4Address : ipprotoendpt2 : IPProtocolEndpoint IPv4Address : udpprotoendpt2 : UDPProtocolEndpoint PortNumber : 68 BindsTo Figure 3 UDP port configuration to specific interface Figure 3 reflects the configuration where the AssignUDPPort( ) method was invoked with the IPEndpoint parameter containing a reference to ipprotoendpt2 and a PortNumber parameter of 68. The instance udpprotoendpt2 is created and associated with ipprotoendpt2 18 Work In Progress Version 1.0.0a

19 DSP Obtain DHCP Service Configuration A client may view information about the DHCP server that granted the lease to the DHCP client as follows: 1) Find all instances of CIM_RemoteAccessAvailableToElement that associate an instance of CIM_RemoteServiceAccessPoint with the CIM_DHCPProtocolEndpoint instance. If more than one instance exists, find the instance of CIM_RemoteAccessAvailableToElement in which the OrderOfAccess property has the value 1. Find the referenced CIM_RemoteServiceAccessPoint instance. If exactly one instance exists, find the referenced CIM_RemoteServiceAccessPoint instance. If no instances exist, no DHCP server is currently modeled for the DHCP client. 2) View the AccessInfo property of the CIM_RemoteServiceAccessPoint instance. 9.4 Perform DHCP Service Configuration Determine Which IP address versions Are Supported Both version 4 and version 6 of IP address scheme should be supported simultaneously. For IP version 6 (IPv6) operations, the client (or device) may use stateless address auto-configuration alternatively. For IPv4 operations, it is desirable to restrict addresses to local network link. View the DHCPType property of the CIM_DHCPServiceCapabilities instance to determine the support for IPv4 (IN-ADDR.ARPA) and IPv6(IP6.ARPA) addresses. IN-ADDR.ARPA property represents a domain that is defined to look up a record given an IPv4 address. In addition, IP6.ARPA property represents a special domain that is defined to look up a record given an IPv6 address. 9.5 Obtain DHCP Service Statistics Obtaining and viewing of the DHCP service statistics are discussed in this section. This includes viewing the management of a set of timers for leasing, monitoring-the use-of, monitoring-idle-time, renewing, etc. of the IP addresses that are issued and managed by a DHCP server View Default Address Lease Time This can be viewed by examining the properties of the associated instance of CIM_DHCPServiceSettingData View Allocation Range and Allocated IP Addresses A client can view the active configuration of the DHCP server as follows: (a) Find all instances of CIM_ElementSettingData that associate an instance of CIM_DHCPServiceSettingData with the CIM_DHCPServiceProtocolEndpoint instance, and (b) For each instance of CIM_ElementSettingData, see the value of the IsCurrent property View all Clients who Request IP address A client can find the DHCP server IP address as follows: (a) Find the instance of CIM_DHCPServiceProtocolEndpoint associated with the CIM_UDPProtocolEndpoint through an instance of CIM_BindsTo, (b) Find the instance of CIM_IPProtocolEndpoint associated with the CIM_UDPProtocolEndpoint through an instance of CIM_BindsTo, and (c) View the IPv4Address and IPv6Address properties of the CIM_IPProtocolEndpoint instance to find the IP address of the DHCP server. Version 1.0.0a Work In Progress 19

20 DSP View all Clients offered with IP address A client can find the DHCP request resolution policy of the DHCP server as follows: (a) Find the instance of CIM_DHCPServiceSettingData associated with the CIM_DHCPServiceProtocolEndpoint through an instance of CIM_ElementCapabilities, and (b) View the value of DHCPResolutionPolicy property of the CIM_DHCPServiceSettingData instance to find the DHCP request resolution policy of the DHCP server. 10 CIM Elements Table 7 shows the instances of CIM Elements for this profile. Instances of the CIM Elements shall be implemented as described in Table 7. Clauses 7 ( Implementation ) and 8 ( Methods ) may impose additional requirements on these elements. Table 7 CIM Elements: Element Name Requirement Description Classes CIM_DHCPServiceCapabilities Mandatory See Sec.8.2 and Sec.10.1 CIM_ DHCPServiceProtocolEndpoint Mandatory See Sec.8.3 and Sec.10.2 CIM_DHCPServiceSettingData Mandatory See Sec.8.4 and Sec.10.3 CIM_ RemoteServiceAccessPoint Mandatory See Sec.10.4 CIM_ ProtocolService Mandatory See Sec.7.1 CIM_ IPAddressAllocationService Mandatory CIM_RegisteredProfile Optional See clauses and Sec.10.5 (Table 12) Indications None defined in this profile CIM_DHCPServiceCapabilities CIM_DHCPServiceCapabilities represents the capabilities of DHCP service as supported and managed by the DHCP server in association with Address Allocation Server (AAS) and DHCP bridge and relay agent if/when applicable. Table 8 contains the requirements for elements of this class Table 8 Class: CIM_DHCPServiceCapabilities Element Name Requirement Description InstanceID Mandatory Key ElementName Mandatory Pattern ".*" AddressOrigin Mandatory This property shall have a value of 4 ( DHCPv4 ) or 7 ( DHCPv6 ). ProtocolIFType Mandatory This property shall have a value of 4096 (IPv4) or 4097 (IPv6). 20 Work In Progress Version 1.0.0a

21 DSP1068 Element Name Requirement Description DomainType Mandatory This property shall have a value of 1 (IPv4/ IN-ADDR.ARPA) or 2 (IPv6/IP6.ARPA). NameServerType Mandatory This property indicates role of the server and shall have a value of 1 (Primary name server), (Secondary name server), or 3 (Caching-only name server). DHCPDiscoverSupport Mandatory This property allows the DHCP server to assemble (using configuration file and global options, subnet-specific options, class-specific options, and client-specific options) and respond to Discover message received from a DHCP client (per RFC2131). DHCPRequestSupport Mandatory This property allows the DHCP server to (a) request for an IP address (from the address allocation server or AAS) for a client who sends an empty configuration file over Discover message, and (b) wait for a request from client accepting the configuration and IP address (per RFC2131). DHCPOfferSupport Mandatory This property allows the DHCP server to construct an "offer" message and send it to the client. The message contains a valid IP address and may contain client s configuration (per RFC2131). DHCPRenewSupport Mandatory This property allows the DHCP server process IP address renewal request from a client (per RFC2131). DHCPACKNACKSupport Mandatory This property allows the DHCP server to receive and process ACK (success or process complete) and NACK (negative ACK means process failure) messages from client, bridge and relay agent (per RFC2131). DHCPAASOptionSupport Mandatory This property allows the DHCP server to directly or indirectly (using a separate Address allocation server or AAS) allocate IP address dynamically from a subnet-specific pool(per RFC2131). DHCPServerManagerOptions Mandatory Two Options are supported: Global and Generic. Global DHCP options are usually the same for all hosts, e.g., list of DNS name servers and the name of the local domain. Generic DHCP options always override the globally defined option and are defined for sets of subnet, vendor class, user class, and client options (per RFC2131). The allocated IP address can be specific per client s request, a previously used one or random. DHCPv6OptionsSupport Optional DHCPv6 server behavior are as discussed in Sec.17.2, Sec.18.2, and Sec.19.1 of the IETF draft, DHCP for IPv6 ( DHCPv6, RFC3315). Version 1.0.0a Work In Progress 21

22 DSP CIM_DHCPServiceProtocolEndpoint CIM_DHCPServiceProtocolEndpoint represents the DHCP server protocol endpoint (essentially a DHCP client) that is associated with an IP interface. Table 9 contains the requirements for elements of this class. Table 9 Class: CIM_DHCPServiceProtocolEndpoint Element Name Requirement Description SystemCreationClassName Mandatory Key CreationClassName Mandatory Key SystemName Mandatory Key Name Mandatory Key NameFormat Mandatory Pattern ".*" ProtocolIFType Mandatory This property shall have a value of 1 (Other). OtherTypeDescription Mandatory This property shall have a value of DHCP. RequestedState Mandatory See of DSP1037 EnabledState Mandatory See of DSP1037 ClientState Mandatory See 7.2 of DSP1037 ElementName Mandatory Pattern ".*" CIM_DHCPServiceSettingData CIM_DHCPServiceSettingData indicates that the IP configuration should be obtained through the DHCP server if possible. Table 10 contains the requirements for elements of this class. Table 10 Class: CIM_DHCPServiceSettingData Element Name Requirement Description InstanceID Mandatory Key AddressOrigin Mandatory This property shall have a value of 4 ( DHCP ) or 7 ( DHCPv6 ). ElementName Mandatory Pattern ".*" ProtocolIFType Mandatory This property shall have a value of 4096 (IPv4) or 4097 (IPv6). DomainType Mandatory This property shall have a value of 1 (IPv4/ IN-ADDR.ARPA) or 2 (IPv6/IP6.ARPA). IPv6OptionsSupported Optional This property shall be set to IPv4/ IN- ADDR.ARPA (for DomainType 1) or IPv6/IP6.ARPA (for DomainType 2) LocalAddressAllocationServer Mandatory This property sets the Address Allocation Server (AAS) to run on the same DHCP server 22 Work In Progress Version 1.0.0a

23 DSP1068 Element Name Requirement Description RemoteAddressAllocationServer Optional If set, this property requires IP address of the remote AAS server in addition to the credential for DHCP server including requirements for authentication to the AAS server. IPv4AddressRangePool Mandatory This property allows setting up of a pool consist of a range of IPv4 addresses. A range is specified by two addresses separated by only a dash (RFC1918). InitialLeasTime Optional This property allows defining the initial lease reservation time in seconds. The default value is 180 seconds. InitialLeaseReservationTime Mandatory This property allows defining the time in minutes for which an address is reserved while the server offers it to a client. The lease begins when the client accepts the address. This reservation period prevents an address from being offered to more than one client at the same time. The default value is 10 minutes DefaultLeaseTime Mandatory This property allows defining the default lease period in days for the subnet. A value of infinite means that there is no limit. MaximumLeaseTime Mandatory This property allows defining the maximum lease period in days for the subnet. A value of infinite means that there is no limit LeaseRenewalTime Mandatory This property allows defining the lease renewal time in units of 0.1%. For example, a value of 500 indicates that the lease should be renewed after 50% of its lease had expired. LeaseRebindTime Optional This property allows defining the rebind time in units of 0.1%. Option values for a subnet can be assigned within the scope of the subnet definition. LeaseTimePadding Optional This property allows defining the lease padding. This is the amount of extra time the server allocates above the client lease time. It is defined in units of 0.1% of the client lease time. The default value of 10 adds 1% to the client lease time for the server lease time. The DHCP server knows the padded lease in order to preventing the server from assuming that the lease has expired before the client finds it out. ProbeAddress Optional This property allows defining whether an address that is about to be allocated should be tested using ping. By default, this is enabled. Version 1.0.0a Work In Progress 23

24 DSP1068 Element Name Requirement Description OptionOverload Mandatory This property allows defining whether option overloading is allowed. If its value is non-zero, it is allowed. By default it is not allowed CIM_RemoteServiceAccessPoint CIM_RemoteServiceAccessPoint represents the managed system s view of the DHCP server. Table 11 contains the requirements for elements of this class. Table 11 Class: CIM_RemoteServiceAccessPoint Element Name Requirement Description InstanceID Mandatory Key ElementName Mandatory Pattern ".*" ElementNameEditSupported Mandatory See 7.1 MaxElementNameLen Conditional See 7.3 OptionsSupported Mandatory None IPv6OptionsSupported Optional None 10.5 CIM_RegisteredProfile CIM_RegisteredProfile identifies the DHCP Server Profile in order for a server to determine whether an instance of CIM_IPProtocolEndpoint is conformant with this profile. The CIM_RegisteredProfile class is (DSP1068) defined by the Profile Registration Profile. With the exception of the mandatory values specified for the properties in Table 12, the behavior of the CIM_RegisteredProfile instance is in accordance with the Profile Registration Profile. Table 12 Class: CIM_RegisteredProfile Element Name Requirement Description RegisteredName Mandatory This property shall have a value of "DHCP Service Management Profile". RegisteredVersion Mandatory This property shall have a value of "1.0.0" RegisteredOrganization Mandatory This property shall have a value of "DMTF". 24 Work In Progress Version 1.0.0a

25 DSP ANNEX A (informative) Change log Version Date Description 1.0.0a DMTF Work in Progress 568 Version 1.0.0a Work In Progress 25

26 DSP Bibliography 26 Work In Progress Version 1.0.0a