Share via

3.2.5.2 Receiving a DHCPREQUEST Message

  • Article

Evaluate and apply administrative controls as described in section 1.4, point 6.<36>

Increment the DHCPv4ServerMibInfo.Requests element, a shared ADM element (see [MS-DHCPM] section 3.1.1.1), as described in section 1.4, point 10.

If the DHCPREQUEST message contains a Vendor Class Identifier Option (section 2.2.3) with a value defined in section 2.2.3, the following points illustrate the behavior of the DHCPv4 server:

  • The DHCPv4 server MUST include the vendor-specific options defined in section 2.2.2 (if configured to do so by the administrator) in the DHCPACK message sent to the clients.

  • The DHCPv4 server MUST interpret the User Class Option if it exists<37> in the DHCPREQUEST message to contain a single value as defined in section 2.2.6.

When the DHCPv4 server receives a request for Option 249 but not for Option 121 in the Parameter Request List, the Classless Static Route information MUST be returned to the DHCPv4 client in Option 249. If the Parameter Request List contains a request for both Options 121 and 249, the Classless Static Route information SHOULD<38> be returned to the DHCPv4 client in Option 121 only.

The DHCPv4 server MUST format any option values that are longer than 255 bytes, as defined in section 2.2.9.

If processing of the DHCPREQUEST message results in the server sending a DHCPACK message to the client, then increment the DHCPv4ServerMibInfo.Acks element, a shared ADM element (see [MS-DHCPM] section 3.1.1.1), as described in section 1.4, point 10.

If processing of the DHCPREQUEST message results in the server sending a DHCPNACK message to the client, then increment the DHCPv4ServerMibInfo.Nacks element, a shared ADM element (see [MS-DHCPM] section 3.1.1.1), as described in section 1.4, point 10.

The remainder of the DHCPREQUEST message MUST be processed as specified by [RFC2131] and [RFC2132].

If the DHCPREQUEST contains a Client Identifier Option (Option 61) with the field Client-Identifier containing the first four bytes as "RAS ", the DHCPv4 server MUST ignore any FQDN Option (Option 81) in the DHCPv4 message and MUST NOT perform DNS registration of A and PTR records on behalf of the DHCPv4 client. For more information, see [RFC4702].