DHCPv6 nested container statements

Nested container statements can only exist as an option inside subnet.

All containers can have other containers nested within it unless otherwise stated. The maximum depth of nesting is seven, including the subnet and the global container (only five nested containers can exist under a subnet container).

Vendor and Inoption containers cannot have any other containers nested within it.

Table 1. Keywords, values, and descriptions for entries in the nested container statements.
Keyword Value Description
class name [range] {OPTIONS|COMMON OPTIONS } Class container. The name value is one string, space separated strings, regular expression, hex 0xhexdigit, 0xhexdigit
vendor name [range] {OPTIONS|COMMON OPTIONS } Vendor container. The name value is one string, space separated strings, regular expression, hex 0xhexdigit, 0xhexdigit
client <id | 0 0xhexdigit | regular expression> <ip | range | none | any> {OPTIONA|COMMON OPTIONS } Client container.

id- 1-hexdigit, 2-hexdigit, 3-hexdigit <ip|range|none|any> - IP address to give to clients that match the ID

inoption icode keytomatch [range] { OPTIONS|COMMON OPTIONS } Inoption container

icode - incoming option code or number to be specified by the client

keytomatch - The option data to be matched against.