@todo Note: the current implementation doesn't allow configuration of the
server's behavior with respect to DNS Updates. This is planned for the future.
-The default behavioris constituted by the set of constants defined in the
+The default behavior is constituted by the set of constants defined in the
(upper part of) dhcp4_srv.cc file. Once the configuration is implemented,
these constants will be removed.
@page dhcpv4o6Dhcp4 DHCPv4-over-DHCPv6 DHCPv4 Server Side
Kea supports DHCPv4-over-DHCPv6 using cooperating DHCPv6 and DHCPv4
-servers. This section describes the DHCPv4 server side.
+servers. This section describes the DHCPv4 server side. For its
+DHCPv6 counter-part, see @ref dhcpv4o6Dhcp6.
@section Dhcp4to6Ipc DHCPv6-to-DHCPv4 Inter Process Communication
@page dhcpv4o6Dhcp6 DHCPv4-over-DHCPv6 DHCPv6 Server Side
Kea supports DHCPv4-over-DHCPv6 using cooperating DHCPv6 and DHCPv4
-servers. This section describes the DHCPv6 server side.
+servers. This section describes the DHCPv6 server side. For its
+DHCPv6 counter-part, see @ref dhcpv4o6Dhcp4.
@section dhcp6to4Ipc DHCPv6-to-DHCPv4 Inter Process Communication
/* RFC 7341 */
#define DHCPV6_DHCPV4_QUERY 20
#define DHCPV6_DHCPV4_RESPONSE 21
-/* draft-ietf-dhc-dhcpv6-active-leasequery-04 */
+/* RFC 7653 */
//#define DHCPV6_ACTIVELEASEQUERY 22
//#define DHCPV6_STARTTLS 23
\ref isc::dhcp::Dhcp4o6IpcBase::send adds them,
\ref isc::dhcp::Dhcp4o6IpcBase::receive decodes and removes them.
+Also see \ref dhcpv4o6Dhcp4 and \ref dhcpv4o6Dhcp6 for details on how IPC
+is used by DHCPv4 and DHCPv6 components.
+
@todo
DHCPv4-over-DHCPv6 which are relayed by a DHCPv6 relay are not yet supported.