3.2.1 Abstract Data Model

This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document.

These DHCP extensions comply with the data store (as defined in [RFC2131] section 2.1). The state machine and data model for DHCPv4 are defined in [RFC2131] section 4.4. The data model for DHCPv6 is similar and is defined by [RFC3315]. The extensions defined in this specification do not require any change to the state machine or the data model of DHCPv4 or DHCPv6.

This protocol includes the following ADM elements, which are directly accessed from [MS-DHCPM] as specified in [MS-DHCPM] section 3.1.1:

  • DHCPv4ClassDef

  • DHCPv4Client

  • DHCPv4ExclusionRange

  • DHCPv4Filter

  • DHCPv4FiltersList

  • DHCPv4FilterStatus

  • DHCPv4IpRange

  • DHCPv4OptionValue

  • DHCPv4Reservation

  • DHCPv4ResvOptValuesList

  • DHCPv4Scope

  • DHCPv4ServerAttributes

  • DHCPv4ServerMibInfo

  • DHCPv4ServerOptValueList

  • DHCPv4SuperScope

  • DHCPv6ClassDef

  • DHCPv6ClientInfo

  • DHCPv6ExclusionRange

  • DHCPv6OptionValue

  • DHCPv6Reservation

  • DHCPv6ResvClassedOptValueList

  • DHCPv6Scope

  • DHCPv6ScopeClassedOptValueList

  • DHCPv6ServerClassedOptValueList

  • DHCPv6ServerMibInfo

  • DHCPv6UserClass