3.1.5.2 Receiving a DHCPACK

  • Article

When a DHCPv4 client implementing this specification receives a DHCPACK that contains a Vendor-Specific Information Option, it MUST be processed as follows.

If it contains a Microsoft Disable NetBIOS Option, the DHCPv4 client MUST update its NetBIOS Enabled Flag for the interface over which the DHCPACK was received, as specified in section 2.2.2.1.

If it contains a Microsoft Release DHCP Lease on Shutdown Option, the DHCPv4 client MUST update its Release DHCP Lease on Shutdown Flag for the interface over which the DHCPACK was received, as specified in section 2.2.2.2.

If it contains a Microsoft Default Router Metric Base Option specified in section 2.2.2.3, the value for this option from the DHCPACK message MUST be applied by the client for the default routes on that interface.

If it contains one or more User Class Options (77), the client MUST first check whether each option conforms to the syntax specified in section 2.2.6. If the option does not conform to the syntax, the DHCPv4 client MUST silently discard the complete DHCPv4 message and start the initialization process again. Otherwise, the client uses the information in an implementation-specific manner.

If it contains a Microsoft Classless Static Route Option (249), the client MUST first check whether the option conforms to the syntax specified in section 2.2.8. If any of the parameters in this DHCPv4 option are invalid or incomplete, the DHCPv4 client MUST silently discard the complete DHCPv4 message and start the initialization process again. Otherwise, if the DHCPACK does not contain a Classless Static Route Option (121), the specified routes MUST be inserted into the routing table in the TCP/IP stack. If it contains both a Microsoft Classless Static Route Option (249) and a Classless Static Route Option (121) then the client MUST select either set of routes (in any implementation-specific way<31>) as the routes to be added into the routing table in the TCP/IP stack.

If it contains an ANDROID_METERED Option specified in section 2.2.2.6, the client SHOULD<32> mark the interface as a metered interface in an implementation-specific manner.