7388 Support DHCP Client FQDN. Allow IAID/DUID for all v4.

*** 20,29 ****
--- 20,30 ----
  #
  
  #
  # Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
  # Use is subject to license terms.
+ # Copyright (c) 2016, Chris Fraire <cfraire@me.com>.
  #
  
  #
  # This file contains tunable parameters for dhcpagent(1M).
  #
*** 88,107 ****
  # digits (for example, the value 0xAABBCC11 would set the client
  # identifier to the 4-byte binary sequence 0xAA 0xBB 0xCC 0x11).
  #
  # CLIENT_ID=
  
  # By default, the DHCP agent will try to request the hostname currently
  # associated with the interface performing DHCP.  If this option is
! # enabled, the agent will attempt to find a host name in /etc/hostname.<if>,
! # which must contain a line of the form
  #
  #       inet name
  #
! # where "name" is a single RFC 1101-compliant token.  If found, the token
! # will be used to request that host name from the DHCP server.  To prevent
! # this, uncomment the following line.
  #
  # REQUEST_HOSTNAME=no
  
  # By default, a parameter request list requesting a subnet mask (1),
  # router (3), DNS server (6), hostname (12), DNS domain (15), broadcast
--- 89,147 ----
  # digits (for example, the value 0xAABBCC11 would set the client
  # identifier to the 4-byte binary sequence 0xAA 0xBB 0xCC 0x11).
  #
  # CLIENT_ID=
  
+ # By default, for an IPv4 interface that is not in an IP network
+ # multipathing (IPMP) group, that is not IP over InfiniBand (IPoIB), and
+ # that is not a logical interface, the DHCP agent will forgo sending a
+ # client identifier unless CLIENT_ID is defined.
+ #
+ # To use a system-managed, RFC 3315-style (i.e., DHCPv6-style) binding
+ # identifier as documented in RFC 4361, "Node-specific Client Identifiers
+ # for DHCPv4," for all IPv4 interfaces (unless CLIENT_ID is defined),
+ # uncomment the following line.
+ #
+ # V4_DEFAULT_IAID_DUID=yes
+ 
+ # By default, the DHCP agent will try to request the Fully Qualified Domain
+ # Name (FQDN) currently associated with the interface performing DHCP.  The
+ # hostname is defined by using the -h,--reqhost option of ipadm(1M) or the
+ # ncu ip-reqhost property of nwamcfg(1M) or by flagging the interface as
+ # primary so that nodename(4) is used as the hostname.
+ #
+ # A defined hostname will be used as the FQDN if it is "rooted" (i.e., if
+ # it ends with a '.') or if it consists of at least three DNS labels (e.g.,
+ # srv.example.com).  If the hostname is not an FQDN, then either a defined
+ # defaultdomain(4) or a defined resolv.conf(4) domain will be appended to
+ # form an FQDN.  If no FQDN can be determined, the option will not be used.
+ #
+ # If this REQUEST_FQDN option is enabled, an FQDN will be sent in messages
+ # to the DHCP server along with RFC 4702 options to request that a
+ # collaborating DNS server perform DNS updates for A and PTR resource
+ # records.  To prevent sending FQDN and DNS options, uncomment the line
+ # below.
+ #
+ # If an FQDN is sent, REQUEST_HOSTNAME processing will not be done, per RFC
+ # 4702 (3.1):  "clients that send the Client FQDN option in their messages
+ # MUST NOT also send the Host Name."
+ #
+ # REQUEST_FQDN=no
+ 
  # By default, the DHCP agent will try to request the hostname currently
  # associated with the interface performing DHCP.  If this option is
! # enabled, the agent will attempt to use an -h,--reqhost option saved with
! # ipadm(1M) or an ncu ip-reqhost property set with nwamcfg(1M); or else
! # attempt to find a host name in /etc/hostname.<if>, which must contain a
! # line of the form
  #
  #       inet name
  #
! # where "name" is a single RFC 1101-compliant token; or else use
! # nodename(4) for a DHCP interface flagged as primary.  If found in any of
! # these configurations, the token will be used to request that host name
! # from the DHCP server.  To prevent this, uncomment the following line.
  #
  # REQUEST_HOSTNAME=no
  
  # By default, a parameter request list requesting a subnet mask (1),
  # router (3), DNS server (6), hostname (12), DNS domain (15), broadcast