DHCP Server Configuration Schema A generic policy type, which is simply a name-value pair. Policies are used to configure implementation-specific behavior within the DHCP server. The configuration options are options that have registered codes with IANA and are defined by RFC's. This list includes only those options that can be configured for the DHCPv4 server to provide to clients. Other options, that is options sent from the client to the server, are defined below for use in forming client filter expressions. The configuration options are options that have registered codes with IANA and are defined by RFC's. This list includes only those options that can be configured for the DHCPv6 server to provide to clients. Other options, that is options sent from the client to the server, are defined below for use in forming client filter expressions. A filter is used to define configuration parameters for specific classes of clients. The optionExpressions can be used to define the filter by matching one or more options from the received message. A link filter is simply a filter which allows for pools. It is distinguished from a standard filter which can be at the global or pool level, and therefore can't have pools. A link is used to define configuration parameters for client on a specific link. The link is determined by the server according to section 11 of RFC 3315. If the message is received directly and the source address is link-local, then the client is on the link attached to the server interface which received the message. If the message is received directly and the source address is not link-local, then the client is on the link identified by the source address. If the message is received from a relay agent, then the client is on the link identified by the link-address of the Relay-Forward message. Opaque data can be specified as either ASCII text, as binary data using hex characters for each byte, or as sub-options using the genericOptionsType. Operators available for forming optionExpressions for use in filterExpressions. A filterExpression is formed from one or more optionExpressions or customExpressions which are logically ANDed together to form the match. A clientClassExpression is the combination of a user/vendor class option that may be provided by a client and an operator for forming the match. An optionExpression is the combination of a generic option and an operator for forming the match.