Lines Matching refs:design
26 ** This document discusses aspects of the DHCPv4 client design that have
28 ** aspects affected the DHCPv6 design, the discussion has been left for
65 the chosen design, are discussed in Appendix A.
67 This document discusses the internal design issues involved in the
80 In order to discuss the design changes for DHCPv6, it's necessary
81 first to talk about the current IPv4-only design, and the
82 assumptions built into that design.
119 The design is single-threaded, so code that walks the global list
248 current design simply replicates the state (notably the DLPI stream,
252 The new design creates two lists of dhcp_pif_t entries, one list for
307 system configuration example as in the initial design discussion:
407 existing design.
457 if_sock_ip_fd in the existing design, but that existing socket is
474 to find the correct transaction ID, but the existing design
595 design.
629 messages. The DHCPv6 method is a cleaner design, so we will change
752 Such a design also begs the question of whether dhcpagent itself
1056 and these issues directed some of the design. In particular:
1085 design may need to be revisited. (The solution will likely be
1118 libdhcputil design, require a new 'type' of entry for the inittab6
1119 file. This is because the design does not allow for any simple