3.1.5.1 Receiving a DHCPOFFER

If the DHCPOFFER contains any of the options defined in this specification, these options SHOULD be ignored; the client MAY<27> instead use the options to choose among offers in any implementation-specific manner.

When sending a DHCPREQUEST in response, the DHCPv4 client SHOULD<28> include a Vendor Class Identifier Option formatted as in section 2.2.3 and MAY<29> include a User Class Option formatted as in section 2.2.6. Because this specification supports only one user class value in this packet, the client MUST conform to the guidelines for the User Class Data defined in section 2.2.6. The DHCPv4 client SHOULD<30> include both options 121 and 249 in the parameter request list in this message.