diff --git a/ChangeLog b/ChangeLog
index 264a3d164d2639712e58943ebf2dec8fda10d006..09d22fc13af2a1472bad9090ba38a2938dcbf1a9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+1584.	[doc]		marcin
+	Documented Kea Configuration Backend in the Kea Administrator
+	Reference Manual.
+	(Gitlab #71,!314, git 3a65b7a9104f2a988dacf1acc26312b4259e958d)
+
 1583.	[bug]		fdupont, marcin
 	Corrected a bug which caused failures to merge a subnet from the
 	Configuration Backend into the DHCP server's configuration
diff --git a/doc/Makefile.am b/doc/Makefile.am
index 18aaeaf90de137d41512cf465167d5f582bd654e..8c98c82405b0f5ae35903e37ee0d55d23c3e26a7 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -26,6 +26,7 @@ nobase_dist_doc_DATA += examples/kea4/cassandra.json
 nobase_dist_doc_DATA += examples/kea4/classify.json
 nobase_dist_doc_DATA += examples/kea4/classify2.json
 nobase_dist_doc_DATA += examples/kea4/comments.json
+nobase_dist_doc_DATA += examples/kea4/config-backend.json
 nobase_dist_doc_DATA += examples/kea4/dhcpv4-over-dhcpv6.json
 nobase_dist_doc_DATA += examples/kea4/global-reservations.json
 nobase_dist_doc_DATA += examples/kea4/ha-load-balancing-primary.json
@@ -48,6 +49,7 @@ nobase_dist_doc_DATA += examples/kea6/cassandra.json
 nobase_dist_doc_DATA += examples/kea6/classify.json
 nobase_dist_doc_DATA += examples/kea6/classify2.json
 nobase_dist_doc_DATA += examples/kea6/comments.json
+nobase_dist_doc_DATA += examples/kea6/config-backend.json
 nobase_dist_doc_DATA += examples/kea6/dhcpv4-over-dhcpv6.json
 nobase_dist_doc_DATA += examples/kea6/duid.json
 nobase_dist_doc_DATA += examples/kea6/global-reservations.json
diff --git a/doc/api/remote-global-parameter4-del.json b/doc/api/remote-global-parameter4-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..43cd91544d81f8a28ca6b395649f5d262031a40b
--- /dev/null
+++ b/doc/api/remote-global-parameter4-del.json
@@ -0,0 +1,24 @@
+{
+    "name": "remote-global-parameter4-del",
+    "brief": "This command is used to delete a global DHCPv4 parameter from the configuration database. The server will use the value specified in the configuration file or a default value (if the parameter is not specified in the configuration file) after deleting the parameter from the database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter4-del\",
+    \"arguments\": {
+        \"parameters\": [ <parameter name> ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command carries the list including exactly one name of the parameter to be deleted.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 global parameter(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-global-parameter4-get-all.json b/doc/api/remote-global-parameter4-get-all.json
new file mode 100644
index 0000000000000000000000000000000000000000..9e6e511a18789fb7aa88f343a8cd3b320482d8cb
--- /dev/null
+++ b/doc/api/remote-global-parameter4-get-all.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-global-parameter4-get-all",
+    "brief": "This command is used to fetch all global parameters for the server from the specified database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter4-get-all\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command contains no arguments besides the optional <command>remote</command>.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 global parameters found.\",
+    \"arguments\": {
+        \"parameters\": [
+            {
+                <first parameter name>: <first parameter value>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                <second parameter name>: <second parameter value>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is appended to each parameter and it provides database specific information associated with the returned objects."
+}
diff --git a/doc/api/remote-global-parameter4-get.json b/doc/api/remote-global-parameter4-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..be62d1910b685d0eb04d2c95fc26f320451e43c1
--- /dev/null
+++ b/doc/api/remote-global-parameter4-get.json
@@ -0,0 +1,31 @@
+{
+    "name": "remote-global-parameter4-get",
+    "brief": "This command is used to fetch selected global parameter for the server from the specified database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter4-get\"
+    \"arguments\": {
+        \"parameters\": [ <parameter name> ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command carries a list including exactly one name of the parameter to be fetched.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 global parameter found.\",
+    \"arguments\": {
+        \"parameters\": {
+            <parameter name>: <parameter value>,
+            \"metadata\": {
+                \"server-tag\": <server tag>
+            }
+        },
+        \"count\": 1
+    }
+}",
+    "resp-comment": "The returned response contains a map with a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is included and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-global-parameter4-set.json b/doc/api/remote-global-parameter4-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..622ca47e324a4517cca3114f7c36ab80e96269af
--- /dev/null
+++ b/doc/api/remote-global-parameter4-set.json
@@ -0,0 +1,24 @@
+{
+    "name": "remote-global-parameter4-set",
+    "brief": "This command is used to create or update one more global parameters in the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter4-set\"
+    \"arguments\": {
+        \"parameters\": {
+            <first parameter name>: <first parameter value>,
+            <second parameter name>: <second parameter value>
+        },
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command carries multiple global parameters with their values. Care should be taken when specifying more than one parameter because in some cases only a subset of the parameters may be successfully stored in the database and other parameters may fail to be stored. In such cases the <command>remote-global-parameter4-get-all</command> may be useful to verify the contents of the database after the update.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 global parameter(s) successfully set.\"
+}"
+}
diff --git a/doc/api/remote-global-parameter6-del.json b/doc/api/remote-global-parameter6-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..faba037271813694e658fc32da0916eaa90df03c
--- /dev/null
+++ b/doc/api/remote-global-parameter6-del.json
@@ -0,0 +1,23 @@
+{
+    "name": "remote-global-parameter6-del",
+    "brief": "This command is used to delete a global DHCPv6 parameter from the configuration database. The server will use the value specified in the configuration file or a default value (if the parameter is not specified in the configuration file) after deleting the parameter from the database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter6-del\",
+    \"arguments\": {
+        \"parameters\": [ <parameter name> ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command carries the list including exactly one name of the parameter to be deleted.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 global parameter(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }"
+}
diff --git a/doc/api/remote-global-parameter6-get-all.json b/doc/api/remote-global-parameter6-get-all.json
new file mode 100644
index 0000000000000000000000000000000000000000..667c7c8f24fd79a60e4c785f8edef03328dce115
--- /dev/null
+++ b/doc/api/remote-global-parameter6-get-all.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-global-parameter6-get-all",
+    "brief": "This command is used to fetch all global parameters for the server from the specified database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter6-get-all\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command contains no arguments besides the optional <command>remote</command>.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 global parameters found.\",
+    \"arguments\": {
+        \"parameters\": [
+            {
+                <first parameter name>: <first parameter value>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                <second parameter name>: <second parameter value>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is appended to each parameter and it provides database specific information associated with the returned objects."
+}
diff --git a/doc/api/remote-global-parameter6-get.json b/doc/api/remote-global-parameter6-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..fb94e973e94fe5fef08ffe9485d96ea878fd5e10
--- /dev/null
+++ b/doc/api/remote-global-parameter6-get.json
@@ -0,0 +1,31 @@
+{
+    "name": "remote-global-parameter6-get",
+    "brief": "This command is used to fetch selected global parameter for the server from the specified database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter6-get\"
+    \"arguments\": {
+        \"parameters\": [ <parameter name> ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command carries a list including exactly one name of the parameter to be fetched.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 global parameter found.\",
+    \"arguments\": {
+        \"parameters\": {
+            <parameter name>: <parameter value>,
+            \"metadata\": {
+                \"server-tag\": <server tag>
+            }
+        },
+        \"count\": 1
+    }
+}",
+    "resp-comment": "The returned response contains a map with a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is included and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-global-parameter6-set.json b/doc/api/remote-global-parameter6-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..0ad6d4bf3a91804641076cf3a8698caca420c75d
--- /dev/null
+++ b/doc/api/remote-global-parameter6-set.json
@@ -0,0 +1,24 @@
+{
+    "name": "remote-global-parameter6-set",
+    "brief": "This command is used to create or update one more global DHCP parameters in the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-global-parameter6-set\"
+    \"arguments\": {
+        \"parameters\": {
+            <first parameter name>: <first parameter value>,
+            <second parameter name>: <second parameter value>
+        },
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command carries multiple global parameters with their values. Care should be taken when specifying more than one parameter because in some cases only a subset of the parameters may be successfully stored in the database and other parameters may fail to be stored. In such cases the <command>remote-global-parameter6-get-all</command> may be useful to verify the contents of the database after the update.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 global parameter(s) successfully set.\"
+}"
+}
diff --git a/doc/api/remote-network4-del.json b/doc/api/remote-network4-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..d72b748e080314bf8bf3c5ed8609e3db023b82cf
--- /dev/null
+++ b/doc/api/remote-network4-del.json
@@ -0,0 +1,29 @@
+{
+    "name": "remote-network4-del",
+    "brief": "This command is used to delete an IPv4 shared network from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network4-del\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <shared network name>
+            }
+        ],
+        \"subnets-action\": \"keep\" | \"delete\",
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one name of the shared network to be deleted. The <command>subnets-action</command> denotes whether the subnets in this shared network should be deleted or not.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 IPv4 shared network(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-network4-get.json b/doc/api/remote-network4-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..b48ee7a7861691916a5403348b45d7fd753296b5
--- /dev/null
+++ b/doc/api/remote-network4-get.json
@@ -0,0 +1,39 @@
+{
+    "name": "remote-network4-get",
+    "brief": "This command is used to fetch selected IPv4 shared network for the server from the specified database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network4-get\"
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <shared network name>
+            }
+        ],
+        \"subnets-include\": \"full\" | \"no\",
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one name of the shared network to be returned. The <command>subnets-include</command> optional parameter allows for specifying whether the subnets belonging to the shared network should also be returned.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv4 shared network found.\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <shared network name>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                },
+                <the rest of the shared network information, potentially including subnets>
+            }
+        ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "If the subnets are returned with the shared network they are carried in the <command>subnet4</command> list within the shared network definition. The metadata is included in the returned shared network definition and it provides the database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-network4-list.json b/doc/api/remote-network4-list.json
new file mode 100644
index 0000000000000000000000000000000000000000..e69b5722b7c6246c7eaceb30f75b7e37d61f29ab
--- /dev/null
+++ b/doc/api/remote-network4-list.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-network4-list",
+    "brief": "This command is used to fetch a list of all IPv4 shared networks from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network4-list\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command contains no arguments besides the optional <command>remote</command>.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 IPv4 shared network(s) found.\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <first shared network name>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                \"name\": <second shared network name>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains the list of maps. Each map contains the shared network name and the metadata which provides database specific information associated with the shared network. The returned list does not contain full definitions of the shared networks. Use <command>remote-network4-get</command> to fetch the full information about the selected shared networks."
+}
diff --git a/doc/api/remote-network4-set.json b/doc/api/remote-network4-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..435d3e382ae937b338c9144b3a0bd4f7e9d69bd7
--- /dev/null
+++ b/doc/api/remote-network4-set.json
@@ -0,0 +1,25 @@
+{
+    "name": "remote-network4-set",
+    "brief": "This command is used to create or replace an IPv4 shared network in the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network4-set\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                <shared network specification excluding subnets list>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must contain exactly one shared network specification. It must not contain subnets (\"subnet4\" parameter). The subnets are added to the shared network using <command>remote-subnet4-set</command> command.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv4 shared network successfully set.\"
+}"
+}
diff --git a/doc/api/remote-network6-del.json b/doc/api/remote-network6-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..570a132097805c07447832793f4095ca655c350a
--- /dev/null
+++ b/doc/api/remote-network6-del.json
@@ -0,0 +1,29 @@
+{
+    "name": "remote-network6-del",
+    "brief": "This command is used to delete an IPv6 shared network from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network6-del\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <shared network name>
+            }
+        ],
+        \"subnets-action\": \"keep\" | \"delete\",
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one name of the shared network to be deleted. The <command>subnets-action</command> denotes whether the subnets in this shared network should be deleted or not.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 IPv6 shared network(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-network6-get.json b/doc/api/remote-network6-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..11ddab120377c7d76a8cf30ba61014a32ac1d292
--- /dev/null
+++ b/doc/api/remote-network6-get.json
@@ -0,0 +1,39 @@
+{
+    "name": "remote-network6-get",
+    "brief": "This command is used to fetch selected IPv6 shared network for the server from the specified database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network6-get\"
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <shared network name>
+            }
+        ],
+        \"subnets-include\": \"full\" | \"no\",
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one name of the shared network to be returned. The <command>subnets-include</command> optional parameter allows for specifying whether the subnets belonging to the shared network should also be returned.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv6 shared network found.\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <shared network name>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                },
+                <the rest of the shared network information, potentially including subnets>
+            }
+        ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "If the subnets are returned with the shared network they are carried in the <command>subnet6</command> list within the shared network definition. The metadata is included in the returned shared network definition and it provides the database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-network6-list.json b/doc/api/remote-network6-list.json
new file mode 100644
index 0000000000000000000000000000000000000000..9fb1e0edcdce0d2d05e098328fae83431501a34b
--- /dev/null
+++ b/doc/api/remote-network6-list.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-network6-list",
+    "brief": "This command is used to fetch a list of all IPv6 shared networks from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network6-list\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command contains no arguments besides the optional <command>remote</command>.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 IPv6 shared network(s) found.\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                \"name\": <first shared network name>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                \"name\": <second shared network name>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains the list of maps. Each map contains the shared network name and the metadata which provides database specific information associated with the shared network. The returned list does not contain full definitions of the shared networks. Use <command>remote-network6-get</command> to fetch the full information about the selected shared networks."
+}
diff --git a/doc/api/remote-network6-set.json b/doc/api/remote-network6-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..1ed48e25a2ca371b591b6258fa4a70ced9db9d68
--- /dev/null
+++ b/doc/api/remote-network6-set.json
@@ -0,0 +1,25 @@
+{
+    "name": "remote-network6-set",
+    "brief": "This command is used to create or replace an IPv6 shared network in the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-network6-set\",
+    \"arguments\": {
+        \"shared-networks\": [
+            {
+                <shared network specification excluding subnets list>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must contain exactly one shared network specification. It must not contain subnets (\"subnet6\" parameter). The subnets are added to the shared network using <command>remote-subnet6-set</command> command.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv6 shared network successfully set.\"
+}"
+}
diff --git a/doc/api/remote-option-def4-del.json b/doc/api/remote-option-def4-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..0eeee2cf5db224047cbcb7237c179a0f3636714f
--- /dev/null
+++ b/doc/api/remote-option-def4-del.json
@@ -0,0 +1,27 @@
+{
+    "name": "remote-option-def4-del",
+    "brief": "This command is used to delete a DHCPv4 option definition from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def4-del\",
+    \"arguments\": {
+        \"option-defs\": [ {
+            \"code\": <option code>,
+            \"space\": <option space
+        } ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one option definition specification comprising an option name and code.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 DHCPv4 option definition(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-option-def4-get-all.json b/doc/api/remote-option-def4-get-all.json
new file mode 100644
index 0000000000000000000000000000000000000000..f921204d45596a063a51652c8e3dd7d47df092eb
--- /dev/null
+++ b/doc/api/remote-option-def4-get-all.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-option-def4-get-all",
+    "brief": "This command is used to fetch all DHCPv4 option definitions from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def4-get-all\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command contains no arguments besides the optional <command>remote</command>.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 DHCPv4 option definition(s) found.\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                <first option definition>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                <second option definition>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains an option definition specification and the metadata including database specific information associated with the returned objects."
+}
diff --git a/doc/api/remote-option-def4-get.json b/doc/api/remote-option-def4-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..0e625a1d84afaf365baf88d10c0571993e148f6a
--- /dev/null
+++ b/doc/api/remote-option-def4-get.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-option-def4-get",
+    "brief": "This command is used to fetch a DHCPv4 option definition from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def4-get\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                \"code\": <option code>,
+                \"space\": <option space>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The desired option definition is identified by the pair of the option code/space values.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 option definition found.\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                <option definition>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "The metadata is included and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-option-def4-set.json b/doc/api/remote-option-def4-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..56041ef813b11a28f586a6eb23ac24d00a15364b
--- /dev/null
+++ b/doc/api/remote-option-def4-set.json
@@ -0,0 +1,25 @@
+{
+    "name": "remote-option-def4-set",
+    "brief": "This command is used to create or replace DHCPv4 option definition in the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def4-set\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                <option definition specification>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must contain exactly one option definition specification.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 option definition set.\"
+}"
+}
diff --git a/doc/api/remote-option-def6-del.json b/doc/api/remote-option-def6-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..daa16c3747110bfe7d1281568504b574ca65e6c0
--- /dev/null
+++ b/doc/api/remote-option-def6-del.json
@@ -0,0 +1,29 @@
+{
+    "name": "remote-option-def6-del",
+    "brief": "This command is used to delete a DHCPv6 option definition from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def6-del\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                \"code\": <option code>,
+                \"space\": <option space
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one option definition specification comprising an option name and code.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 DHCPv6 option definition(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-option-def6-get-all.json b/doc/api/remote-option-def6-get-all.json
new file mode 100644
index 0000000000000000000000000000000000000000..a212876e2d9b06dbf9e507323d944a4fd9e6315e
--- /dev/null
+++ b/doc/api/remote-option-def6-get-all.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-option-def6-get-all",
+    "brief": "This command is used to fetch all DHCPv6 option definitions from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def6-get-all\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command contains no arguments besides the optional <command>remote</command>.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 DHCPv6 option definition(s) found.\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                <first option definition>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                <second option definition>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains an option definition specification and the metadata including database specific information associated with the returned objects."
+}
diff --git a/doc/api/remote-option-def6-get.json b/doc/api/remote-option-def6-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..f9b1500cd877f066d7336f942581f9900db09227
--- /dev/null
+++ b/doc/api/remote-option-def6-get.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-option-def6-get",
+    "brief": "This command is used to fetch a DHCPv6 option definition from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def6-get\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                \"code\": <option code>,
+                \"space\": <option space>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The desired option definition is identified by the pair of the option code/space values.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 option definition found.\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                <option definition>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "The metadata is included and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-option-def6-set.json b/doc/api/remote-option-def6-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..0fb748edc49cc674e1944c09ee8570c0bea52f25
--- /dev/null
+++ b/doc/api/remote-option-def6-set.json
@@ -0,0 +1,25 @@
+{
+    "name": "remote-option-def6-set",
+    "brief": "This command is used to create or replace DHCPv6 option definition in the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option-def6-set\",
+    \"arguments\": {
+        \"option-defs\": [
+            {
+                <option definition specification>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must contain exactly one option definition specification.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 option definition set.\"
+}"
+}
diff --git a/doc/api/remote-option4-global-del.json b/doc/api/remote-option4-global-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..9be9ad2d86c6375063d9bab1568bf9fda621a434
--- /dev/null
+++ b/doc/api/remote-option4-global-del.json
@@ -0,0 +1,29 @@
+{
+    "name": "remote-option4-global-del",
+    "brief": "This command is used to delete a DHCPv4 global option from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option4-global-del\",
+    \"arguments\": {
+        \"options\": [
+            {
+                \"code\": <option code>
+                \"space\": <option space>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one option specification comprising an option name and code.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 DHCPv4 option(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-option4-global-get-all.json b/doc/api/remote-option4-global-get-all.json
new file mode 100644
index 0000000000000000000000000000000000000000..db75efd989c59c45da2d39b8f193e4ec3c44236c
--- /dev/null
+++ b/doc/api/remote-option4-global-get-all.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-option4-global-get-all",
+    "brief": "This command is used to fetch all DHCPv4 global options for the server from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option4-global-get-all\",
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command takes no arguments besides the optional <command>remote</command> map.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 DHCPv4 option(s) found.\",
+    \"arguments\": {
+        \"options\": [
+            {
+                <first option specification>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                <second option specification>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains a global option specification and the metadata including database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-option4-global-get.json b/doc/api/remote-option4-global-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..4ceedb693b656c28967b85f4dde2e9d6d0c62b56
--- /dev/null
+++ b/doc/api/remote-option4-global-get.json
@@ -0,0 +1,36 @@
+{
+    "name": "remote-option4-global-get",
+    "brief": "This command is used to fetch a global DHCPv4 option for the server from the specified database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option4-global-get\",
+    \"arguments\": {
+        \"options\": [
+            {
+                \"code\": <option code>,
+                \"space\": <option space>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+}",
+    "cmd-comment": "The option is identified by the pair of option code/space values.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 option in found.\",
+    \"arguments\": {
+        \"options\": [
+            {
+                <option information>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ]
+    }
+}",
+    "resp-comment": "The metadata is included and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-option4-global-set.json b/doc/api/remote-option4-global-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..072b0f702233a8c14be0c39886bb131a1fd6ee35
--- /dev/null
+++ b/doc/api/remote-option4-global-set.json
@@ -0,0 +1,33 @@
+{
+    "name": "remote-option4-global-set",
+    "brief": "This command is used to create or replace a DHCPv4 global option in the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option4-global-set\",
+    \"arguments\": {
+        \"options\": [
+            {
+                <global option specification>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must cotain exactly one option specification.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv4 option set.\",
+    \"arguments\": {
+        \"options\": [
+            {
+                \"code\": <option code>,
+                \"space\": <option space>
+            }
+        ]
+    }
+}"
+}
diff --git a/doc/api/remote-option6-global-del.json b/doc/api/remote-option6-global-del.json
new file mode 100644
index 0000000000000000000000000000000000000000..7786ccca6adb2f2840dcc502f8ba6f40f715621a
--- /dev/null
+++ b/doc/api/remote-option6-global-del.json
@@ -0,0 +1,29 @@
+{
+    "name": "remote-option6-global-del",
+    "brief": "This command is used to delete a DHCPv6 global option from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option6-global-del\",
+    \"arguments\": {
+        \"options\": [
+            {
+                \"code\": <option code>
+                \"space\": <option space>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one option specification comprising an option name and code.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 DHCPv6 option(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-option6-global-get-all.json b/doc/api/remote-option6-global-get-all.json
new file mode 100644
index 0000000000000000000000000000000000000000..9abd53968ee96ac6d7fc1578404e2515085999fa
--- /dev/null
+++ b/doc/api/remote-option6-global-get-all.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-option6-global-get-all",
+    "brief": "This command is used to fetch all DHCPv6 global options for the server from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option6-global-get-all\",
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command takes no arguments besides the optional <command>remote</command> map.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 DHCPv6 option(s) found.\",
+    \"arguments\": {
+        \"options\": [
+            {
+                <first option specification>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                <second option specification>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains a global option specification and the metadata including database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-option6-global-get.json b/doc/api/remote-option6-global-get.json
new file mode 100644
index 0000000000000000000000000000000000000000..b4ce7b625e099bd4b8cfbaf349018e290b4573aa
--- /dev/null
+++ b/doc/api/remote-option6-global-get.json
@@ -0,0 +1,36 @@
+{
+    "name": "remote-option6-global-get",
+    "brief": "This command is used to delete a DHCPv6 global option from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option6-global-get\",
+    \"arguments\": {
+        \"options\": [
+            {
+                \"code\": <option code>,
+                \"space\": <option space>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+}",
+    "cmd-comment": "The option is identified by the pair of option code/space values.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 option found.\",
+    \"arguments\": {
+        \"options\": [
+            {
+                <option information>,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ]
+    }
+}",
+    "resp-comment": "The metadata is included and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-option6-global-set.json b/doc/api/remote-option6-global-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..c13e51a454fc9e00dba0925c578ecb0fab9840cf
--- /dev/null
+++ b/doc/api/remote-option6-global-set.json
@@ -0,0 +1,33 @@
+{
+    "name": "remote-option6-global-set",
+    "brief": "This command is used to create or replace a DHCPv6 global option in the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-option6-global-set\",
+    \"arguments\": {
+        \"options\": [
+            {
+                <global option specification>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must cotain exactly one option specification.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"DHCPv6 option set.\",
+    \"arguments\": {
+        \"options\": [
+            {
+                \"code\": <option code>,
+                \"space\": <option space>
+            }
+        ]
+    }
+}"
+}
diff --git a/doc/api/remote-subnet4-del-by-id.json b/doc/api/remote-subnet4-del-by-id.json
new file mode 100644
index 0000000000000000000000000000000000000000..15c0985f8328e6c8c7038985ae49ed0a94116fbc
--- /dev/null
+++ b/doc/api/remote-subnet4-del-by-id.json
@@ -0,0 +1,28 @@
+{
+    "name": "remote-subnet4-del-by-id",
+    "brief": "This command is used to delete an IPv4 subnet by ID from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet4-del-by-id\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <subnet identifier>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one id of the subnet to be deleted.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 IPv4 subnet(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-subnet4-del-by-prefix.json b/doc/api/remote-subnet4-del-by-prefix.json
new file mode 100644
index 0000000000000000000000000000000000000000..9ba462c1c2838c83b8a139df5ad1b80ee9085afc
--- /dev/null
+++ b/doc/api/remote-subnet4-del-by-prefix.json
@@ -0,0 +1,28 @@
+{
+    "name": "remote-subnet4-del-by-prefix",
+    "brief": "This command is used to delete an IPv4 subnet by prefix from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet4-del-by-prefix\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"subnet\": <subnet prefix>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one prefix of the subnet to be deleted.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 IPv4 subnet(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-subnet4-get-by-id.json b/doc/api/remote-subnet4-get-by-id.json
new file mode 100644
index 0000000000000000000000000000000000000000..4fbe9d0b24c61a952dfcef7aa0bef912619ba190
--- /dev/null
+++ b/doc/api/remote-subnet4-get-by-id.json
@@ -0,0 +1,36 @@
+{
+    "name": "remote-subnet4-get-by-id",
+    "brief": "This command is used to fetch selected IPv4 subnet by ID for the server from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet4-get-by-id\"
+    \"arguments\": {
+        \"subnets\": [ {
+            \"id\": <subnet identifier>
+        } ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one id of the subnet to be returned.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv4 subnet found.\",
+    \"arguments\": {
+        \"subnets\": [ {
+            \"id\": <subnet identifier>
+            \"subnet\": <subnet prefix>,
+            \"shared-network-name\": <shared network name> | null,
+            \"metadata\": {
+                \"server-tag\": <server tag>
+            },
+            <the rest of the subnet specification here>
+        } ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-subnet4-get-by-prefix.json b/doc/api/remote-subnet4-get-by-prefix.json
new file mode 100644
index 0000000000000000000000000000000000000000..2790245346f2ec823484cdda0452f3e01c857e0e
--- /dev/null
+++ b/doc/api/remote-subnet4-get-by-prefix.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-subnet4-get-by-prefix",
+    "brief": "This command is used to fetch selected IPv4 subnet by prefix from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet4-get-by-prefix\"
+    \"arguments\": {
+        \"subnets\": [ {
+            \"subnet\": <subnet prefix>
+        } ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one prefix of the subnet to be returned.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv4 subnet found.\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <subnet identifier>
+                \"subnet\": <subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                },
+                <the rest of the subnet specification here>
+            }
+        ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-subnet4-list.json b/doc/api/remote-subnet4-list.json
new file mode 100644
index 0000000000000000000000000000000000000000..92ea88e7f06065e3476d64b27b39d2d64caca732
--- /dev/null
+++ b/doc/api/remote-subnet4-list.json
@@ -0,0 +1,42 @@
+{
+    "name": "remote-subnet4-list",
+    "brief": "This command is used to fetch a list of all IPv4 subnets from the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet4-list\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes no arguments besides the optional <command>remote</command> map.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 IPv4 subnets found.\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <first subnet identifier>,
+                \"subnet\": <first subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                \"id\": <second subnet identifier>,
+                \"subnet\": <second subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains a subnet identifier, prefix and shared network name to which the subnet belongs. If the subnet does not belong to a shared netork the name is null. The metadata includes database specific information associated with the subnets. The returned list does not contain full subnet definitions. Use <command>remote-subnet4-get</command> to fetch the full information about the selected subnets."
+}
diff --git a/doc/api/remote-subnet4-set.json b/doc/api/remote-subnet4-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..b4b409ce77765612be2472b10e856fa8ae125540
--- /dev/null
+++ b/doc/api/remote-subnet4-set.json
@@ -0,0 +1,32 @@
+{
+    "name": "remote-subnet4-set",
+    "brief": "This command is used to create or replace an IPv4 subnet the configuration database.",
+    "support": [ "kea-dhcp4" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet4-set\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <subnet identifier>,
+                \"subnet\": <subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                <the rest of the subnet specification here>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must contain exactly one subnet specification. The <command>shared-network-name</command> parameter is required for these commands. It associates the subnet with the shared network by its name. If the subnet must not belong to any shared network (global subnet), the <command>null</command> value must be specified for the shared network name.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv4 subnet successfully set.\",
+    \"arguments\": {
+        \"id\": <subnet identifier>,
+        \"subnet\": <subnet prefix>
+    }
+}"
+}
diff --git a/doc/api/remote-subnet6-del-by-id.json b/doc/api/remote-subnet6-del-by-id.json
new file mode 100644
index 0000000000000000000000000000000000000000..194552b66f798f4cef2c8cae8fcf2ad10ecc53cd
--- /dev/null
+++ b/doc/api/remote-subnet6-del-by-id.json
@@ -0,0 +1,28 @@
+{
+    "name": "remote-subnet6-del-by-id",
+    "brief": "This command is used to delete an IPv6 subnet by ID from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet6-del-by-id\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <subnet identifier>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one id of the subnet to be deleted.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 IPv6 subnet(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-subnet6-del-by-prefix.json b/doc/api/remote-subnet6-del-by-prefix.json
new file mode 100644
index 0000000000000000000000000000000000000000..0909b7bbfeb2edd157b76b31d4b13e28c38280bf
--- /dev/null
+++ b/doc/api/remote-subnet6-del-by-prefix.json
@@ -0,0 +1,28 @@
+{
+    "name": "remote-subnet6-del-by-prefix",
+    "brief": "This command is used to delete an IPv6 subnet by prefix from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet6-del-by-prefix\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"subnet\": <subnet prefix>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one prefix of the subnet to be deleted.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"1 IPv6 subnet(s) deleted.\",
+    \"arguments\": {
+        \"count\": 1
+    }
+}"
+}
diff --git a/doc/api/remote-subnet6-get-by-id.json b/doc/api/remote-subnet6-get-by-id.json
new file mode 100644
index 0000000000000000000000000000000000000000..b260eec7fc093f886a788e4afe2334533e9f938a
--- /dev/null
+++ b/doc/api/remote-subnet6-get-by-id.json
@@ -0,0 +1,40 @@
+{
+    "name": "remote-subnet6-get-by-id",
+    "brief": "This command is used to fetch selected IPv6 subnet by ID for the server from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet6-get-by-id\"
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <subnet identifier>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one id of the subnet to be returned.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv6 subnet found.\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <subnet identifier>
+                \"subnet\": <subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                },
+                <the rest of the subnet specification here>
+            }
+        ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-subnet6-get-by-prefix.json b/doc/api/remote-subnet6-get-by-prefix.json
new file mode 100644
index 0000000000000000000000000000000000000000..86dbfcb3fe6b151bf25fdcc878e62e7f5a2e2b83
--- /dev/null
+++ b/doc/api/remote-subnet6-get-by-prefix.json
@@ -0,0 +1,38 @@
+{
+    "name": "remote-subnet6-get-by-prefix",
+    "brief": "This command is used to fetch selected IPv6 subnet by prefix from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet4-get-by-prefix\"
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"subnet\": <subnet prefix>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes a list with exactly one prefix of the subnet to be returned.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv6 subnet found.\",
+    \"arguments\": {
+        \"subnets\": [ {
+            \"id\": <subnet identifier>
+            \"subnet\": <subnet prefix>,
+            \"shared-network-name\": <shared network name> | null,
+            \"metadata\": {
+                \"server-tag\": <server tag>
+            },
+            <the rest of the subnet specification here>
+        } ],
+        \"count\": 1
+    }
+}",
+    "resp-comment": "If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object."
+}
diff --git a/doc/api/remote-subnet6-list.json b/doc/api/remote-subnet6-list.json
new file mode 100644
index 0000000000000000000000000000000000000000..ea279512987d0dcc5934b85cfcf49f58df4dfb96
--- /dev/null
+++ b/doc/api/remote-subnet6-list.json
@@ -0,0 +1,42 @@
+{
+    "name": "remote-subnet6-list",
+    "brief": "This command is used to fetch a list of all IPv6 subnets from the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet6-list\"
+    \"arguments\": {
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "This command includes no arguments besides the optional <command>remote</command> map.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"2 IPv6 subnets found.\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <first subnet identifier>,
+                \"subnet\": <first subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            },
+            {
+                \"id\": <second subnet identifier>,
+                \"subnet\": <second subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                \"metadata\": {
+                    \"server-tag\": <server tag>
+                }
+            }
+        ],
+        \"count\": 2
+    }
+}",
+    "resp-comment": "The returned response contains a list of maps. Each map contains a subnet identifier, prefix and shared network name to which the subnet belongs. If the subnet does not belong to a shared netork the name is null. The metadata includes database specific information associated with the subnets. The returned list does not contain full subnet definitions. Use <command>remote-subnet6-get</command> to fetch the full information about the selected subnets."
+}
diff --git a/doc/api/remote-subnet6-set.json b/doc/api/remote-subnet6-set.json
new file mode 100644
index 0000000000000000000000000000000000000000..f0545b95b89b26f5b9c1da07c692f1047ce34a0a
--- /dev/null
+++ b/doc/api/remote-subnet6-set.json
@@ -0,0 +1,32 @@
+{
+    "name": "remote-subnet6-set",
+    "brief": "This command is used to create or replace an IPv4 subnet the configuration database.",
+    "support": [ "kea-dhcp6" ],
+    "avail": "1.6.0",
+    "hook": "cb_cmds",
+    "cmd-syntax": "{
+    \"command\": \"remote-subnet6-set\",
+    \"arguments\": {
+        \"subnets\": [
+            {
+                \"id\": <subnet identifier>,
+                \"subnet\": <subnet prefix>,
+                \"shared-network-name\": <shared network name> | null,
+                <the rest of the subnet specification here>
+            }
+        ],
+        \"remote\": {
+            <specification of the database to connect to>
+        }
+    }
+}",
+    "cmd-comment": "The provided list must contain exactly one subnet specification. The <command>shared-network-name</command> parameter is required for these commands. It associates the subnet with the shared network by its name. If the subnet must not belong to any shared network (global subnet), the <command>null</command> value must be specified for the shared network name.",
+    "resp-syntax": "{
+    \"result\": 0,
+    \"text\": \"IPv6 subnet successfully set.\",
+    \"arguments\": {
+        \"id\": <subnet identifier>,
+        \"subnet\": <subnet prefix>
+    }
+}"
+}
diff --git a/doc/docgen/cmds-list b/doc/docgen/cmds-list
index 55db2c753acb2369fe2ff666e4b0f755e5d86c04..2a22ef34bb0cf57a983904d1174071aed736d699 100644
--- a/doc/docgen/cmds-list
+++ b/doc/docgen/cmds-list
@@ -50,6 +50,50 @@ network6-get
 network6-list
 network6-subnet-add
 network6-subnet-del
+remote-global-parameter4-del
+remote-global-parameter4-get
+remote-global-parameter4-get-all
+remote-global-parameter4-set
+remote-global-parameter6-del
+remote-global-parameter6-get
+remote-global-parameter6-get-all
+remote-global-parameter6-set
+remote-network4-del
+remote-network4-get
+remote-network4-list
+remote-network4-set
+remote-network6-del
+remote-network6-get
+remote-network6-list
+remote-network6-set
+remote-option-def4-del
+remote-option-def4-get
+remote-option-def4-get-all
+remote-option-def4-set
+remote-option-def6-del
+remote-option-def6-get
+remote-option-def6-get-all
+remote-option-def6-set
+remote-option4-global-del
+remote-option4-global-get
+remote-option4-global-get-all
+remote-option4-global-set
+remote-option6-global-del
+remote-option6-global-get
+remote-option6-global-get-all
+remote-option6-global-set
+remote-subnet4-del-by-id
+remote-subnet4-del-by-prefix
+remote-subnet4-get-by-id
+remote-subnet4-get-by-prefix
+remote-subnet4-list
+remote-subnet4-set
+remote-subnet6-del-by-id
+remote-subnet6-del-by-prefix
+remote-subnet6-get-by-id
+remote-subnet6-get-by-prefix
+remote-subnet6-list
+remote-subnet6-set
 reservation-add
 reservation-del
 reservation-get
diff --git a/doc/examples/kea4/config-backend.json b/doc/examples/kea4/config-backend.json
new file mode 100644
index 0000000000000000000000000000000000000000..637ad8433e1254087f8d7bf1fae36503153cdd2b
--- /dev/null
+++ b/doc/examples/kea4/config-backend.json
@@ -0,0 +1,76 @@
+// This is an example configuration file for the DHCPv4 server in Kea.
+// It demonstrates how to enable Kea Configuration Backend using MySQL.
+// It requires that libdhcp_mysql_cb.so library is available and
+// optionally libdhcp_cb_cmds.so hooks library.
+
+{ "Dhcp4":
+
+{
+    // Kea is told to listen on ethX interface only.
+    "interfaces-config": {
+        "interfaces": [ "ethX" ]
+    },
+
+    // Use memfile lease database backend.
+    "lease-database": {
+        "type": "memfile",
+        "lfc-interval": 3600
+    },
+
+    // This parameter controls how the server accesses the configuration
+    // database. Currently only one database type is available - "mysql".
+    // It requires that libdhcp_mysql_cb.so hooks library is loaded.
+    "config-control": {
+        // A list of database backends to connect to. Currently, it is limited
+        // to a single backend.
+        "config-databases": [
+            {
+                "type": "mysql",
+                "name": "kea",
+                "user": "kea",
+                "password": "kea",
+                "host": "localhost",
+                "port": 3306
+            }
+        ],
+        // Controls how often the server polls the database for the
+        // configuration updates. The setting below implies that it
+        // will take up to approx. 20 seconds for the server to
+        // discover and fetch configuration changes.
+        "config-fetch-wait-time": 20
+    },
+
+    // Hooks libraries that enable configuration backend are loaded.
+    "hooks-libraries": [
+        // The libdhcp_mysql_cb.so is required to use MySQL Configuration
+        // Backend.
+        {
+            "library": "/usr/local/lib/kea/hooks/libdhcp_mysql_cb.so"
+        }
+        // The libdhcp_cb_cmds.so is optional. It allows for managing the
+        // configuration in the database. If this library is not loaded,
+        // the configuration can be managed directly using available
+        // tools that work directly with the MySQL database.
+        //,{
+            // "library": "/usr/local/lib/kea/hooks/libdhcp_cb_cmds.so"
+        //}
+    ],
+
+    // The following configures logging. It assumes that messages with at
+    // least informational level (info, warn, error and fatal) should be
+    // logged to stdout. Alternatively, you can specify stderr here, a filename
+    // or 'syslog', which will store output messages via syslog.
+    "loggers": [
+        {
+            "name": "kea-dhcp4",
+            "output_options": [
+                {
+                    "output": "stdout"
+                }
+            ],
+            "severity": "INFO"
+        }
+    ]
+}
+
+}
diff --git a/doc/examples/kea6/config-backend.json b/doc/examples/kea6/config-backend.json
new file mode 100644
index 0000000000000000000000000000000000000000..8956462d3f01bd4c20186c3e692f1a649de6f587
--- /dev/null
+++ b/doc/examples/kea6/config-backend.json
@@ -0,0 +1,77 @@
+// This is an example configuration file for the DHCPv4 server in Kea.
+// It demonstrates how to enable Kea Configuration Backend using MySQL.
+// It requires that libdhcp_mysql_cb.so library is available and
+// optionally libdhcp_cb_cmds.so hooks library.
+
+{ "Dhcp6":
+
+{
+    // Kea is told to listen on ethX interface only.
+    "interfaces-config": {
+        "interfaces": [ "ethX" ]
+    },
+
+    // Use memfile lease database backend.
+    "lease-database": {
+        "type": "memfile",
+        "lfc-interval": 3600
+    },
+
+    // This parameter controls how the server accesses the configuration
+    // database. Currently only one database type is available - "mysql".
+    // It requires that libdhcp_mysql_cb.so hooks library is loaded.
+    "config-control": {
+        // A list of database backends to connect to. Currently, it is limited
+        // to a single backend.
+        "config-databases": [
+            {
+                "type": "mysql",
+                "name": "kea",
+                "user": "kea",
+                "password": "kea",
+                "host": "localhost",
+                "port": 3306
+            }
+        ],
+        // Controls how often the server polls the database for the
+        // configuration updates. The setting below implies that it
+        // will take up to approx. 20 seconds for the server to
+        // discover and fetch configuration changes.
+        "config-fetch-wait-time": 20
+    },
+
+    // Hooks libraries that enable configuration backend are loaded.
+    "hooks-libraries": [
+        // The libdhcp_mysql_cb.so is required to use MySQL Configuration
+        // Backend.
+        {
+            "library": "/usr/local/lib/kea/hooks/libdhcp_mysql_cb.so"
+        }
+        // The libdhcp_cb_cmds.so is optional. It allows for managing the
+        // configuration in the database. If this library is not loaded,
+        // the configuration can be managed directly using available
+        // tools that work directly with the MySQL database.
+        //,{
+            // "library": "/usr/local/lib/kea/hooks/libdhcp_cb_cmds.so"
+        //}
+    ],
+
+    // The following configures logging. It assumes that messages with at
+    // least informational level (info, warn, error and fatal) should be
+    // logged to stdout. Alternatively, you can specify stderr here, a filename
+    // or 'syslog', which will store output messages via syslog.
+    "loggers": [
+        {
+            "name": "kea-dhcp6",
+            "output_options": [
+                {
+                    "output": "stdout"
+                }
+            ],
+            "debuglevel": 0,
+            "severity": "INFO"
+        }
+    ]
+}
+
+}
diff --git a/doc/guide/Makefile.am b/doc/guide/Makefile.am
index 46945c4176b48c046a14875e9a6bc51d7beb7310..948fc9e58b844386ad6b6a1056c217c4f9f1128e 100644
--- a/doc/guide/Makefile.am
+++ b/doc/guide/Makefile.am
@@ -6,11 +6,11 @@ dist_doc_DATA = $(DOCS)
 dist_html_DATA = $(HTMLDOCS) kea-guide.css kea-logo-100x70.png
 
 DOCBOOK = kea-guide.xml intro.xml quickstart.xml install.xml admin.xml config.xml
-DOCBOOK += keactrl.xml dhcp4-srv.xml dhcp6-srv.xml lease-expiration.xml logging.xml
-DOCBOOK += ddns.xml hooks.xml hooks-class-cmds.xml hooks-ha.xml hooks-host-cache.xml
-DOCBOOK += hooks-lease-cmds.xml hooks-radius.xml hooks-stat-cmds.xml
-DOCBOOK += lfc.xml stats.xml ctrl-channel.xml classify.xml shell.xml agent.xml
-DOCBOOK += netconf.xml api.xml congestion-handling.xml hammer.xml
+DOCBOOK += config-backend.xml keactrl.xml dhcp4-srv.xml dhcp6-srv.xml lease-expiration.xml
+DOCBOOK += logging.xml ddns.xml hooks.xml hooks-class-cmds.xml hooks-cb-cmds.xml
+DOCBOOK += hooks-ha.xml hooks-host-cache.xml hooks-lease-cmds.xml hooks-radius.xml
+DOCBOOK += hooks-stat-cmds.xml lfc.xml stats.xml ctrl-channel.xml classify.xml shell.xml
+DOCBOOK += agent.xml netconf.xml api.xml congestion-handling.xml hammer.xml
 
 EXTRA_DIST = $(DOCBOOK)
 
diff --git a/doc/guide/admin.xml b/doc/guide/admin.xml
index f20fea02431a07576d0fdb45a7dd56dee5730ebd..c7e709c0bc755f20d4a3d5b027c095fe97595ef0 100644
--- a/doc/guide/admin.xml
+++ b/doc/guide/admin.xml
@@ -1,5 +1,5 @@
 <!--
- - Copyright (C) 2015-2018 Internet Systems Consortium, Inc. ("ISC")
+ - Copyright (C) 2015-2019 Internet Systems Consortium, Inc. ("ISC")
  -
  - This Source Code Form is subject to the terms of the Mozilla Public
  - License, v. 2.0. If a copy of the MPL was not distributed with this
@@ -14,15 +14,11 @@
     <title>Databases and Database Version Numbers</title>
 
     <para>
-      Kea supports the storage of leases and host reservations (i.e. static
-      assignments of addresses, prefixes, and options) in one of
-      the several supported backend databases. As future versions of Kea
-      are released, the structure of those backends will change.
-      For example, Kea currently only stores lease information
-      and host reservations. Future versions of Kea will store
-      additional data such as subnet definitions, so the backend
-      structure will need to be updated to accommodate the extra
-      information.
+      Kea may be configured to use a database as a storage for leases,
+      a source of servers' configurations and host reservations (i.e. static
+      assignments of addresses, prefixes, options etc.). Subsequent Kea
+      releases introduce changes to the database schemas to faciliate new
+      features and correct discovered issues with the existing schemas.
     </para>
 
     <para>
@@ -75,7 +71,7 @@
         <listitem>
           <simpara>
             <command>lease-init</command> —
-            Initializes a new lease database. This is useful during a new
+            Initializes a new database schema. This is useful during a new
             Kea installation. The database is initialized to the
             latest version supported by the version of the software being
             installed.
@@ -85,7 +81,7 @@
         <listitem>
           <simpara>
             <command>lease-version</command> —
-            Reports the lease backend version number. This is
+            Reports the database backend version number. This is
             not necessarily equal to the Kea version number as
             each backend has its own versioning scheme.
           </simpara>
@@ -94,7 +90,7 @@
         <listitem>
           <simpara>
             <command>lease-upgrade</command> —
-            Conducts a lease backend upgrade. This is useful when
+            Conducts a database schema upgrade. This is useful when
             upgrading Kea.
           </simpara>
         </listitem>
@@ -125,21 +121,21 @@
         <listitem>
           <simpara>
             <command>mysql</command> —
-            Lease information is stored in a MySQL relational database.
+            Information is stored in a MySQL relational database.
           </simpara>
         </listitem>
 
         <listitem>
           <simpara>
             <command>pgsql</command> —
-            Lease information is stored in a PostgreSQL relational database.
+            Information is stored in a PostgreSQL relational database.
           </simpara>
         </listitem>
 
         <listitem>
           <simpara>
             <command>cql</command> —
-            Lease information is stored in an Apache Cassandra database.
+            Information is stored in an Apache Cassandra database.
           </simpara>
         </listitem>
 
@@ -220,6 +216,14 @@
               <entry>yes</entry>
             </row>
 
+            <row>
+              <entry>Configuration Backend</entry>
+              <entry>no</entry>
+              <entry>yes</entry>
+              <entry>no</entry>
+              <entry>no</entry>
+            </row>
+
           </tbody>
           </tgroup>
        </table>
@@ -271,8 +275,9 @@
       <title>MySQL</title>
 
       <para>
-        MySQL is able to store leases, host reservations, and options defined on
-        a per-host basis. This section can be safely ignored
+        MySQL is able to store leases, host reservations, options defined on
+        a per-host basis and a subset of the server configuration parameters
+        (serving as a configuration backend). This section can be safely ignored
         if you choose to store the data in other backends.
       </para>
 
diff --git a/doc/guide/api.xml b/doc/guide/api.xml
index b2512965740f24bd66719532842d7dd016e231f3..a1a37e599f5fbd25d4931fdd197fce5c715c357c 100644
--- a/doc/guide/api.xml
+++ b/doc/guide/api.xml
@@ -9,7 +9,7 @@
 <!-- autogenerated using cmd_docgen. Do not edit by hand! -->
 <appendix xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="api">
   <title>API Reference</title>
-  <para>Kea currently supports 71 commands:
+  <para>Kea currently supports 121 commands:
 <command><link linkend="ref-build-report">build-report</link></command>
 , <command><link linkend="ref-cache-clear">cache-clear</link></command>
 , <command><link linkend="ref-cache-get">cache-get</link></command>
@@ -62,6 +62,50 @@
 , <command><link linkend="ref-network6-list">network6-list</link></command>
 , <command><link linkend="ref-network6-subnet-add">network6-subnet-add</link></command>
 , <command><link linkend="ref-network6-subnet-del">network6-subnet-del</link></command>
+, <command><link linkend="ref-remote-global-parameter4-del">remote-global-parameter4-del</link></command>
+, <command><link linkend="ref-remote-global-parameter4-get">remote-global-parameter4-get</link></command>
+, <command><link linkend="ref-remote-global-parameter4-get-all">remote-global-parameter4-get-all</link></command>
+, <command><link linkend="ref-remote-global-parameter4-set">remote-global-parameter4-set</link></command>
+, <command><link linkend="ref-remote-global-parameter6-del">remote-global-parameter6-del</link></command>
+, <command><link linkend="ref-remote-global-parameter6-get">remote-global-parameter6-get</link></command>
+, <command><link linkend="ref-remote-global-parameter6-get-all">remote-global-parameter6-get-all</link></command>
+, <command><link linkend="ref-remote-global-parameter6-set">remote-global-parameter6-set</link></command>
+, <command><link linkend="ref-remote-network4-del">remote-network4-del</link></command>
+, <command><link linkend="ref-remote-network4-get">remote-network4-get</link></command>
+, <command><link linkend="ref-remote-network4-list">remote-network4-list</link></command>
+, <command><link linkend="ref-remote-network4-set">remote-network4-set</link></command>
+, <command><link linkend="ref-remote-network6-del">remote-network6-del</link></command>
+, <command><link linkend="ref-remote-network6-get">remote-network6-get</link></command>
+, <command><link linkend="ref-remote-network6-list">remote-network6-list</link></command>
+, <command><link linkend="ref-remote-network6-set">remote-network6-set</link></command>
+, <command><link linkend="ref-remote-option-def4-del">remote-option-def4-del</link></command>
+, <command><link linkend="ref-remote-option-def4-get">remote-option-def4-get</link></command>
+, <command><link linkend="ref-remote-option-def4-get-all">remote-option-def4-get-all</link></command>
+, <command><link linkend="ref-remote-option-def4-set">remote-option-def4-set</link></command>
+, <command><link linkend="ref-remote-option-def6-del">remote-option-def6-del</link></command>
+, <command><link linkend="ref-remote-option-def6-get">remote-option-def6-get</link></command>
+, <command><link linkend="ref-remote-option-def6-get-all">remote-option-def6-get-all</link></command>
+, <command><link linkend="ref-remote-option-def6-set">remote-option-def6-set</link></command>
+, <command><link linkend="ref-remote-option4-global-del">remote-option4-global-del</link></command>
+, <command><link linkend="ref-remote-option4-global-get">remote-option4-global-get</link></command>
+, <command><link linkend="ref-remote-option4-global-get-all">remote-option4-global-get-all</link></command>
+, <command><link linkend="ref-remote-option4-global-set">remote-option4-global-set</link></command>
+, <command><link linkend="ref-remote-option6-global-del">remote-option6-global-del</link></command>
+, <command><link linkend="ref-remote-option6-global-get">remote-option6-global-get</link></command>
+, <command><link linkend="ref-remote-option6-global-get-all">remote-option6-global-get-all</link></command>
+, <command><link linkend="ref-remote-option6-global-set">remote-option6-global-set</link></command>
+, <command><link linkend="ref-remote-subnet4-del-by-id">remote-subnet4-del-by-id</link></command>
+, <command><link linkend="ref-remote-subnet4-del-by-prefix">remote-subnet4-del-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet4-get-by-id">remote-subnet4-get-by-id</link></command>
+, <command><link linkend="ref-remote-subnet4-get-by-prefix">remote-subnet4-get-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet4-list">remote-subnet4-list</link></command>
+, <command><link linkend="ref-remote-subnet4-set">remote-subnet4-set</link></command>
+, <command><link linkend="ref-remote-subnet6-del-by-id">remote-subnet6-del-by-id</link></command>
+, <command><link linkend="ref-remote-subnet6-del-by-prefix">remote-subnet6-del-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet6-get-by-id">remote-subnet6-get-by-id</link></command>
+, <command><link linkend="ref-remote-subnet6-get-by-prefix">remote-subnet6-get-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet6-list">remote-subnet6-list</link></command>
+, <command><link linkend="ref-remote-subnet6-set">remote-subnet6-set</link></command>
 , <command><link linkend="ref-reservation-add">reservation-add</link></command>
 , <command><link linkend="ref-reservation-del">reservation-del</link></command>
 , <command><link linkend="ref-reservation-get">reservation-get</link></command>
@@ -148,6 +192,28 @@
 , <command><link linkend="ref-network4-list">network4-list</link></command>
 , <command><link linkend="ref-network4-subnet-add">network4-subnet-add</link></command>
 , <command><link linkend="ref-network4-subnet-del">network4-subnet-del</link></command>
+, <command><link linkend="ref-remote-global-parameter4-del">remote-global-parameter4-del</link></command>
+, <command><link linkend="ref-remote-global-parameter4-get">remote-global-parameter4-get</link></command>
+, <command><link linkend="ref-remote-global-parameter4-get-all">remote-global-parameter4-get-all</link></command>
+, <command><link linkend="ref-remote-global-parameter4-set">remote-global-parameter4-set</link></command>
+, <command><link linkend="ref-remote-network4-del">remote-network4-del</link></command>
+, <command><link linkend="ref-remote-network4-get">remote-network4-get</link></command>
+, <command><link linkend="ref-remote-network4-list">remote-network4-list</link></command>
+, <command><link linkend="ref-remote-network4-set">remote-network4-set</link></command>
+, <command><link linkend="ref-remote-option-def4-del">remote-option-def4-del</link></command>
+, <command><link linkend="ref-remote-option-def4-get">remote-option-def4-get</link></command>
+, <command><link linkend="ref-remote-option-def4-get-all">remote-option-def4-get-all</link></command>
+, <command><link linkend="ref-remote-option-def4-set">remote-option-def4-set</link></command>
+, <command><link linkend="ref-remote-option4-global-del">remote-option4-global-del</link></command>
+, <command><link linkend="ref-remote-option4-global-get">remote-option4-global-get</link></command>
+, <command><link linkend="ref-remote-option4-global-get-all">remote-option4-global-get-all</link></command>
+, <command><link linkend="ref-remote-option4-global-set">remote-option4-global-set</link></command>
+, <command><link linkend="ref-remote-subnet4-del-by-id">remote-subnet4-del-by-id</link></command>
+, <command><link linkend="ref-remote-subnet4-del-by-prefix">remote-subnet4-del-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet4-get-by-id">remote-subnet4-get-by-id</link></command>
+, <command><link linkend="ref-remote-subnet4-get-by-prefix">remote-subnet4-get-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet4-list">remote-subnet4-list</link></command>
+, <command><link linkend="ref-remote-subnet4-set">remote-subnet4-set</link></command>
 , <command><link linkend="ref-reservation-add">reservation-add</link></command>
 , <command><link linkend="ref-reservation-del">reservation-del</link></command>
 , <command><link linkend="ref-reservation-get">reservation-get</link></command>
@@ -208,6 +274,28 @@
 , <command><link linkend="ref-network6-list">network6-list</link></command>
 , <command><link linkend="ref-network6-subnet-add">network6-subnet-add</link></command>
 , <command><link linkend="ref-network6-subnet-del">network6-subnet-del</link></command>
+, <command><link linkend="ref-remote-global-parameter6-del">remote-global-parameter6-del</link></command>
+, <command><link linkend="ref-remote-global-parameter6-get">remote-global-parameter6-get</link></command>
+, <command><link linkend="ref-remote-global-parameter6-get-all">remote-global-parameter6-get-all</link></command>
+, <command><link linkend="ref-remote-global-parameter6-set">remote-global-parameter6-set</link></command>
+, <command><link linkend="ref-remote-network6-del">remote-network6-del</link></command>
+, <command><link linkend="ref-remote-network6-get">remote-network6-get</link></command>
+, <command><link linkend="ref-remote-network6-list">remote-network6-list</link></command>
+, <command><link linkend="ref-remote-network6-set">remote-network6-set</link></command>
+, <command><link linkend="ref-remote-option-def6-del">remote-option-def6-del</link></command>
+, <command><link linkend="ref-remote-option-def6-get">remote-option-def6-get</link></command>
+, <command><link linkend="ref-remote-option-def6-get-all">remote-option-def6-get-all</link></command>
+, <command><link linkend="ref-remote-option-def6-set">remote-option-def6-set</link></command>
+, <command><link linkend="ref-remote-option6-global-del">remote-option6-global-del</link></command>
+, <command><link linkend="ref-remote-option6-global-get">remote-option6-global-get</link></command>
+, <command><link linkend="ref-remote-option6-global-get-all">remote-option6-global-get-all</link></command>
+, <command><link linkend="ref-remote-option6-global-set">remote-option6-global-set</link></command>
+, <command><link linkend="ref-remote-subnet6-del-by-id">remote-subnet6-del-by-id</link></command>
+, <command><link linkend="ref-remote-subnet6-del-by-prefix">remote-subnet6-del-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet6-get-by-id">remote-subnet6-get-by-id</link></command>
+, <command><link linkend="ref-remote-subnet6-get-by-prefix">remote-subnet6-get-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet6-list">remote-subnet6-list</link></command>
+, <command><link linkend="ref-remote-subnet6-set">remote-subnet6-set</link></command>
 , <command><link linkend="ref-reservation-add">reservation-add</link></command>
 , <command><link linkend="ref-reservation-del">reservation-del</link></command>
 , <command><link linkend="ref-reservation-get">reservation-get</link></command>
@@ -228,6 +316,51 @@
 , <command><link linkend="ref-subnet6-update">subnet6-update</link></command>
 , <command><link linkend="ref-version-get">version-get</link></command>
 .</para>
+<para xml:id="commands-cb_cmds-lib">Commands supported by cb_cmds hook library: <command><link linkend="ref-remote-global-parameter4-del">remote-global-parameter4-del</link></command>
+, <command><link linkend="ref-remote-global-parameter4-get">remote-global-parameter4-get</link></command>
+, <command><link linkend="ref-remote-global-parameter4-get-all">remote-global-parameter4-get-all</link></command>
+, <command><link linkend="ref-remote-global-parameter4-set">remote-global-parameter4-set</link></command>
+, <command><link linkend="ref-remote-global-parameter6-del">remote-global-parameter6-del</link></command>
+, <command><link linkend="ref-remote-global-parameter6-get">remote-global-parameter6-get</link></command>
+, <command><link linkend="ref-remote-global-parameter6-get-all">remote-global-parameter6-get-all</link></command>
+, <command><link linkend="ref-remote-global-parameter6-set">remote-global-parameter6-set</link></command>
+, <command><link linkend="ref-remote-network4-del">remote-network4-del</link></command>
+, <command><link linkend="ref-remote-network4-get">remote-network4-get</link></command>
+, <command><link linkend="ref-remote-network4-list">remote-network4-list</link></command>
+, <command><link linkend="ref-remote-network4-set">remote-network4-set</link></command>
+, <command><link linkend="ref-remote-network6-del">remote-network6-del</link></command>
+, <command><link linkend="ref-remote-network6-get">remote-network6-get</link></command>
+, <command><link linkend="ref-remote-network6-list">remote-network6-list</link></command>
+, <command><link linkend="ref-remote-network6-set">remote-network6-set</link></command>
+, <command><link linkend="ref-remote-option-def4-del">remote-option-def4-del</link></command>
+, <command><link linkend="ref-remote-option-def4-get">remote-option-def4-get</link></command>
+, <command><link linkend="ref-remote-option-def4-get-all">remote-option-def4-get-all</link></command>
+, <command><link linkend="ref-remote-option-def4-set">remote-option-def4-set</link></command>
+, <command><link linkend="ref-remote-option-def6-del">remote-option-def6-del</link></command>
+, <command><link linkend="ref-remote-option-def6-get">remote-option-def6-get</link></command>
+, <command><link linkend="ref-remote-option-def6-get-all">remote-option-def6-get-all</link></command>
+, <command><link linkend="ref-remote-option-def6-set">remote-option-def6-set</link></command>
+, <command><link linkend="ref-remote-option4-global-del">remote-option4-global-del</link></command>
+, <command><link linkend="ref-remote-option4-global-get">remote-option4-global-get</link></command>
+, <command><link linkend="ref-remote-option4-global-get-all">remote-option4-global-get-all</link></command>
+, <command><link linkend="ref-remote-option4-global-set">remote-option4-global-set</link></command>
+, <command><link linkend="ref-remote-option6-global-del">remote-option6-global-del</link></command>
+, <command><link linkend="ref-remote-option6-global-get">remote-option6-global-get</link></command>
+, <command><link linkend="ref-remote-option6-global-get-all">remote-option6-global-get-all</link></command>
+, <command><link linkend="ref-remote-option6-global-set">remote-option6-global-set</link></command>
+, <command><link linkend="ref-remote-subnet4-del-by-id">remote-subnet4-del-by-id</link></command>
+, <command><link linkend="ref-remote-subnet4-del-by-prefix">remote-subnet4-del-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet4-get-by-id">remote-subnet4-get-by-id</link></command>
+, <command><link linkend="ref-remote-subnet4-get-by-prefix">remote-subnet4-get-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet4-list">remote-subnet4-list</link></command>
+, <command><link linkend="ref-remote-subnet4-set">remote-subnet4-set</link></command>
+, <command><link linkend="ref-remote-subnet6-del-by-id">remote-subnet6-del-by-id</link></command>
+, <command><link linkend="ref-remote-subnet6-del-by-prefix">remote-subnet6-del-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet6-get-by-id">remote-subnet6-get-by-id</link></command>
+, <command><link linkend="ref-remote-subnet6-get-by-prefix">remote-subnet6-get-by-prefix</link></command>
+, <command><link linkend="ref-remote-subnet6-list">remote-subnet6-list</link></command>
+, <command><link linkend="ref-remote-subnet6-set">remote-subnet6-set</link></command>
+.</para>
 <para xml:id="commands-class_cmds-lib">Commands supported by class_cmds hook library: <command><link linkend="ref-class-add">class-add</link></command>
 , <command><link linkend="ref-class-del">class-del</link></command>
 , <command><link linkend="ref-class-get">class-get</link></command>
@@ -376,7 +509,7 @@ Result is an integer representation of the status. Currently supported statuses
   <screen>{
     "result": 0
     "text": "123 entries returned."
-    "arguments": &lt;list of cashed host&gt;
+    "arguments": &lt;list of host reservations&gt;
 }</screen>
 Result is an integer representation of the status. Currently supported statuses are:
 <itemizedlist>
@@ -393,7 +526,7 @@ Result is an integer representation of the status. Currently supported statuses
 <!-- start of cache-get-by-id -->
 <section xml:id="reference-cache-get-by-id">
 <title>cache-get-by-id reference</title>
-<para xml:id="ref-cache-get-by-id"><command>cache-get-by-id</command> - Returns entries matching the given identifier from the host cache.</para>
+<para xml:id="ref-cache-get-by-id"><command>cache-get-by-id</command> - Returns entries matching the given identifier from  the host cache.</para>
 
 <para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
 
@@ -406,15 +539,14 @@ Result is an integer representation of the status. Currently supported statuses
     "command": "cache-get-by-id",
     "arguments": {
         "hw-address": "01:02:03:04:05:06"
-    }
-}</screen>
+    }</screen>
 </para>
 
 <para>Response syntax:
   <screen>{
     "result": 0
     "text": "2 entries returned."
-    "arguments": &lt;list of cashed host&gt;
+    "arguments": &lt;list of host reservations&gt;
 }</screen>
 Result is an integer representation of the status. Currently supported statuses are:
 <itemizedlist>
@@ -584,7 +716,7 @@ Result is an integer representation of the status. Currently supported statuses
 <!-- start of cache-size -->
 <section xml:id="reference-cache-size">
 <title>cache-size reference</title>
-<para xml:id="ref-cache-size"><command>cache-size</command> - This command returns the number of cached host reservations.</para>
+<para xml:id="ref-cache-size"><command>cache-size</command> - Returns number of entries of the host cache.</para>
 
 <para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
 
@@ -600,11 +732,10 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Response syntax:
   <screen>{
-    "result": 0,
-    "text": "123 entries.",
+    "result": 0
+    "text": "123 entries."
     "arguments": { "size": 123 }
-}
-</screen>
+}</screen>
 Result is an integer representation of the status. Currently supported statuses are:
 <itemizedlist>
   <listitem><para>0 - success</para></listitem>
@@ -893,7 +1024,7 @@ This command takes no parameters.</para>
   <screen>{
     "result": &lt;integer&gt;,
     "arguments": {
-        &lt;JSON configuration here, starting with Dhcp4, Dhcp6, Dhcp-ddns, or Control-agent object&gt;
+        &lt;JSON configuration here, starting with Dhcp4, Dhcp6, or Control-agent object&gt;
     }
 }</screen>
 Result is an integer representation of the status. Currently supported statuses are:
@@ -1001,7 +1132,7 @@ Result is an integer representation of the status. Currently supported statuses
         }
      }
 }</screen>
-where &lt;server&gt; is the configuration element name for a given server such as "Dhcp4" or "Dhcp6"</para>
+where &gt;server&lt; is the configuration element name for a given server such as "Dhcp4" or "Dhcp6"</para>
 
 <para>Response syntax:
   <screen>{"result": 0, "text": "Configuration seems sane..." }
@@ -1178,11 +1309,11 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.4.0 (<link linkend="commands-high_availability-lib">high_availability</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="ha-server-states"/></para>
+<para>Description and examples: See <xref linkend="command-ha-heartbeat"/></para>
 
 <para>Command syntax:
   <screen>{
-    "command": "ha-heartbeat"
+    "command": "ha-heartbeat",
     }</screen>
 </para>
 
@@ -1214,8 +1345,7 @@ The response to this command is different from the typical command response. The
     "service": [ &lt;service, typically "dhcp4" or "dhcp6"&gt; ],
     "arguments": {
         "scopes": [ "HA_server1", "HA_server2" ]
-    }
-}</screen>
+    }</screen>
 In the example given, the arguments configure the server to handle traffic from both HA_server1 and HA_server2 scopes.</para>
 
 <para>Response syntax:
@@ -1239,8 +1369,8 @@ Result is an integer representation of the status. Currently supported statuses
 <!-- start of ha-sync -->
 <section xml:id="reference-ha-sync">
 <title>ha-sync reference</title>
-<para xml:id="ref-ha-sync"><command>ha-sync</command> - The command is issued to instruct the server running in HA mode to
-synchronize its local lease database with the selected peer.</para>
+<para xml:id="ref-ha-sync"><command>ha-sync</command> - The command is issued to instruct the server running in HA mode to 
+              synchronize its local lease database with the selected peer.</para>
 
 <para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
 
@@ -1409,7 +1539,7 @@ lease4-get returns a result that indicates a result of the operation and lease d
 
 <para>Command syntax:
   <screen>{
-    "command": "lease4-get-all",
+    "command": "lease4-get-all"
     "arguments": "subnets"
 }</screen>
 The lease4-get-all command may result in very large responses.</para>
@@ -1521,7 +1651,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-lease_cmds-lib">lease_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-lease4-add"/></para>
+<para>Description and examples: See <xref linkend="command-lease6-add"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -1536,11 +1666,8 @@ Result is an integer representation of the status. Currently supported statuses
 lease6-add can be also used to add leases for IPv6 prefixes..</para>
 
 <para>Response syntax:
-  <screen>{ "result": 0,
-            "text": "Lease added." }
-
-          { "result": 1,
-            "text": "missing parameter 'ip-address' (&lt;string&gt;:3:19)" }</screen>
+  <screen>{ "result": 0, "text": "Lease added." }
+    { "result": 1, "text": "missing parameter 'ip-address' (&lt;string&gt;:3:19)" }</screen>
 Result is an integer representation of the status. Currently supported statuses are:
 <itemizedlist>
   <listitem><para>0 - success</para></listitem>
@@ -1562,7 +1689,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-lease_cmds-lib">lease_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-lease4-del"/></para>
+<para>Description and examples: See <xref linkend="command-lease6-del"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -1600,7 +1727,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-lease_cmds-lib">lease_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-lease4-get"/></para>
+<para>Description and examples: See <xref linkend="command-lease6-get"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -1639,7 +1766,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-lease_cmds-lib">lease_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-lease4-get-all"/></para>
+<para>Description and examples: See <xref linkend="command-lease6-get-all"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -1703,7 +1830,7 @@ The lease6-get-all command may result in very large responses.</para>
 
 <para>Availability: 1.3.0 (<link linkend="commands-lease_cmds-lib">lease_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-lease4-update"/></para>
+<para>Description and examples: See <xref linkend="command-lease6-update"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -1747,7 +1874,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-lease_cmds-lib">lease_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-lease4-wipe"/></para>
+<para>Description and examples: See <xref linkend="command-lease6-wipe"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -2178,7 +2305,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-subnet_cmds-lib">subnet_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-network4-add"/></para>
+<para>Description and examples: See <xref linkend="command-network6-add"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -2243,7 +2370,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-subnet_cmds-lib">subnet_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-network4-del"/></para>
+<para>Description and examples: See <xref linkend="command-network6-del"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -2284,7 +2411,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-subnet_cmds-lib">subnet_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-network4-get"/></para>
+<para>Description and examples: See <xref linkend="command-network6-get"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -2342,7 +2469,7 @@ Note that the actual response contains many additional fields that are omitted h
 
 <para>Availability: 1.3.0 (<link linkend="commands-subnet_cmds-lib">subnet_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-network4-list"/></para>
+<para>Description and examples: See <xref linkend="command-network6-list"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -2382,7 +2509,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-subnet_cmds-lib">subnet_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-network4-subnet-add"/></para>
+<para>Description and examples: See <xref linkend="command-network6-subnet-add"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -2420,7 +2547,7 @@ Result is an integer representation of the status. Currently supported statuses
 
 <para>Availability: 1.3.0 (<link linkend="commands-subnet_cmds-lib">subnet_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-network4-subnet-del"/></para>
+<para>Description and examples: See <xref linkend="command-network6-subnet-del"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -2449,96 +2576,37 @@ Result is an integer representation of the status. Currently supported statuses
 </section>
 <!-- end of network6-subnet-del -->
 
-<!-- start of reservation-add -->
-<section xml:id="reference-reservation-add">
-<title>reservation-add reference</title>
-<para xml:id="ref-reservation-add"><command>reservation-add</command> - adds a new host reservation. The reservation may include IPv4 address,
-        IPv6 addresses, IPv6 prefixes, various identifiers, a class
-        the client will be assigned to, DHCPv4 and DHCPv6 options and
-        more.</para>
+<!-- start of remote-global-parameter4-del -->
+<section xml:id="reference-remote-global-parameter4-del">
+<title>remote-global-parameter4-del reference</title>
+<para xml:id="ref-remote-global-parameter4-del"><command>remote-global-parameter4-del</command> - This command is used to delete a global DHCPv4 parameter from the configuration database. The server will use the value specified in the configuration file or a default value (if the parameter is not specified in the configuration file) after deleting the parameter from the database.</para>
 
-<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
 
-<para>Availability: 1.2.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-reservation-add"/></para>
+<para>Description and examples: See <xref linkend="command-remote-global-parameter4-del"/></para>
 
 <para>Command syntax:
   <screen>{
-    "command": "reservation-add",
+    "command": "remote-global-parameter4-del",
     "arguments": {
-        "reservation": {
-            "boot-file-name": &lt;string&gt;,
-            "comment": &lt;string&gt;
-            "client-id": &lt;string&gt;,
-            "circuit-id": &lt;string&gt;,
-            "duid": &lt;string&gt;,
-            "flex-id": &lt;string&gt;,
-            "ip-address": &lt;string (IPv4 address)&gt;,
-            "ip-addresses": [ &lt;comma separated strings&gt; ],
-            "hw-address": &lt;string&gt;,
-            "hostname": &lt;string&gt;,
-            "next-server": &lt;string (IPv4 address)&gt;,
-            "option-data-list": [ &lt;comma separated structures defining options&gt; ],
-            "prefixes": [ &lt;comma separated IPv6 prefixes&gt; ],
-            "reservation-client-classes": [ &lt;comma separated strings&gt; ],
-            "server-hostname": &lt;string&gt;,
-            "subnet-id": &lt;integer&gt;,
-            "user-context": &lt;any valid JSON&gt;,
+        "parameters": [ &lt;parameter name&gt; ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
         }
     }
 }</screen>
-Note the ip-address, client-id, next-server, server-hostname and
-boot-file-name are IPv4 specific. duid, ip-addresses and prefixes are
-IPv6 specific.</para>
+This command carries the list including exactly one name of the parameter to be deleted.</para>
 
 <para>Response syntax:
-  <screen>
-{
-    "result": &lt;integer&gt;,
-    "text": &lt;string&gt;
-}</screen>
-Result is an integer representation of the status. Currently supported statuses are:
-<itemizedlist>
-  <listitem><para>0 - success</para></listitem>
-  <listitem><para>1 - error</para></listitem>
-  <listitem><para>2 - unsupported</para></listitem>
-  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)
-  </para></listitem>
-</itemizedlist></para>
-
-</section>
-<!-- end of reservation-add -->
-
-<!-- start of reservation-del -->
-<section xml:id="reference-reservation-del">
-<title>reservation-del reference</title>
-<para xml:id="ref-reservation-del"><command>reservation-del</command> - Deletes an existing host reservation.</para>
-
-<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
-
-<para>Availability: 1.2.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
-
-<para>Description and examples: See <xref linkend="command-reservation-del"/></para>
-
-<para>Command syntax:
   <screen>{
-    "command": "reservation-del",
+    "result": 0,
+    "text": "DHCPv4 global parameter(s) deleted.",
     "arguments": {
-        "subnet-id": &lt;integer&gt;,
-        "ip-address": &lt;string&gt;,
-        "identifier-type": &lt;one of "hw-address", "duid", "circuit-id", "client-id" and "flex-id"&gt;,
-        "identifier": &lt;string&gt;
+        "count": 1
     }
 }</screen>
-The host reservation can be identified by either (subnet-id, ip-address) pair or a triplet of (subnet-id, identifier-type, identifier).</para>
-
-<para>Response syntax:
-  <screen>{
-    "result": &lt;integer&gt;,
-    "text": &lt;string&gt;
-}
-</screen>
 Result is an integer representation of the status. Currently supported statuses are:
 <itemizedlist>
   <listitem><para>0 - success</para></listitem>
@@ -2549,204 +2617,130 @@ Result is an integer representation of the status. Currently supported statuses
 </para>
 
 </section>
-<!-- end of reservation-del -->
+<!-- end of remote-global-parameter4-del -->
 
-<!-- start of reservation-get -->
-<section xml:id="reference-reservation-get">
-<title>reservation-get reference</title>
-<para xml:id="ref-reservation-get"><command>reservation-get</command> - Attempts to retrieve an existing host reservation</para>
+<!-- start of remote-global-parameter4-get -->
+<section xml:id="reference-remote-global-parameter4-get">
+<title>remote-global-parameter4-get reference</title>
+<para xml:id="ref-remote-global-parameter4-get"><command>remote-global-parameter4-get</command> - This command is used to fetch selected global parameter for the server from the specified database.</para>
 
-<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
 
-<para>Availability: 1.2.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-reservation-get"/></para>
+<para>Description and examples: See <xref linkend="command-remote-global-parameter4-get"/></para>
 
 <para>Command syntax:
   <screen>{
-    "command": "reservation-get",
+    "command": "remote-global-parameter4-get"
     "arguments": {
-        "subnet-id": &lt;integer&gt;,
-        "identifier-type": &lt;string with one value out of: hw-address|duid|circuit-id|client-id|flex-id&gt;,
-        "identifier": &lt;string&gt;;
+        "parameters": [ &lt;parameter name&gt; ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
     }
 }</screen>
-The host reservation can be identified by either (subnet-id, ip-address) pair or a triplet of (subnet-id, identifier-type, identifier).</para>
+This command carries a list including exactly one name of the parameter to be fetched.</para>
 
 <para>Response syntax:
   <screen>{
-    "result": &lt;integer&gt;,
-    "text": &lt;string&gt;,
+    "result": 0,
+    "text": "DHCPv4 global parameter found.",
     "arguments": {
-        "boot-file-name": &lt;string&gt;,
-        "comment": &lt;string&gt;
-        "client-id": &lt;string&gt;,
-        "circuit-id": &lt;string&gt;,
-        "duid": &lt;string&gt;,
-        "flex-id": &lt;string&gt;,
-        "ip-address": &lt;string (IPv4 address)&gt;,
-        "ip-addresses": [ &lt;comma separated strings&gt; ],
-        "hw-address": &lt;string&gt;,
-        "hostname": &lt;string&gt;,
-        "next-server": &lt;string (IPv4 address)&gt;,
-        "option-data-list": [ &lt;comma separated structures defining options&gt; ],
-        "prefixes": [ &lt;comma separated IPv6 prefixes&gt; ],
-        "reservation-client-classes": [ &lt;comma separated strings&gt; ],
-        "server-hostname": &lt;string&gt;,
-        "subnet-id": &lt;integer&gt;,
-        "user-context": &lt;any valid JSON&gt;,
+        "parameters": {
+            &lt;parameter name&gt;: &lt;parameter value&gt;,
+            "metadata": {
+                "server-tag": &lt;server tag&gt;
+            }
+        },
+        "count": 1
     }
 }</screen>
-Arguments object appear only if a host is found. Many fields in the arguments
-object appear only if specific field is set.</para>
+The returned response contains a map with a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is included and it provides database specific information associated with the returned object.</para>
 
 </section>
-<!-- end of reservation-get -->
+<!-- end of remote-global-parameter4-get -->
 
-<!-- start of reservation-get-all -->
-<section xml:id="reference-reservation-get-all">
-<title>reservation-get-all reference</title>
-<para xml:id="ref-reservation-get-all"><command>reservation-get-all</command> - Retrieve all host reservations for a specified subnet.</para>
+<!-- start of remote-global-parameter4-get-all -->
+<section xml:id="reference-remote-global-parameter4-get-all">
+<title>remote-global-parameter4-get-all reference</title>
+<para xml:id="ref-remote-global-parameter4-get-all"><command>remote-global-parameter4-get-all</command> - This command is used to fetch all global parameters for the server from the specified database.</para>
 
-<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
 
-<para>Availability: 1.6.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-reservation-get-all"/></para>
+<para>Description and examples: See <xref linkend="command-remote-global-parameter4-get-all"/></para>
 
 <para>Command syntax:
   <screen>{
-    "command": "reservation-get-all",
+    "command": "remote-global-parameter4-get-all"
     "arguments": {
-        "subnet-id": &lt;integer&gt;
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
     }
 }</screen>
-Host reservations can be identified by subnet-id.</para>
+This command contains no arguments besides the optional <command>remote</command>.</para>
 
 <para>Response syntax:
   <screen>{
-    "result": &lt;integer&gt;,
-    "text": &lt;string&gt;,
+    "result": 0,
+    "text": "DHCPv4 global parameters found.",
     "arguments": {
-        "hosts": [
-            {
-                "boot-file-name": &lt;string&gt;,
-                "comment": &lt;string&gt;
-                "client-id": &lt;string&gt;,
-                "circuit-id": &lt;string&gt;,
-                "duid": &lt;string&gt;,
-                "flex-id": &lt;string&gt;,
-                "ip-address": &lt;string (IPv4 address)&gt;,
-                "ip-addresses": [ &lt;comma separated strings&gt; ],
-                "hw-address": &lt;string&gt;,
-                "hostname": &lt;string&gt;,
-                "next-server": &lt;string (IPv4 address)&gt;,
-                "option-data-list": [ &lt;comma separated structures defining options&gt; ],
-                "prefixes": [ &lt;comma separated IPv6 prefixes&gt; ],
-                "reservation-client-classes": [ &lt;comma separated strings&gt; ],
-                "server-hostname": &lt;string&gt;,
-                "subnet-id": &lt;integer&gt;,
-                "user-context": &lt;any valid JSON&gt;,
+        "parameters": [
+            {
+                &lt;first parameter name&gt;: &lt;first parameter value&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
             },
-            ...
-        ]
+            {
+                &lt;second parameter name&gt;: &lt;second parameter value&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
     }
 }</screen>
-
-The reservation-get-all command may result in very large responses.</para>
+The returned response contains a list of maps. Each map contains a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is appended to each parameter and it provides database specific information associated with the returned objects.</para>
 
 </section>
-<!-- end of reservation-get-all -->
+<!-- end of remote-global-parameter4-get-all -->
 
-<!-- start of reservation-get-page -->
-<section xml:id="reference-reservation-get-page">
-<title>reservation-get-page reference</title>
-<para xml:id="ref-reservation-get-page"><command>reservation-get-page</command> - Retrieve all host reservations for a specified subnet by pages.</para>
+<!-- start of remote-global-parameter4-set -->
+<section xml:id="reference-remote-global-parameter4-set">
+<title>remote-global-parameter4-set reference</title>
+<para xml:id="ref-remote-global-parameter4-set"><command>remote-global-parameter4-set</command> - This command is used to create or update one more global parameters in the configuration database.</para>
 
-<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
 
-<para>Availability: 1.6.0 (<link linkend="commands-host_cmds-lib">host_cmds</link> hook) at the exception of the Cassandra host backend</para>
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-reservation-get-page"/></para>
+<para>Description and examples: See <xref linkend="command-remote-global-parameter4-set"/></para>
 
 <para>Command syntax:
   <screen>{
-    "command": "reservation-get-page",
+    "command": "remote-global-parameter4-set"
     "arguments": {
-        "subnet-id": &lt;integer&gt;,
-        "limit": &lt;integer&gt;,
-        "source-index": &lt;integer&gt;,
-        "from": &lt;integer&gt;
+        "parameters": {
+            &lt;first parameter name&gt;: &lt;first parameter value&gt;,
+            &lt;second parameter name&gt;: &lt;second parameter value&gt;
+        },
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
     }
 }</screen>
-Returned host reservations are from the specified subnet. Page size is
-limited by the limit parameter. Start of the page is given by the optional
-source index (default 0 i.e. configuration file) and from host id (default
-0).
-</para>
+This command carries multiple global parameters with their values. Care should be taken when specifying more than one parameter because in some cases only a subset of the parameters may be successfully stored in the database and other parameters may fail to be stored. In such cases the <command>remote-global-parameter4-get-all</command> may be useful to verify the contents of the database after the update.</para>
 
 <para>Response syntax:
   <screen>{
-    "result": &lt;integer&gt;,
-    "text": &lt;string&gt;,
-    "arguments": {
-        "source-index": &lt;string&gt;,
-        "count": &lt;string&gt;,
-        "next": &lt;integer&gt;,
-        "hosts": [
-            {
-                "boot-file-name": &lt;string&gt;,
-                "comment": &lt;string&gt;
-                "client-id": &lt;string&gt;,
-                "circuit-id": &lt;string&gt;,
-                "duid": &lt;string&gt;,
-                "flex-id": &lt;string&gt;,
-                "ip-address": &lt;string (IPv4 address)&gt;,
-                "ip-addresses": [ &lt;comma separated strings&gt; ],
-                "hw-address": &lt;string&gt;,
-                "hostname": &lt;string&gt;,
-                "next-server": &lt;string (IPv4 address)&gt;,
-                "option-data-list": [ &lt;comma separated structures defining options&gt; ],
-                "prefixes": [ &lt;comma separated IPv6 prefixes&gt; ],
-                "reservation-client-classes": [ &lt;comma separated strings&gt; ],
-                "server-hostname": &lt;string&gt;,
-                "subnet-id": &lt;integer&gt;,
-                "user-context": &lt;any valid JSON&gt;,
-            },
-            ...
-        ]
-    }
-}</screen>
-The source index and the next host id should be used getting the next page.
-After the last page the result is 3 (empty).
-</para>
-</section>
-<!-- end of reservation-get-page -->
-
-<!-- start of shutdown -->
-<section xml:id="reference-shutdown">
-<title>shutdown reference</title>
-<para xml:id="ref-shutdown"><command>shutdown</command> - The shutdown command instructs the server to initiate its shutdown procedure.</para>
-
-<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command>, <command><link linkend="commands-kea-dhcp-ddns">kea-dhcp-ddns</link></command>, <command><link linkend="commands-kea-ctrl-agent">kea-ctrl-agent</link></command></para>
-
-<para>Availability: 1.0.0 (built-in)</para>
-
-<para>Description and examples: See <xref linkend="command-shutdown"/></para>
-
-<para>Command syntax:
-  <screen>{
-    "command": "shutdown"
+    "result": 0,
+    "text": "DHCPv4 global parameter(s) successfully set."
 }</screen>
-The server will respond with a confirmation that the shutdown
-                    procedure has been initiated.</para>
-
-<para>Response syntax:
-  <screen>{
-    "result": &lt;integer&gt;,
-    "text": &lt;string&gt;
-}
-</screen>
 Result is an integer representation of the status. Currently supported statuses are:
 <itemizedlist>
   <listitem><para>0 - success</para></listitem>
@@ -2757,44 +2751,38 @@ Result is an integer representation of the status. Currently supported statuses
 </para>
 
 </section>
-<!-- end of shutdown -->
+<!-- end of remote-global-parameter4-set -->
 
-<!-- start of stat-lease4-get -->
-<section xml:id="reference-stat-lease4-get">
-<title>stat-lease4-get reference</title>
-<para xml:id="ref-stat-lease4-get"><command>stat-lease4-get</command> - The stat-lease4-get command fetches lease statistics for a range
-              of known IPv4 subnets.</para>
+<!-- start of remote-global-parameter6-del -->
+<section xml:id="reference-remote-global-parameter6-del">
+<title>remote-global-parameter6-del reference</title>
+<para xml:id="ref-remote-global-parameter6-del"><command>remote-global-parameter6-del</command> - This command is used to delete a global DHCPv6 parameter from the configuration database. The server will use the value specified in the configuration file or a default value (if the parameter is not specified in the configuration file) after deleting the parameter from the database.</para>
 
-<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
 
-<para>Availability: 1.4.0 (<link linkend="commands-stat_cmds-lib">stat_cmds</link>  hook)</para>
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-stat-lease4-get"/></para>
+<para>Description and examples: See <xref linkend="command-remote-global-parameter6-del"/></para>
 
 <para>Command syntax:
   <screen>{
-  "command": "stat-lease4-get"
+    "command": "remote-global-parameter6-del",
+    "arguments": {
+        "parameters": [ &lt;parameter name&gt; ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
 }</screen>
-</para>
+This command carries the list including exactly one name of the parameter to be deleted.</para>
 
 <para>Response syntax:
   <screen>{
     "result": 0,
-    "text": "stat-lease4-get: 2 rows found",
+    "text": "DHCPv6 global parameter(s) deleted.",
     "arguments": {
-      "result-set": {
-        "columns": [ "subnet-id",
-                       "total-addresses",
-                       "assigned-addresses",
-                       "declined-addresses" ]
-        "rows": [
-          [ 10, 256, 111, 0 ],
-          [ 20, 4098, 2034, 4 ]
-        ],
-      "timestamp": "2018-05-04 15:03:37.000000"
-      }
-    }
-  }</screen>
+        "count": 1
+    }</screen>
 Result is an integer representation of the status. Currently supported statuses are:
 <itemizedlist>
   <listitem><para>0 - success</para></listitem>
@@ -2805,19 +2793,2206 @@ Result is an integer representation of the status. Currently supported statuses
 </para>
 
 </section>
-<!-- end of stat-lease4-get -->
+<!-- end of remote-global-parameter6-del -->
 
-<!-- start of stat-lease6-get -->
-<section xml:id="reference-stat-lease6-get">
-<title>stat-lease6-get reference</title>
-<para xml:id="ref-stat-lease6-get"><command>stat-lease6-get</command> - The stat-lease6-get command fetches lease statistics for a range
-              of known IPv6 subnets.</para>
+<!-- start of remote-global-parameter6-get -->
+<section xml:id="reference-remote-global-parameter6-get">
+<title>remote-global-parameter6-get reference</title>
+<para xml:id="ref-remote-global-parameter6-get"><command>remote-global-parameter6-get</command> - This command is used to fetch selected global parameter for the server from the specified database.</para>
 
 <para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
 
-<para>Availability: 1.4.0 (<link linkend="commands-stat_cmds-lib">stat_cmds</link>  hook)</para>
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
 
-<para>Description and examples: See <xref linkend="command-stat-lease4-get"/></para>
+<para>Description and examples: See <xref linkend="command-remote-global-parameter6-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-global-parameter6-get"
+    "arguments": {
+        "parameters": [ &lt;parameter name&gt; ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command carries a list including exactly one name of the parameter to be fetched.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv6 global parameter found.",
+    "arguments": {
+        "parameters": {
+            &lt;parameter name&gt;: &lt;parameter value&gt;,
+            "metadata": {
+                "server-tag": &lt;server tag&gt;
+            }
+        },
+        "count": 1
+    }
+}</screen>
+The returned response contains a map with a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is included and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-global-parameter6-get -->
+
+<!-- start of remote-global-parameter6-get-all -->
+<section xml:id="reference-remote-global-parameter6-get-all">
+<title>remote-global-parameter6-get-all reference</title>
+<para xml:id="ref-remote-global-parameter6-get-all"><command>remote-global-parameter6-get-all</command> - This command is used to fetch all global parameters for the server from the specified database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-global-parameter6-get-all"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-global-parameter6-get-all"
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command contains no arguments besides the optional <command>remote</command>.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv6 global parameters found.",
+    "arguments": {
+        "parameters": [
+            {
+                &lt;first parameter name&gt;: &lt;first parameter value&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                &lt;second parameter name&gt;: &lt;second parameter value&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains a list of maps. Each map contains a global parameter name/value pair. The value may be a JSON string, integer, real or boolean. The metadata is appended to each parameter and it provides database specific information associated with the returned objects.</para>
+
+</section>
+<!-- end of remote-global-parameter6-get-all -->
+
+<!-- start of remote-global-parameter6-set -->
+<section xml:id="reference-remote-global-parameter6-set">
+<title>remote-global-parameter6-set reference</title>
+<para xml:id="ref-remote-global-parameter6-set"><command>remote-global-parameter6-set</command> - This command is used to create or update one more global DHCP parameters in the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-global-parameter6-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-global-parameter6-set"
+    "arguments": {
+        "parameters": {
+            &lt;first parameter name&gt;: &lt;first parameter value&gt;,
+            &lt;second parameter name&gt;: &lt;second parameter value&gt;
+        },
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command carries multiple global parameters with their values. Care should be taken when specifying more than one parameter because in some cases only a subset of the parameters may be successfully stored in the database and other parameters may fail to be stored. In such cases the <command>remote-global-parameter6-get-all</command> may be useful to verify the contents of the database after the update.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv6 global parameter(s) successfully set."
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-global-parameter6-set -->
+
+<!-- start of remote-network4-del -->
+<section xml:id="reference-remote-network4-del">
+<title>remote-network4-del reference</title>
+<para xml:id="ref-remote-network4-del"><command>remote-network4-del</command> - This command is used to delete an IPv4 shared network from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network4-del"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network4-del",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;shared network name&gt;
+            }
+        ],
+        "subnets-action": "keep" | "delete",
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one name of the shared network to be deleted. The <command>subnets-action</command> denotes whether the subnets in this shared network should be deleted or not.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 IPv4 shared network(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-network4-del -->
+
+<!-- start of remote-network4-get -->
+<section xml:id="reference-remote-network4-get">
+<title>remote-network4-get reference</title>
+<para xml:id="ref-remote-network4-get"><command>remote-network4-get</command> - This command is used to fetch selected IPv4 shared network for the server from the specified database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network4-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network4-get"
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;shared network name&gt;
+            }
+        ],
+        "subnets-include": "full" | "no",
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one name of the shared network to be returned. The <command>subnets-include</command> optional parameter allows for specifying whether the subnets belonging to the shared network should also be returned.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv4 shared network found.",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;shared network name&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                },
+                &lt;the rest of the shared network information, potentially including subnets&gt;
+            }
+        ],
+        "count": 1
+    }
+}</screen>
+If the subnets are returned with the shared network they are carried in the <command>subnet4</command> list within the shared network definition. The metadata is included in the returned shared network definition and it provides the database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-network4-get -->
+
+<!-- start of remote-network4-list -->
+<section xml:id="reference-remote-network4-list">
+<title>remote-network4-list reference</title>
+<para xml:id="ref-remote-network4-list"><command>remote-network4-list</command> - This command is used to fetch a list of all IPv4 shared networks from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network4-list"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network4-list"
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command contains no arguments besides the optional <command>remote</command>.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 IPv4 shared network(s) found.",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;first shared network name&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                "name": &lt;second shared network name&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains the list of maps. Each map contains the shared network name and the metadata which provides database specific information associated with the shared network. The returned list does not contain full definitions of the shared networks. Use <command>remote-network4-get</command> to fetch the full information about the selected shared networks.</para>
+
+</section>
+<!-- end of remote-network4-list -->
+
+<!-- start of remote-network4-set -->
+<section xml:id="reference-remote-network4-set">
+<title>remote-network4-set reference</title>
+<para xml:id="ref-remote-network4-set"><command>remote-network4-set</command> - This command is used to create or replace an IPv4 shared network in the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network4-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network4-set",
+    "arguments": {
+        "shared-networks": [
+            {
+                &lt;shared network specification excluding subnets list&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must contain exactly one shared network specification. It must not contain subnets ("subnet4" parameter). The subnets are added to the shared network using <command>remote-subnet4-set</command> command.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv4 shared network successfully set."
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-network4-set -->
+
+<!-- start of remote-network6-del -->
+<section xml:id="reference-remote-network6-del">
+<title>remote-network6-del reference</title>
+<para xml:id="ref-remote-network6-del"><command>remote-network6-del</command> - This command is used to delete an IPv6 shared network from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network6-del"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network6-del",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;shared network name&gt;
+            }
+        ],
+        "subnets-action": "keep" | "delete",
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one name of the shared network to be deleted. The <command>subnets-action</command> denotes whether the subnets in this shared network should be deleted or not.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 IPv6 shared network(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-network6-del -->
+
+<!-- start of remote-network6-get -->
+<section xml:id="reference-remote-network6-get">
+<title>remote-network6-get reference</title>
+<para xml:id="ref-remote-network6-get"><command>remote-network6-get</command> - This command is used to fetch selected IPv6 shared network for the server from the specified database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network6-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network6-get"
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;shared network name&gt;
+            }
+        ],
+        "subnets-include": "full" | "no",
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one name of the shared network to be returned. The <command>subnets-include</command> optional parameter allows for specifying whether the subnets belonging to the shared network should also be returned.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv6 shared network found.",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;shared network name&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                },
+                &lt;the rest of the shared network information, potentially including subnets&gt;
+            }
+        ],
+        "count": 1
+    }
+}</screen>
+If the subnets are returned with the shared network they are carried in the <command>subnet6</command> list within the shared network definition. The metadata is included in the returned shared network definition and it provides the database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-network6-get -->
+
+<!-- start of remote-network6-list -->
+<section xml:id="reference-remote-network6-list">
+<title>remote-network6-list reference</title>
+<para xml:id="ref-remote-network6-list"><command>remote-network6-list</command> - This command is used to fetch a list of all IPv6 shared networks from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network6-list"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network6-list"
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command contains no arguments besides the optional <command>remote</command>.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 IPv6 shared network(s) found.",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": &lt;first shared network name&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                "name": &lt;second shared network name&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains the list of maps. Each map contains the shared network name and the metadata which provides database specific information associated with the shared network. The returned list does not contain full definitions of the shared networks. Use <command>remote-network6-get</command> to fetch the full information about the selected shared networks.</para>
+
+</section>
+<!-- end of remote-network6-list -->
+
+<!-- start of remote-network6-set -->
+<section xml:id="reference-remote-network6-set">
+<title>remote-network6-set reference</title>
+<para xml:id="ref-remote-network6-set"><command>remote-network6-set</command> - This command is used to create or replace an IPv6 shared network in the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-network6-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-network6-set",
+    "arguments": {
+        "shared-networks": [
+            {
+                &lt;shared network specification excluding subnets list&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must contain exactly one shared network specification. It must not contain subnets ("subnet6" parameter). The subnets are added to the shared network using <command>remote-subnet6-set</command> command.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv6 shared network successfully set."
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-network6-set -->
+
+<!-- start of remote-option-def4-del -->
+<section xml:id="reference-remote-option-def4-del">
+<title>remote-option-def4-del reference</title>
+<para xml:id="ref-remote-option-def4-del"><command>remote-option-def4-del</command> - This command is used to delete a DHCPv4 option definition from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def4-del"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def4-del",
+    "arguments": {
+        "option-defs": [ {
+            "code": &lt;option code&gt;,
+            "space": &lt;option space
+        } ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one option definition specification comprising an option name and code.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 DHCPv4 option definition(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option-def4-del -->
+
+<!-- start of remote-option-def4-get -->
+<section xml:id="reference-remote-option-def4-get">
+<title>remote-option-def4-get reference</title>
+<para xml:id="ref-remote-option-def4-get"><command>remote-option-def4-get</command> - This command is used to fetch a DHCPv4 option definition from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def4-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def4-get",
+    "arguments": {
+        "option-defs": [
+            {
+                "code": &lt;option code&gt;,
+                "space": &lt;option space&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The desired option definition is identified by the pair of the option code/space values.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv4 option definition found.",
+    "arguments": {
+        "option-defs": [
+            {
+                &lt;option definition&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 1
+    }
+}</screen>
+The metadata is included and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-option-def4-get -->
+
+<!-- start of remote-option-def4-get-all -->
+<section xml:id="reference-remote-option-def4-get-all">
+<title>remote-option-def4-get-all reference</title>
+<para xml:id="ref-remote-option-def4-get-all"><command>remote-option-def4-get-all</command> - This command is used to fetch all DHCPv4 option definitions from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def4-get-all"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def4-get-all"
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command contains no arguments besides the optional <command>remote</command>.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 DHCPv4 option definition(s) found.",
+    "arguments": {
+        "option-defs": [
+            {
+                &lt;first option definition&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                &lt;second option definition&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains a list of maps. Each map contains an option definition specification and the metadata including database specific information associated with the returned objects.</para>
+
+</section>
+<!-- end of remote-option-def4-get-all -->
+
+<!-- start of remote-option-def4-set -->
+<section xml:id="reference-remote-option-def4-set">
+<title>remote-option-def4-set reference</title>
+<para xml:id="ref-remote-option-def4-set"><command>remote-option-def4-set</command> - This command is used to create or replace DHCPv4 option definition in the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def4-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def4-set",
+    "arguments": {
+        "option-defs": [
+            {
+                &lt;option definition specification&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must contain exactly one option definition specification.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv4 option definition set."
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option-def4-set -->
+
+<!-- start of remote-option-def6-del -->
+<section xml:id="reference-remote-option-def6-del">
+<title>remote-option-def6-del reference</title>
+<para xml:id="ref-remote-option-def6-del"><command>remote-option-def6-del</command> - This command is used to delete a DHCPv6 option definition from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def6-del"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def6-del",
+    "arguments": {
+        "option-defs": [
+            {
+                "code": &lt;option code&gt;,
+                "space": &lt;option space
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one option definition specification comprising an option name and code.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 DHCPv6 option definition(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option-def6-del -->
+
+<!-- start of remote-option-def6-get -->
+<section xml:id="reference-remote-option-def6-get">
+<title>remote-option-def6-get reference</title>
+<para xml:id="ref-remote-option-def6-get"><command>remote-option-def6-get</command> - This command is used to fetch a DHCPv6 option definition from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def6-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def6-get",
+    "arguments": {
+        "option-defs": [
+            {
+                "code": &lt;option code&gt;,
+                "space": &lt;option space&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The desired option definition is identified by the pair of the option code/space values.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv6 option definition found.",
+    "arguments": {
+        "option-defs": [
+            {
+                &lt;option definition&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 1
+    }
+}</screen>
+The metadata is included and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-option-def6-get -->
+
+<!-- start of remote-option-def6-get-all -->
+<section xml:id="reference-remote-option-def6-get-all">
+<title>remote-option-def6-get-all reference</title>
+<para xml:id="ref-remote-option-def6-get-all"><command>remote-option-def6-get-all</command> - This command is used to fetch all DHCPv6 option definitions from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def6-get-all"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def6-get-all"
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command contains no arguments besides the optional <command>remote</command>.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 DHCPv6 option definition(s) found.",
+    "arguments": {
+        "option-defs": [
+            {
+                &lt;first option definition&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                &lt;second option definition&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains a list of maps. Each map contains an option definition specification and the metadata including database specific information associated with the returned objects.</para>
+
+</section>
+<!-- end of remote-option-def6-get-all -->
+
+<!-- start of remote-option-def6-set -->
+<section xml:id="reference-remote-option-def6-set">
+<title>remote-option-def6-set reference</title>
+<para xml:id="ref-remote-option-def6-set"><command>remote-option-def6-set</command> - This command is used to create or replace DHCPv6 option definition in the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option-def6-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option-def6-set",
+    "arguments": {
+        "option-defs": [
+            {
+                &lt;option definition specification&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must contain exactly one option definition specification.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv6 option definition set."
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option-def6-set -->
+
+<!-- start of remote-option4-global-del -->
+<section xml:id="reference-remote-option4-global-del">
+<title>remote-option4-global-del reference</title>
+<para xml:id="ref-remote-option4-global-del"><command>remote-option4-global-del</command> - This command is used to delete a DHCPv4 global option from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option4-global-del"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option4-global-del",
+    "arguments": {
+        "options": [
+            {
+                "code": &lt;option code&gt;
+                "space": &lt;option space&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one option specification comprising an option name and code.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 DHCPv4 option(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option4-global-del -->
+
+<!-- start of remote-option4-global-get -->
+<section xml:id="reference-remote-option4-global-get">
+<title>remote-option4-global-get reference</title>
+<para xml:id="ref-remote-option4-global-get"><command>remote-option4-global-get</command> - This command is used to fetch a global DHCPv4 option for the server from the specified database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option4-global-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option4-global-get",
+    "arguments": {
+        "options": [
+            {
+                "code": &lt;option code&gt;,
+                "space": &lt;option space&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+}</screen>
+The option is identified by the pair of option code/space values.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv4 option in found.",
+    "arguments": {
+        "options": [
+            {
+                &lt;option information&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ]
+    }
+}</screen>
+The metadata is included and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-option4-global-get -->
+
+<!-- start of remote-option4-global-get-all -->
+<section xml:id="reference-remote-option4-global-get-all">
+<title>remote-option4-global-get-all reference</title>
+<para xml:id="ref-remote-option4-global-get-all"><command>remote-option4-global-get-all</command> - This command is used to fetch all DHCPv4 global options for the server from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option4-global-get-all"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option4-global-get-all",
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command takes no arguments besides the optional <command>remote</command> map.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 DHCPv4 option(s) found.",
+    "arguments": {
+        "options": [
+            {
+                &lt;first option specification&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                &lt;second option specification&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains a list of maps. Each map contains a global option specification and the metadata including database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-option4-global-get-all -->
+
+<!-- start of remote-option4-global-set -->
+<section xml:id="reference-remote-option4-global-set">
+<title>remote-option4-global-set reference</title>
+<para xml:id="ref-remote-option4-global-set"><command>remote-option4-global-set</command> - This command is used to create or replace a DHCPv4 global option in the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option4-global-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option4-global-set",
+    "arguments": {
+        "options": [
+            {
+                &lt;global option specification&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must cotain exactly one option specification.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv4 option set.",
+    "arguments": {
+        "options": [
+            {
+                "code": &lt;option code&gt;,
+                "space": &lt;option space&gt;
+            }
+        ]
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option4-global-set -->
+
+<!-- start of remote-option6-global-del -->
+<section xml:id="reference-remote-option6-global-del">
+<title>remote-option6-global-del reference</title>
+<para xml:id="ref-remote-option6-global-del"><command>remote-option6-global-del</command> - This command is used to delete a DHCPv6 global option from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option6-global-del"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option6-global-del",
+    "arguments": {
+        "options": [
+            {
+                "code": &lt;option code&gt;
+                "space": &lt;option space&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one option specification comprising an option name and code.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 DHCPv6 option(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option6-global-del -->
+
+<!-- start of remote-option6-global-get -->
+<section xml:id="reference-remote-option6-global-get">
+<title>remote-option6-global-get reference</title>
+<para xml:id="ref-remote-option6-global-get"><command>remote-option6-global-get</command> - This command is used to delete a DHCPv6 global option from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option6-global-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option6-global-get",
+    "arguments": {
+        "options": [
+            {
+                "code": &lt;option code&gt;,
+                "space": &lt;option space&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+}</screen>
+The option is identified by the pair of option code/space values.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv6 option found.",
+    "arguments": {
+        "options": [
+            {
+                &lt;option information&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ]
+    }
+}</screen>
+The metadata is included and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-option6-global-get -->
+
+<!-- start of remote-option6-global-get-all -->
+<section xml:id="reference-remote-option6-global-get-all">
+<title>remote-option6-global-get-all reference</title>
+<para xml:id="ref-remote-option6-global-get-all"><command>remote-option6-global-get-all</command> - This command is used to fetch all DHCPv6 global options for the server from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option6-global-get-all"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option6-global-get-all",
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command takes no arguments besides the optional <command>remote</command> map.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 DHCPv6 option(s) found.",
+    "arguments": {
+        "options": [
+            {
+                &lt;first option specification&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                &lt;second option specification&gt;,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains a list of maps. Each map contains a global option specification and the metadata including database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-option6-global-get-all -->
+
+<!-- start of remote-option6-global-set -->
+<section xml:id="reference-remote-option6-global-set">
+<title>remote-option6-global-set reference</title>
+<para xml:id="ref-remote-option6-global-set"><command>remote-option6-global-set</command> - This command is used to create or replace a DHCPv6 global option in the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-option6-global-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-option6-global-set",
+    "arguments": {
+        "options": [
+            {
+                &lt;global option specification&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must cotain exactly one option specification.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "DHCPv6 option set.",
+    "arguments": {
+        "options": [
+            {
+                "code": &lt;option code&gt;,
+                "space": &lt;option space&gt;
+            }
+        ]
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-option6-global-set -->
+
+<!-- start of remote-subnet4-del-by-id -->
+<section xml:id="reference-remote-subnet4-del-by-id">
+<title>remote-subnet4-del-by-id reference</title>
+<para xml:id="ref-remote-subnet4-del-by-id"><command>remote-subnet4-del-by-id</command> - This command is used to delete an IPv4 subnet by ID from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet4-del-by-id"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet4-del-by-id",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;subnet identifier&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one id of the subnet to be deleted.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 IPv4 subnet(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-subnet4-del-by-id -->
+
+<!-- start of remote-subnet4-del-by-prefix -->
+<section xml:id="reference-remote-subnet4-del-by-prefix">
+<title>remote-subnet4-del-by-prefix reference</title>
+<para xml:id="ref-remote-subnet4-del-by-prefix"><command>remote-subnet4-del-by-prefix</command> - This command is used to delete an IPv4 subnet by prefix from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet4-del-by-prefix"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet4-del-by-prefix",
+    "arguments": {
+        "subnets": [
+            {
+                "subnet": &lt;subnet prefix&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one prefix of the subnet to be deleted.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 IPv4 subnet(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-subnet4-del-by-prefix -->
+
+<!-- start of remote-subnet4-get-by-id -->
+<section xml:id="reference-remote-subnet4-get-by-id">
+<title>remote-subnet4-get-by-id reference</title>
+<para xml:id="ref-remote-subnet4-get-by-id"><command>remote-subnet4-get-by-id</command> - This command is used to fetch selected IPv4 subnet by ID for the server from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet4-get-by-id"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet4-get-by-id"
+    "arguments": {
+        "subnets": [ {
+            "id": &lt;subnet identifier&gt;
+        } ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one id of the subnet to be returned.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv4 subnet found.",
+    "arguments": {
+        "subnets": [ {
+            "id": &lt;subnet identifier&gt;
+            "subnet": &lt;subnet prefix&gt;,
+            "shared-network-name": &lt;shared network name&gt; | null,
+            "metadata": {
+                "server-tag": &lt;server tag&gt;
+            },
+            &lt;the rest of the subnet specification here&gt;
+        } ],
+        "count": 1
+    }
+}</screen>
+If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-subnet4-get-by-id -->
+
+<!-- start of remote-subnet4-get-by-prefix -->
+<section xml:id="reference-remote-subnet4-get-by-prefix">
+<title>remote-subnet4-get-by-prefix reference</title>
+<para xml:id="ref-remote-subnet4-get-by-prefix"><command>remote-subnet4-get-by-prefix</command> - This command is used to fetch selected IPv4 subnet by prefix from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet4-get-by-prefix"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet4-get-by-prefix"
+    "arguments": {
+        "subnets": [ {
+            "subnet": &lt;subnet prefix&gt;
+        } ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one prefix of the subnet to be returned.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv4 subnet found.",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;subnet identifier&gt;
+                "subnet": &lt;subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                },
+                &lt;the rest of the subnet specification here&gt;
+            }
+        ],
+        "count": 1
+    }
+}</screen>
+If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-subnet4-get-by-prefix -->
+
+<!-- start of remote-subnet4-list -->
+<section xml:id="reference-remote-subnet4-list">
+<title>remote-subnet4-list reference</title>
+<para xml:id="ref-remote-subnet4-list"><command>remote-subnet4-list</command> - This command is used to fetch a list of all IPv4 subnets from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet4-list"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet4-list"
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes no arguments besides the optional <command>remote</command> map.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 IPv4 subnets found.",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;first subnet identifier&gt;,
+                "subnet": &lt;first subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                "id": &lt;second subnet identifier&gt;,
+                "subnet": &lt;second subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains a list of maps. Each map contains a subnet identifier, prefix and shared network name to which the subnet belongs. If the subnet does not belong to a shared netork the name is null. The metadata includes database specific information associated with the subnets. The returned list does not contain full subnet definitions. Use <command>remote-subnet4-get</command> to fetch the full information about the selected subnets.</para>
+
+</section>
+<!-- end of remote-subnet4-list -->
+
+<!-- start of remote-subnet4-set -->
+<section xml:id="reference-remote-subnet4-set">
+<title>remote-subnet4-set reference</title>
+<para xml:id="ref-remote-subnet4-set"><command>remote-subnet4-set</command> - This command is used to create or replace an IPv4 subnet the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet4-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet4-set",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;subnet identifier&gt;,
+                "subnet": &lt;subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                &lt;the rest of the subnet specification here&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must contain exactly one subnet specification. The <command>shared-network-name</command> parameter is required for these commands. It associates the subnet with the shared network by its name. If the subnet must not belong to any shared network (global subnet), the <command>null</command> value must be specified for the shared network name.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv4 subnet successfully set.",
+    "arguments": {
+        "id": &lt;subnet identifier&gt;,
+        "subnet": &lt;subnet prefix&gt;
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-subnet4-set -->
+
+<!-- start of remote-subnet6-del-by-id -->
+<section xml:id="reference-remote-subnet6-del-by-id">
+<title>remote-subnet6-del-by-id reference</title>
+<para xml:id="ref-remote-subnet6-del-by-id"><command>remote-subnet6-del-by-id</command> - This command is used to delete an IPv6 subnet by ID from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet6-del-by-id"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet6-del-by-id",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;subnet identifier&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one id of the subnet to be deleted.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 IPv6 subnet(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-subnet6-del-by-id -->
+
+<!-- start of remote-subnet6-del-by-prefix -->
+<section xml:id="reference-remote-subnet6-del-by-prefix">
+<title>remote-subnet6-del-by-prefix reference</title>
+<para xml:id="ref-remote-subnet6-del-by-prefix"><command>remote-subnet6-del-by-prefix</command> - This command is used to delete an IPv6 subnet by prefix from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet6-del-by-prefix"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet6-del-by-prefix",
+    "arguments": {
+        "subnets": [
+            {
+                "subnet": &lt;subnet prefix&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one prefix of the subnet to be deleted.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "1 IPv6 subnet(s) deleted.",
+    "arguments": {
+        "count": 1
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-subnet6-del-by-prefix -->
+
+<!-- start of remote-subnet6-get-by-id -->
+<section xml:id="reference-remote-subnet6-get-by-id">
+<title>remote-subnet6-get-by-id reference</title>
+<para xml:id="ref-remote-subnet6-get-by-id"><command>remote-subnet6-get-by-id</command> - This command is used to fetch selected IPv6 subnet by ID for the server from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet6-get-by-id"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet6-get-by-id"
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;subnet identifier&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one id of the subnet to be returned.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv6 subnet found.",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;subnet identifier&gt;
+                "subnet": &lt;subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                },
+                &lt;the rest of the subnet specification here&gt;
+            }
+        ],
+        "count": 1
+    }
+}</screen>
+If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-subnet6-get-by-id -->
+
+<!-- start of remote-subnet6-get-by-prefix -->
+<section xml:id="reference-remote-subnet6-get-by-prefix">
+<title>remote-subnet6-get-by-prefix reference</title>
+<para xml:id="ref-remote-subnet6-get-by-prefix"><command>remote-subnet6-get-by-prefix</command> - This command is used to fetch selected IPv6 subnet by prefix from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet6-get-by-prefix"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet4-get-by-prefix"
+    "arguments": {
+        "subnets": [
+            {
+                "subnet": &lt;subnet prefix&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes a list with exactly one prefix of the subnet to be returned.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv6 subnet found.",
+    "arguments": {
+        "subnets": [ {
+            "id": &lt;subnet identifier&gt;
+            "subnet": &lt;subnet prefix&gt;,
+            "shared-network-name": &lt;shared network name&gt; | null,
+            "metadata": {
+                "server-tag": &lt;server tag&gt;
+            },
+            &lt;the rest of the subnet specification here&gt;
+        } ],
+        "count": 1
+    }
+}</screen>
+If the shared network name is null, it means that the returned subnet does not belong to any shared network (global subnet). The metadata is included in the returned subnet definition and it provides database specific information associated with the returned object.</para>
+
+</section>
+<!-- end of remote-subnet6-get-by-prefix -->
+
+<!-- start of remote-subnet6-list -->
+<section xml:id="reference-remote-subnet6-list">
+<title>remote-subnet6-list reference</title>
+<para xml:id="ref-remote-subnet6-list"><command>remote-subnet6-list</command> - This command is used to fetch a list of all IPv6 subnets from the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet6-list"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet6-list"
+    "arguments": {
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+This command includes no arguments besides the optional <command>remote</command> map.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "2 IPv6 subnets found.",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;first subnet identifier&gt;,
+                "subnet": &lt;first subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            },
+            {
+                "id": &lt;second subnet identifier&gt;,
+                "subnet": &lt;second subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                "metadata": {
+                    "server-tag": &lt;server tag&gt;
+                }
+            }
+        ],
+        "count": 2
+    }
+}</screen>
+The returned response contains a list of maps. Each map contains a subnet identifier, prefix and shared network name to which the subnet belongs. If the subnet does not belong to a shared netork the name is null. The metadata includes database specific information associated with the subnets. The returned list does not contain full subnet definitions. Use <command>remote-subnet6-get</command> to fetch the full information about the selected subnets.</para>
+
+</section>
+<!-- end of remote-subnet6-list -->
+
+<!-- start of remote-subnet6-set -->
+<section xml:id="reference-remote-subnet6-set">
+<title>remote-subnet6-set reference</title>
+<para xml:id="ref-remote-subnet6-set"><command>remote-subnet6-set</command> - This command is used to create or replace an IPv4 subnet the configuration database.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-cb_cmds-lib">cb_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-remote-subnet6-set"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "remote-subnet6-set",
+    "arguments": {
+        "subnets": [
+            {
+                "id": &lt;subnet identifier&gt;,
+                "subnet": &lt;subnet prefix&gt;,
+                "shared-network-name": &lt;shared network name&gt; | null,
+                &lt;the rest of the subnet specification here&gt;
+            }
+        ],
+        "remote": {
+            &lt;specification of the database to connect to&gt;
+        }
+    }
+}</screen>
+The provided list must contain exactly one subnet specification. The <command>shared-network-name</command> parameter is required for these commands. It associates the subnet with the shared network by its name. If the subnet must not belong to any shared network (global subnet), the <command>null</command> value must be specified for the shared network name.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "IPv6 subnet successfully set.",
+    "arguments": {
+        "id": &lt;subnet identifier&gt;,
+        "subnet": &lt;subnet prefix&gt;
+    }
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of remote-subnet6-set -->
+
+<!-- start of reservation-add -->
+<section xml:id="reference-reservation-add">
+<title>reservation-add reference</title>
+<para xml:id="ref-reservation-add"><command>reservation-add</command> - adds a new host reservation. The reservation may include IPv4 address,
+        IPv6 addresses, IPv6 prefixes, various identifiers, a class
+        the client will be assigned to, DHCPv4 and DHCPv6 options and
+        more.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.2.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-reservation-add"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "reservation-add",
+    "arguments": {
+        "reservation": {
+            "boot-file-name": &lt;string&gt;,
+            "comment": &lt;string&gt;
+            "client-id": &lt;string&gt;,
+            "circuit-id": &lt;string&gt;,
+            "duid": &lt;string&gt;,
+            "flex-id": &lt;string&gt;,
+            "ip-address": &lt;string (IPv4 address)&gt;,
+            "ip-addresses": [ &lt;comma separated strings&gt; ],
+            "hw-address": &lt;string&gt;,
+            "hostname": &lt;string&gt;,
+            "next-server": &lt;string (IPv4 address)&gt;,
+            "option-data-list": [ &lt;comma separated structures defining options&gt; ],
+            "prefixes": [ &lt;comma separated IPv6 prefixes&gt; ],
+            "reservation-client-classes": [ &lt;comma separated strings&gt; ],
+            "server-hostname": &lt;string&gt;,
+            "subnet-id": &lt;integer&gt;,
+            "user-context": &lt;any valid JSON&gt;,
+        }
+    }
+}</screen>
+Note the ip-address, client-id, next-server, server-hostname and
+boot-file-name are IPv4 specific. duid, ip-addresses and prefixes are
+IPv6 specific.</para>
+
+<para>Response syntax:
+  <screen>
+{
+    "result": &lt;integer&gt;,
+    "text": &lt;string&gt;
+}</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)
+  </para></listitem>
+</itemizedlist></para>
+
+</section>
+<!-- end of reservation-add -->
+
+<!-- start of reservation-del -->
+<section xml:id="reference-reservation-del">
+<title>reservation-del reference</title>
+<para xml:id="ref-reservation-del"><command>reservation-del</command> - Deletes an existing host reservation.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.2.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-reservation-del"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "reservation-del",
+    "arguments": {
+        "subnet-id": &lt;integer&gt;,
+        "ip-address": &lt;string&gt;,
+        "identifier-type": &lt;one of "hw-address", "duid", "circuit-id", "client-id" and "flex-id"&gt;,
+        "identifier": &lt;string&gt;
+    }
+}</screen>
+The host reservation can be identified by either (subnet-id, ip-address) pair or a triplet of (subnet-id, identifier-type, identifier).</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": &lt;integer&gt;,
+    "text": &lt;string&gt;
+}
+</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of reservation-del -->
+
+<!-- start of reservation-get -->
+<section xml:id="reference-reservation-get">
+<title>reservation-get reference</title>
+<para xml:id="ref-reservation-get"><command>reservation-get</command> - Attempts to retrieve an existing host reservation</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.2.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-reservation-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "reservation-get",
+    "arguments": {
+        "subnet-id": &lt;integer&gt;,
+        "identifier-type": &lt;string with one value out of: hw-address|duid|circuit-id|client-id|flex-id&gt;,
+        "identifier": &lt;string&gt;;
+    }
+}</screen>
+The host reservation can be identified by either (subnet-id, ip-address) pair or a triplet of (subnet-id, identifier-type, identifier).</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": &lt;integer&gt;,
+    "text": &lt;string&gt;,
+    "arguments": {
+        "boot-file-name": &lt;string&gt;,
+        "comment": &lt;string&gt;
+        "client-id": &lt;string&gt;,
+        "circuit-id": &lt;string&gt;,
+        "duid": &lt;string&gt;,
+        "flex-id": &lt;string&gt;,
+        "ip-address": &lt;string (IPv4 address)&gt;,
+        "ip-addresses": [ &lt;comma separated strings&gt; ],
+        "hw-address": &lt;string&gt;,
+        "hostname": &lt;string&gt;,
+        "next-server": &lt;string (IPv4 address)&gt;,
+        "option-data-list": [ &lt;comma separated structures defining options&gt; ],
+        "prefixes": [ &lt;comma separated IPv6 prefixes&gt; ],
+        "reservation-client-classes": [ &lt;comma separated strings&gt; ],
+        "server-hostname": &lt;string&gt;,
+        "subnet-id": &lt;integer&gt;,
+        "user-context": &lt;any valid JSON&gt;,
+    }
+}</screen>
+Arguments object appear only if a host is found. Many fields in the arguments
+object appear only if specific field is set.</para>
+
+</section>
+<!-- end of reservation-get -->
+
+<!-- start of reservation-get-all -->
+<section xml:id="reference-reservation-get-all">
+<title>reservation-get-all reference</title>
+<para xml:id="ref-reservation-get-all"><command>reservation-get-all</command> - Retrieve all host reservations for a specified subnet.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-reservation-get-all"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "reservation-get-all",
+    "arguments": {
+        "subnet-id": &lt;integer&gt;
+}</screen>
+</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": &lt;integer&gt;,
+    "text": &lt;string&gt;
+}
+</screen>
+reservation-get-all command may result in very large responses.</para>
+
+</section>
+<!-- end of reservation-get-all -->
+
+<!-- start of reservation-get-page -->
+<section xml:id="reference-reservation-get-page">
+<title>reservation-get-page reference</title>
+<para xml:id="ref-reservation-get-page"><command>reservation-get-page</command> - Retrieve host reservations for a specified subnet by page.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.6.0 (<link linkend="commands-host_cmds-lib">host_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-reservation-get-page"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "reservation-get-page",
+    "arguments": {
+        "subnet-id": &lt;integer&gt;,
+        "limit": &lt;integer&gt;,
+        "source-index": &lt;integer&gt;,
+        "from": &lt;integer&gt;
+    }
+}</screen>
+the subnet id and the page size limit are mandatory. The source index and from host id are optional and default to 0. Values to use to next the next page are returned in responses in a next map.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": &lt;integer&gt;,
+    "text": &lt;string&gt;
+}
+</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of reservation-get-page -->
+
+<!-- start of shutdown -->
+<section xml:id="reference-shutdown">
+<title>shutdown reference</title>
+<para xml:id="ref-shutdown"><command>shutdown</command> - The shutdown command instructs the server to initiate its shutdown procedure.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command>, <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command>, <command><link linkend="commands-kea-dhcp-ddns">kea-dhcp-ddns</link></command>, <command><link linkend="commands-kea-ctrl-agent">kea-ctrl-agent</link></command></para>
+
+<para>Availability: 1.0.0 (built-in)</para>
+
+<para>Description and examples: See <xref linkend="command-shutdown"/></para>
+
+<para>Command syntax:
+  <screen>{
+    "command": "shutdown"
+}</screen>
+The server will respond with a confirmation that the shutdown
+                    procedure has been initiated.</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": &lt;integer&gt;,
+    "text": &lt;string&gt;
+}
+</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of shutdown -->
+
+<!-- start of stat-lease4-get -->
+<section xml:id="reference-stat-lease4-get">
+<title>stat-lease4-get reference</title>
+<para xml:id="ref-stat-lease4-get"><command>stat-lease4-get</command> - The stat-lease4-get command fetches lease statistics for a range
+              of known IPv4 subnets.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
+
+<para>Availability: 1.4.0 (<link linkend="commands-stat_cmds-lib">stat_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-stat-lease4-get"/></para>
+
+<para>Command syntax:
+  <screen>{
+  "command": "stat-lease4-get"
+}</screen>
+</para>
+
+<para>Response syntax:
+  <screen>{
+    "result": 0,
+    "text": "stat-lease4-get: 2 rows found",
+    "arguments": {
+      "result-set": {
+        "columns": [ "subnet-id",
+                       "total-addresses",
+                       "assigned-addresses",
+                       "declined-addresses" ]
+        "rows": [
+          [ 10, 256, 111, 0 ],
+          [ 20, 4098, 2034, 4 ]
+        ],
+      "timestamp": "2018-05-04 15:03:37.000000"
+      }
+    }
+  }</screen>
+Result is an integer representation of the status. Currently supported statuses are:
+<itemizedlist>
+  <listitem><para>0 - success</para></listitem>
+  <listitem><para>1 - error</para></listitem>
+  <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
+</itemizedlist>
+</para>
+
+</section>
+<!-- end of stat-lease4-get -->
+
+<!-- start of stat-lease6-get -->
+<section xml:id="reference-stat-lease6-get">
+<title>stat-lease6-get reference</title>
+<para xml:id="ref-stat-lease6-get"><command>stat-lease6-get</command> - The stat-lease6-get command fetches lease statistics for a range
+              of known IPv6 subnets.</para>
+
+<para>Supported by: <command><link linkend="commands-kea-dhcp6">kea-dhcp6</link></command></para>
+
+<para>Availability: 1.4.0 (<link linkend="commands-stat_cmds-lib">stat_cmds</link>  hook)</para>
+
+<para>Description and examples: See <xref linkend="command-stat-lease6-get"/></para>
 
 <para>Command syntax:
   <screen>{
@@ -3093,7 +5268,7 @@ Result is an integer representation of the status. Currently supported statuses
   <screen>{
     "command": "subnet4-add",
     "arguments": {
-        "subnet4": [ {
+        "subnets": [ {
             "id": 123,
             "subnet": "10.20.30.0/24",
             ...
@@ -3262,7 +5437,7 @@ If no IPv4 subnets are found, an error code is returned along with the error des
 <!-- start of subnet4-update -->
 <section xml:id="reference-subnet4-update">
 <title>subnet4-update reference</title>
-<para xml:id="ref-subnet4-update"><command>subnet4-update</command> - This command is used to  update a subnet in the existing server configuration.</para>
+<para xml:id="ref-subnet4-update"><command>subnet4-update</command> - This command is used to update a subnet in the existing server configuration.</para>
 
 <para>Supported by: <command><link linkend="commands-kea-dhcp4">kea-dhcp4</link></command></para>
 
@@ -3274,7 +5449,7 @@ If no IPv4 subnets are found, an error code is returned along with the error des
   <screen>{
     "command": "subnet4-update",
     "arguments": {
-        "subnet4": [ {
+        "subnets": [ {
             "id": 123,
             "subnet": "10.20.30.0/24",
             ...
@@ -3301,6 +5476,7 @@ Result is an integer representation of the status. Currently supported statuses
   <listitem><para>0 - success</para></listitem>
   <listitem><para>1 - error</para></listitem>
   <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
 </itemizedlist>
 </para>
 
@@ -3528,6 +5704,7 @@ Result is an integer representation of the status. Currently supported statuses
   <listitem><para>0 - success</para></listitem>
   <listitem><para>1 - error</para></listitem>
   <listitem><para>2 - unsupported</para></listitem>
+  <listitem><para>3 - empty (command was completed successfully, but no data was affected or returned)</para></listitem>
 </itemizedlist>
 </para>
 
diff --git a/doc/guide/config-backend.xml b/doc/guide/config-backend.xml
new file mode 100644
index 0000000000000000000000000000000000000000..038f66890fea317c21dc125e00b8a75a3d070fd8
--- /dev/null
+++ b/doc/guide/config-backend.xml
@@ -0,0 +1,188 @@
+<!--
+ - Copyright (C) 2019 Internet Systems Consortium, Inc. ("ISC")
+ -
+ - This Source Code Form is subject to the terms of the Mozilla Public
+ - License, v. 2.0. If a copy of the MPL was not distributed with this
+ - file, you can obtain one at http://mozilla.org/MPL/2.0/.
+-->
+
+<section xml:id="config-backend">
+  <title>Kea Configuration Backend</title>
+
+  <section xml:id="cb-applicability">
+    <title>Applicability</title>
+
+    <para>
+      Kea Configuration Backend (abbreviated as CB) is a feature first
+      introduced in 1.6.0 release, which provides Kea servers with the
+      ability to manage and fetch their configuration from one or more
+      databases. In the documentation, the term "Configuration Backend"
+      may also refer to the particular Kea module providing support
+      to manage and fetch the configuration information from the particular
+      database type. For example: MySQL Configuration Backend is the logic
+      implemented within the "mysql_cb" hooks library which provides a
+      complete set of functions to manage and fetch the configuration
+      information from the MySQL database.
+    </para>
+
+    <para>
+      In small deployments, e.g. those comprising a single DHCP server instance
+      with limited and infrequently changing number of subnets, it may
+      be impractical to use the CB as a configuration repository because
+      it requires additional third party software to be installed and
+      configured - in particular the  MySQL server and MySQL client.
+      Once the number of DHCP servers and/or the number of managed
+      subnets in the network grows, the usefulness of the CB becomes
+      obvious.
+    </para>
+
+    <para>
+      A good example is a pair of the Kea DHCP servers which can be
+      configured to support High Availability as described in
+      <xref linkend="high-availability-library"/>.
+      The configurations of both servers are almost exactly the same.
+      They may differ by the server identifier and designation of the
+      server as a primary or standby (or secondary). They may also
+      differ by the interfaces configuration. Typically, the subnets,
+      shared networks, option definitions, global parameters are
+      the same for both servers and can be sourced from a single
+      database instance to both Kea servers.
+    </para>
+
+    <para>
+      Using the database as a single source of configuration for subnets
+      and/or other configuration information supported by the CB has
+      the advantage that any modifications to the configuration in
+      the database is automatically applied to both servers.
+    </para>
+
+    <para>
+      Another case when the centralized configuration repository is desired
+      is in deployments including large number of the DHCP servers, possibly
+      using a common lease database to provide redundancy. The new servers
+      can be added to the pool frequently to fulfil growing scalability
+      requirements. Adding the new server does not require replicating
+      the entire configuration to the new server when common database is
+      used.
+    </para>
+
+    <para>
+      Using the database as a configuration repository for Kea servers also
+      brings other benefits, such as:
+      <itemizedlist>
+        <listitem><simpara>an ability to use database specific tools to access
+        the configuration information,</simpara></listitem>
+        <listitem><simpara>an ability to create customized statistics based
+        on the information stored in the database,</simpara></listitem>
+        <listitem><simpara>an ability to backup the configuration information
+        using the database builtin replication mechanisms.</simpara></listitem>
+      </itemizedlist>
+    </para>
+
+  </section>
+
+  <section xml:id="cb-limitations">
+    <title>CB Capabilities and Limitations</title>
+    <para>
+      Kea CB has been introduced in the 1.6.0 release, but this
+      implementation comes with a number of limitations being the
+      result of the overall complexity of this feature and the development
+      time constraints. This feature will evolve over time and the new
+      capabilities will be added in subsequent releases. In this
+      section we present the limitations of the CB, present in the
+      current Kea 1.6.0 release:
+    </para>
+
+    <itemizedlist>
+      <listitem><simpara>
+        Kea CB is currently supported for the MySQL database only.
+      </simpara></listitem>
+      <listitem><simpara>
+        Kea CB is only supported for DHCPv4 and DHCPv6 servers.
+        Neither Control Agent nor D2 deamon can be configured via the database.
+      </simpara></listitem>
+      <listitem><simpara>
+        Configuration to be stored for the DHCP servers includes: global parameters,
+        option definitions, global options, shared networks and subnets. Other
+        configuration parameters are not stored in the database at the moment.
+        They have to be configured via the JSON configuration file.
+      </simpara></listitem>
+      <listitem><simpara>
+        It is not supported to differentiate configurations of multiple
+        DHCP servers within the same database. All servers conected to the
+        particular database instance share the configuration stored in this
+        database. This limitation will be removed in Kea 1.6.0 final release.
+      </simpara></listitem>
+    </itemizedlist>
+
+    <note>
+      <para>
+        We strongly recommend to not duplicate the configuration information
+        in the file and the database. For example, when specifying subnets
+        for the DHCP server, please store them in the configuration backend
+        or in the configuration file, not in both places. Storing some subnets
+        in the database and other in the file may put you at risk of potential
+        configuration conflicts. Note that the configuration from the database
+        takes precedence over the configuration from the file, thus it is possible
+        that parts of the configuration specified in the file may be overriden.
+      </para>
+    </note>
+
+    <note>
+      <para>
+        It is recommended that <command>subnet_cmds</command> hooks library is
+        not used to manage the subnets when the configuration backend is used
+        as a source of information about the subnets. The
+        <command>subnet_cmds</command> hooks library modifies the local subnets
+        configuration (in the server's memory), not in the database. Use
+        the <command>cb_cmds</command> hooks library to manage the subnets
+        information in the database instead.
+      </para>
+    </note>
+
+  </section>
+
+  <section xml:id="cb-components">
+    <title>CB Components</title>
+    <para>
+      In order to use the Kea CB feature, the Kea 1.6.0 version or later is
+      required. The <command>mysql_cb</command> open source hooks library
+      implementing the Configuration Backend for MySQL must be compiled and
+      loaded by the DHCP servers. This hooks library is compiled when the
+      <filename>--with-mysql</filename> configuration switch is used during
+      Kea build. The MySQL C client libraries must be installed
+      as explained in the <xref linkend="dhcp-install-configure"/>.
+    </para>
+
+    <note>
+      <simpara>Any existing MySQL schema must be upgraded to the latest schema
+      required by the particular Kea version using <command>kea-admin</command>
+      tool described in <xref linkend="kea-admin"/>.</simpara>
+    </note>
+
+    <para>
+      The <command>cb_cmds</command> premium hooks library is available to
+      ISC paid supported customers, which provides a complete set of commands
+      to manage the servers' configuration information within the database.
+      This library can be attached to both DHCPv4 and DHCPv6 server instance.
+      It is still possible to manage the configuration information without the
+      <command>cb_cmds</command> hooks library with commonly available tools
+      such as MySQL Workbench or command line MySQL client, by directly working
+      with the database.
+    </para>
+
+    <para>
+      Refer to the <xref linkend="cb-cmds-library"/> for the details regarding
+      the <command>cb_cmds</command> hooks library.
+    </para>
+
+    <para>
+      The DHCPv4 and DHCPv6 server specific configuration of the CB as well as
+      the list of supported configuration parameters can be found in the
+      <xref linkend="dhcp4-cb"/> and <xref linkend="dhcp6-cb"/>
+      respectively.
+    </para>
+
+  </section>
+
+</section>
diff --git a/doc/guide/config.xml b/doc/guide/config.xml
index f391154c6d515ad8c958b1a0c37c8bbab54548d5..805c642c6bba13e2ea10e155695737802ee03bf7 100644
--- a/doc/guide/config.xml
+++ b/doc/guide/config.xml
@@ -151,4 +151,7 @@
 
   </section>
 
+  <!-- Include large section about Kea Config Backend -->
+  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="config-backend.xml"/>
+
 </chapter>
diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index 506e22882b879b4b706a4b04dd414c988b8930a3..173b2988a5fbdaff6146c309f4bbeec5aac517ba 100644
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -5581,4 +5581,200 @@ autogenerated IDs are not stable across configuration changes.</para>
 
     </section>
 
+    <section id="dhcp4-cb">
+      <title>Configuration Backend in DHCPv4</title>
+      <para>
+        In the <xref linkend="config-backend"/> we have described the
+        Configuration Backend feature, its applicability and limitations. This
+        section focuses on the usage of the CB with the DHCPv4 server. It lists
+        the supported parameters, describes limitations and gives examples of the
+        DHCPv4 server configuration to take advantage of the CB. Please also refer
+        to the sibling section <xref linkend="dhcp6-cb"/> for the
+        DHCPv6 specific usage of the CB.
+      </para>
+
+      <section id="dhcp4-cb-parameters">
+        <title>Supported Parameters</title>
+        <para>The ultimate goal for the CB is to serve as a central configuration
+        repository for one or multiple Kea servers connected to the database.
+        In the future it will be possible to store the most of the server's configuration
+        in the database and reduce the configuration file to bare minimum, i.e.
+        the only mandatory parameter will be the <command>config-control</command>
+        which includes the necessary information to connect to the database. In
+        the Kea 1.6.0 release, however, only the subset of the DHCPv4 server
+        parameters can be stored in the database. All other parameters must be
+        specified in the JSON configuration file, if required.</para>
+
+        <para>The following table lists DHCPv4 specific parameters supported by
+        the Configuration Backend with an indication on which level of the
+        hierarchy it is currently supported. The "n/a" is used in cases
+        when the particular parameter is not applicable on the particular
+        level of the hierarchy or in cases when the parameter is not supported
+        by the server on this level of hierarchy. The "no" is used when
+        the parameter is supported by the server on the particular level of
+        hierarchy but is not configurable via the Configuration Backend.
+        </para>
+
+        <para>All supported parameters can be configured via <command>cb_cmds</command>
+        hooks library described in the <xref linkend="cb-cmds-library"/>. The
+        general rule is that the scalar global parameters are set using the
+        <command>remote-global-parameter4-set</command>. The shared network
+        specific parameters are set using the <command>remote-network4-set</command>.
+        Finally, the subnet and pool level parameters are set using the
+        <command>remote-subnet4-set</command>. Whenever there is an exception from
+        this general rule, it is highlighted in the table. The non-scalar global
+        parameters have dedicated commands, e.g. modifying the global DHCPv4 options
+        (<command>option-data</command>) is performed using the
+        <command>remote-option4-global-set</command>.</para>
+
+        <para>
+          <table frame="all" xml:id="dhcp4-cb-parameters">
+            <title>List of DHCPv4 Parameters Supported by the Configuration Backend</title>
+            <tgroup cols="5">
+              <colspec colname="parameter"/>
+              <colspec colname="global" align="center"/>
+              <colspec colname="shared network" align="center"/>
+              <colspec colname="subnet" align="center"/>
+              <colspec colname="pool" align="center"/>
+              <thead>
+                <row>
+                  <entry>Parameter</entry>
+                  <entry>Global</entry>
+                  <entry>Shared Network</entry>
+                  <entry>Subnet</entry>
+                  <entry>Pool</entry>
+                </row>
+              </thead>
+              <tbody>
+                <row><entry>4o6-interface</entry><entry>n/a</entry><entry>n/a</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>4o6-interface-id</entry><entry>n/a</entry><entry>n/a</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>4o6-subnet</entry><entry>n/a</entry><entry>n/a</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>boot-file-name</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>calculate-tee-times</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>client-class</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>no</entry></row>
+                <row><entry>decline-probation-period</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>dhcp4o6-port</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>echo-client-id</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>interface</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>match-client-id</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>next-server</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>option-data</entry><entry>yes (via remote-option4-global-set)</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry></row>
+                <row><entry>option-def</entry><entry>yes (via remote-option-def4-set)</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>rebind-timer</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>renew-timer</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>server-hostname</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>valid-lifetime</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>relay</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>require-client-classes</entry><entry>no</entry><entry>yes</entry><entry>yes</entry><entry>no</entry></row>
+                <row><entry>reservation-mode</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>t1-percent</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+                <row><entry>t2-percent</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry></row>
+              </tbody>
+            </tgroup>
+          </table>
+        </para>
+      </section>
+
+      <section id="dhcp4-cb-json">
+      <title>Enabling Configuration Backend</title>
+      <para>
+        Consider the following configuration snippet:
+<screen>
+{
+    "Dhcp4": {
+        "config-control": {
+            "config-databases": [
+                {
+                    "type": "mysql",
+                    "name": "kea",
+                    "user": "kea",
+                    "password": "kea",
+                    "host": "192.0.2.1",
+                    "port": 3302
+                }
+            ],
+            "config-fetch-wait-time": 20
+        },
+        "hooks-libraries": [
+            {
+                "library": "/usr/local/lib/kea/hooks/libdhcp_mysql_cb.so"
+            },
+            {
+                "library": "/usr/local/lib/kea/hooks/libdhcp_cb_cmds.so"
+            }
+        ],
+        ...
+    }
+}
+</screen>
+      </para>
+      <para>
+        The <command>config-control</command> contains two parameters. The
+        <command>config-databases</command> is a list which contains one
+        element comprising database type, location and the credentials to
+        be used to connect to this database. Note that the parameters specified
+        here correspond to the database specification for the lease database
+        backend and hosts database backend. Currently only one database connection
+        can be specified on the <command>config-databases</command> list. The server
+        will connect to this database during the startup or reconfiguration, and
+        will fetch the configuration available for this server from the database.
+        This configuration is merged into the configuration read from the
+        configuration file.</para>
+
+        <note>
+          <para>Whenever there is a conflict between the parameters specified
+          in the configuration file and the database, the parameters from the
+          database take precedence. We strongly recommend to avoid
+          duplicating parameters in the file and the database but this recommendation
+          is not enforced by the Kea servers. In particular, if the subnets'
+          configuration is sourced from the database, we recommend that all
+          subnets are specified in the database and no subnets are specified
+          in the configuration file. It is possible to specify the
+          subnets in both places, but that must be done with care. The subnets in
+          the configuration file with overlapping ids and/or prefixes with the
+          subnets from the database will be superseded by those from the database.
+          </para>
+        </note>
+
+        <para>
+          Once the Kea server is configured, it starts periodically polling for
+          the configuration changes in the database. The frequency of polling
+          is controlled by the <command>config-fetch-wait-time</command> parameter.
+          It is expressed in seconds and it is the period between the
+          time when the server completed last polling (and possibly the local
+          configuration update) and the time when it begins polling again. In
+          the example above, this period is set to 20 seconds. This means that
+          after adding a new configuration into the database (e.g. added new
+          subnet), it will take up to 20 seconds (plus the time needed to fetch
+          and apply the new configuration) before the server starts using this
+          subnet. The lower the <command>config-fetch-wait-time</command> value,
+          the shorter the time for the server to react to the incremental
+          configuration updates in the database. On the other hand, polling the
+          database too frequently may impact the DHCP server's performance because
+          the server needs to make at least one query to the database to discover
+          the pending configuration updates.The default value of the
+          <command>config-fetch-wait-time</command> is 30 seconds.
+        </para>
+
+        <para>
+          Finally, in the configuration example above, two hooks libraries are loaded.
+          The former, <filename>libdhcp_mysql_cb.so</filename>, is the implementation of
+          the Configuration Backend for MySQL. It must be always present when the
+          server uses MySQL as the configuration repository. Failing to load this
+          library will result in an error during the server configuration if the
+          "mysql" database is selected with the <command>config-control</command>
+          parameter.
+        </para>
+
+        <para>
+          The latter hooks library, <filename>libdhcp_cb_cmds.so</filename>, is
+          optional. It should be loaded when the Kea server instance is to be used
+          for managing the configuration in the database. See the
+          <xref linkend="cb-cmds-library"/> for the details. Note that this hooks
+          library is only available to the ISC customers with a support contract.
+        </para>
+
+      </section>
+
+    </section>
   </chapter>
diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml
index ec0610dabfa6866be816e4c815347c138ebe2a72..19dae2990c79149fc8d2772fe9f29e74460665d7 100644
--- a/doc/guide/dhcp6-srv.xml
+++ b/doc/guide/dhcp6-srv.xml
@@ -5643,4 +5643,146 @@ autogenerated IDs are not stable across configuration changes.
 
     </section>
 
+    <section id="dhcp6-cb">
+      <title>Configuration Backend in DHCPv6</title>
+      <para>
+        In the <xref linkend="config-backend"/> we have described the
+        Configuration Backend feature, its applicability and limitations. This
+        section focuses on the usage of the CB with the DHCPv6 server. It lists
+        the supported parameters, describes limitations and gives examples of the
+        DHCPv6 server configuration to take advantage of the CB. Please also refer
+        to the sibling section <xref linkend="dhcp4-cb"/> for the
+        DHCPv4 specific usage of the CB.
+      </para>
+
+      <section id="dhcp6-cb-parameters">
+        <title>Supported Parameters</title>
+        <para>The ultimate goal for the CB is to serve as a central configuration
+        repository for one or multiple Kea servers connected to the database.
+        In the future it will be possible to store the most of the server's configuration
+        in the database and reduce the configuration file to bare minimum, i.e.
+        the only mandatory parameter will be the <command>config-control</command>
+        which includes the necessary information to connect to the database. In
+        the Kea 1.6.0 release, however, only the subset of the DHCPv4 server
+        parameters can be stored in the database. All other parameters must be
+        specified in the JSON configuration file, if required.</para>
+
+        <para>The following table lists DHCPv6 specific parameters supported by
+        the Configuration Backend with an indication on which level of the
+        hierarchy it is currently supported. The "n/a" is used in cases
+        when the particular parameter is not applicable on the particular
+        level of the hierarchy or in cases when the parameter is not supported
+        by the server on this level of hierarchy. The "no" is used when
+        the parameter is supported by the server on the particular level of
+        hierarchy but is not configurable via the Configuration Backend.
+        </para>
+
+        <para>All supported parameters can be configured via <command>cb_cmds</command>
+        hooks library described in the <xref linkend="cb-cmds-library"/>. The
+        general rule is that the scalar global parameters are set using the
+        <command>remote-global-parameter6-set</command>. The shared network
+        specific parameters are set using the <command>remote-network6-set</command>.
+        Finally, the subnet and pool level parameters are set using the
+        <command>remote-subnet6-set</command>. Whenever there is an exception from
+        this general rule, it is highlighted in the table. The non-scalar global
+        parameters have dedicated commands, e.g. modifying the global DHCPv6 options
+        (<command>option-data</command>) is performed using the
+        <command>remote-option6-global-set</command>.</para>
+
+
+        <para>
+          <table frame="all" xml:id="dhcp6-cb-parameters">
+            <title>List of DHCPv6 Parameters Supported by the Configuration Backend</title>
+            <tgroup cols="6">
+              <colspec colname="parameter"/>
+              <colspec colname="global" align="center"/>
+              <colspec colname="shared network" align="center"/>
+              <colspec colname="subnet" align="center"/>
+              <colspec colname="pool" align="center"/>
+              <colspec colname="pd-pool" align="center"/>
+              <thead>
+                <row>
+                  <entry>Parameter</entry>
+                  <entry>Global</entry>
+                  <entry>Shared Network</entry>
+                  <entry>Subnet</entry>
+                  <entry>Pool</entry>
+                  <entry>Prefix Delegation Pool</entry>
+                </row>
+              </thead>
+              <tbody>
+                <row><entry>calculate-tee-times</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>client-class</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>no</entry><entry>no</entry></row>
+                <row><entry>decline-probation-period</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>delegated-len</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>yes</entry></row>
+                <row><entry>dhcp4o6-port</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>excluded-prefix</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>no</entry></row>
+                <row><entry>excluded-prefix-len</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>no</entry></row>
+                <row><entry>interface</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>interface-id</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>option-data</entry><entry>yes (via remote-option6-global-set)</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry></row>
+                <row><entry>option-def</entry><entry>yes (via remote-option-def6-set)</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>preferred-lifetime</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>prefix</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>yes</entry></row>
+                <row><entry>prefix-len</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>n/a</entry><entry>yes</entry></row>
+                <row><entry>rapid-commit</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>rebind-timer</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>relay</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>renew-timer</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>require-client-classes</entry><entry>n/a</entry><entry>yes</entry><entry>yes</entry><entry>no</entry><entry>no</entry></row>
+                <row><entry>reservation-mode</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>t1-percent</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>t2-percent</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+                <row><entry>valid-lifetime</entry><entry>yes</entry><entry>yes</entry><entry>yes</entry><entry>n/a</entry><entry>n/a</entry></row>
+              </tbody>
+            </tgroup>
+          </table>
+        </para>
+      </section>
+
+      <section id="dhcp6-cb-json">
+      <title>Enabling Configuration Backend</title>
+      <para>
+        The following configuration snippet demonstrates how to enable the MySQL
+        Configuration Backend for the DHCPv6 server:
+
+<screen>
+{
+    "Dhcp6": {
+        "config-control": {
+            "config-databases": [
+                {
+                    "type": "mysql",
+                    "name": "kea",
+                    "user": "kea",
+                    "password": "kea",
+                    "host": "2001:db8:1::1",
+                    "port": 3302
+                }
+            ],
+            "config-fetch-wait-time": 20
+        },
+        "hooks-libraries": [
+            {
+                "library": "/usr/local/lib/kea/hooks/libdhcp_mysql_cb.so"
+            },
+            {
+                "library": "/usr/local/lib/kea/hooks/libdhcp_cb_cmds.so"
+            }
+        ],
+        ...
+    }
+}
+</screen>
+      </para>
+
+      <para>
+        The configuration structure is almost identical as for the DHCPv4
+        server (see <xref linkend="dhcp4-cb-json"/> for the detailed description).
+      </para>
+
+      </section>
+
+    </section>
+
   </chapter>
diff --git a/doc/guide/hooks-cb-cmds.xml b/doc/guide/hooks-cb-cmds.xml
new file mode 100644
index 0000000000000000000000000000000000000000..a20d1b9add44bcfe8cfd3ad9f8664b3356199340
--- /dev/null
+++ b/doc/guide/hooks-cb-cmds.xml
@@ -0,0 +1,870 @@
+<!--
+ - Copyright (C) 2019 Internet Systems Consortium, Inc. ("ISC")
+ -
+ - This Source Code Form is subject to the terms of the Mozilla Public
+ - License, v. 2.0. If a copy of the MPL was not distributed with this
+ - file, you can obtain one at http://mozilla.org/MPL/2.0/.
+-->
+
+    <section id="cb-cmds-library">
+      <title>cb_cmds: Configuration Backend Commands</title>
+      <para>
+        This section describes the <command>cb_cmds</command> hooks library
+        which is used to manage Kea servers' configurations in the Configuration
+        Backends. This library must be used in conjuction with the available CB
+        hooks libraries  implementing the common APIs to create, read, update
+        and delete (CRUD) the configuration information in the respective
+        databases. For example: the <command>mysql_cb</command> hooks library,
+        released in Kea 1.6.0, implements this API for MySQL. In order to manage
+        the configuration information in the MySQL database both
+        <command>mysql_cb</command> and <command>cb_cmds</command> libraries
+        must be loaded by the server used for the configuration management.
+      </para>
+
+      <para>The <command>cb_cmds</command> library is only available to ISC
+      customers with a support contract.
+
+      <note>
+        <para>This library may only be loaded by the <command>kea-dhcp4</command>
+        or the <command>kea-dhcp6</command> process.
+        </para>
+      </note>
+      </para>
+
+      <section>
+        <title>Commands Structure</title>
+        <para>There are 5 types of commands supported by this library:</para>
+        <itemizedlist>
+          <listitem><simpara><command>del</command> - delete selected object from the
+          database, e.g. <command>remote-global-parameter4-del</command>
+          </simpara></listitem>
+          <listitem><simpara><command>get</command> - fetch selected object from the
+          database, e.g. <command>remote-subnet4-get</command>,</simpara></listitem>
+          <listitem><simpara><command>get-all</command> - fetch all objects of the
+          particular type from the database, e.g.
+          <command>remote-option-def4-get-all</command>,</simpara></listitem>
+          <listitem><simpara><command>list</command> - list all objects of the particular
+          type in the database, e.g. <command>remote-network4-list</command>; this class
+          of commands returns brief information about each object comparing to the output
+          of <command>get-all</command>,</simpara>
+          </listitem>
+          <listitem><simpara><command>set</command> - creates or replaces an object
+          of the given type in the database, e.g. <command>remote-option4-global-set</command>
+          .</simpara></listitem>
+        </itemizedlist>
+
+        <para>All types of commands accept optional <command>remote</command> map which
+        selects the database instance to which the command refers. For example:
+<screen>
+{
+    "command": "remote-subnet4-list",
+    "arguments": {
+        "remote": {
+            "type": "mysql",
+            "host": "192.0.2.33",
+            "port": 3302
+        }
+    }
+}
+</screen>
+        </para>
+        <para>
+          selects the MySQL database, running on host 192.0.2.33 and port 3302, to
+          fetch the list of subnets from. All parameters in the
+          <command>remote</command> are optional. The <command>port</command>
+          parameter can be only specified in conjuction with the
+          <command>host</command>. If no parameters in the <command>remote</command>
+          parameter are to be specified, the parameter should be omitted. In this
+          case, the server will use the first backend listed in the
+          <command>config-control</command> map within the configuration of the
+          server receiving the command.
+        </para>
+
+        <note>
+          <para>
+            In the Kea 1.6.0 release, it is possible to configure the Kea server to
+            use only one configuration backend. Strictly speaking, it is possible
+            to point Kea server to at most one MySQL database using the
+            <command>config-control</command> parameter. That's why, in this
+            release, the <command>remote</command> parameter may be omitted in
+            the commands because the cb_cmds hooks library will use by default
+            the sole backend.
+          </para>
+        </note>
+      </section>
+
+      <section id="cb-cmds-dhcp">
+        <title>Control Commands for DHCP Servers</title>
+        <para>This section describes and gives some examples of the control
+        commands implemented by the <command>cb_cmds</command> hooks library, to manage
+        the configuration information of the DHCPv4 and DHCPv6 servers. Many of the
+        commands are almost identical between DHCPv4 and DHCPv6, i.e. only differ by the
+        command name. Other commands slightly differ by the structure of the inserted
+        data, e.g. the structure of the IPv4 subnet information is different than the
+        structure of the IPv6 subnet. Nevertheless, they still share the structure of
+        the command arguments and thus it makes sense to describe them together.</para>
+
+        <para>In the following sections, various commands are described and the
+        usage examples are provided. In the sections jointly describing the DHCPv4 and
+        DHCPv6 variants of the particular command we sometimes use the following
+        notation - the <command>remote-subnet[46]-set</command> is the wildcard
+        name for the two commands: <command>remote-subnet4-set</command> and
+        <command>remote-subnet6-set</command>.</para>
+
+        <para>In addition, whenever the text in the subsequent sections refers to a
+        DHCP command or DHCP parameter, it refers to both DHCPv4 and DHCPv6
+        variants. The text specific to the particular server type refers to them as:
+        DHCPv4 command, DHCPv4 parameter, DHCPv6 command, DHCPv6 parameter etc.
+        </para>
+
+        <section id="cb-cmds-metadata">
+          <title>Metadata</title>
+          <para>The typical response to the <command>get</command> or <command>list</command>
+          command includes a list of returned objects (e.g. subnets) and each such
+          object contains the <command>metadata</command> map with some database specific
+          information describing this object. In other words, the metadata contains any
+          information about the fetched object which may be useful for the administrator,
+          but is not the part of the object specification from the DHCP server standpoint.
+          In the Kea 1.6.0 release, the metadata is limited to the
+          <command>server-tag</command>, which describescthe association of the object
+          with the particular server or all servers. The server tag is always set to
+          <command>all</command> in the Kea 1.6.0 beta release.
+          </para>
+
+          <para>The following is the example response to the <command>remote-network4-list</command>
+          command, which includes the metadata:
+          <screen>
+{
+    "result": 0,
+    "text": "1 IPv4 shared network(s) found.",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": "level3",
+                "metadata": {
+                    "server-tag": "all"
+                }
+            }
+        ],
+        "count": 1
+    }
+}
+         </screen>
+         </para>
+
+          <para>Client implementations must not assume that the metadata contains
+          only the <command>server-tag</command> parameter. In the future releases
+          this map will be extended with additional information, e.g. object
+          modification time, log message created during the last modification etc.
+          </para>
+        </section>
+
+        <section id="command-remote-global-parameter4-del">
+          <title>remote-global-parameter4-del, remote-global-parameter6-del commands</title>
+          <para id="command-remote-global-parameter6-del">This command is used to
+          delete a global DHCP parameter from the configuration database. When the
+          parameter is deleted from the database the server will use the value
+          specified in the configuration file for this parameter or a default
+          value if the parameter is not specified in the configuration file.</para>
+          <para>The following command attempts to delete the DHCPv4
+          <command>renew-timer</command> parameter from the database:
+          <screen>
+{
+    "command": "remote-global-parameter4-del",
+    "arguments": {
+        "parameters": [ "renew-timer" ],
+        "remote": {
+            "type": "mysql"
+         }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-global-parameter4-get">
+          <title>remote-global-parameter4-get, remote-global-parameter6-get commands</title>
+          <para id="command-remote-global-parameter6-get">These commands are used to
+          fetch a scalar global DHCP parameter from the configuration database.</para>
+          <para>The following command attempts to fetch the
+          <command>boot-file-name</command> parameter:
+          <screen>
+{
+    "command": "remote-global-parameter4-get",
+    "arguments": {
+        "parameters": [ "boot-file-name" ],
+         "remote": {
+             "type": "mysql"
+         }
+    }
+}
+          </screen>
+          </para>
+          <para>
+            The returned value has one of the four scalar types: string, integer, real
+            or boolean. Non scalar global configuration parameters, such as map or list,
+            are not returned by this command.</para>
+
+            <para>In case of the example above the string value is returned, e.g.:
+            <screen>
+{
+    "result": 0,
+    "text": "1 DHCPv4 global parameter found.",
+    "arguments": {
+        "parameters": {
+            "boot-file-name": "/dev/null",
+            "metadata": {
+                "server-tag": "all"
+            }
+        },
+        "count": 1
+    }
+}
+            </screen>
+          </para>
+
+          <para>
+            The example response for the integer value is:
+            <screen>
+{
+    "result": 0,
+    "text": "1 DHCPv4 global parameter found.",
+    "arguments": {
+        "parameters": {
+            "renew-timer": 2000,
+            "metadata": {
+                "server-tag": "all"
+            }
+        },
+        "count": 1
+    }
+}
+            </screen>
+          </para>
+
+          <para>
+            The real value:
+            <screen>
+{
+    "result": 0,
+    "text": "1 DHCPv4 global parameter found.",
+    "arguments": {
+        "parameters": {
+            "t1-percent": 0.85,
+            "metadata": {
+                "server-tag": "all"
+            }
+        },
+        "count": 1
+    }
+}
+            </screen>
+          </para>
+
+          <para>
+            Finally, the boolean value:
+            <screen>
+{
+    "result": 0,
+    "text": "1 DHCPv4 global parameter found.",
+    "arguments": {
+        "parameters": {
+            "match-client-id": true,
+            "metadata": {
+                "server-tag": "all"
+            }
+        },
+        "count": 1
+    }
+}
+            </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-global-parameter4-get-all">
+          <title>remote-global-parameter4-get-all, remote-global-parameter6-get-all commands</title>
+          <para id="command-remote-global-parameter6-get-all">These commands are used to
+          fetch all global DHCP parameters from the database. They include no arguments
+          besides the optional <command>remote</command> map.</para>
+        </section>
+
+        <section id="command-remote-global-parameter4-set">
+          <title>remote-global-parameter4-set</title>
+          <para id="command-remote-global-parameter6-set">This command is used to
+          create scalar global DHCP parameters in the database. If any of the parameters
+          already exists, its value is replaced as a result of this command. It is
+          possible to set multiple parameters within a single command, each having
+          one of the four types: a string, integer, real and boolean. For example:
+          <screen>
+{
+    "command": "remote-global-parameter4-set"
+    "arguments": {
+        "parameters": {
+            "boot-file-name": "/dev/null",
+            "renew-timer": 2000,
+            "t1-percent": 0.85,
+            "match-client-id": true
+        },
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+          <para>An error is returned if any of the parameters is not supported by the
+          DHCP server or its type does not match. Care should be taken when
+          multiple parameters are specified in a single command because it is
+          possible that only some of the parameters are stored successfully and
+          some fail. If an error occurred when processing this command, it is
+          recommended to use <command>remote-global-parameter[46]-get-all</command>
+          to check which of the parameters have been stored/updated successfully
+          and which failed.</para>
+        </section>
+
+        <section id="command-remote-network4-del">
+          <title>remote-network4-del, remote-network6-del commands</title>
+          <para id="command-remote-network6-del">These commands are used to delete an
+          IPv4 or IPv6 shared network from the database. The optional parameter
+          <command>subnets-action</command> determines whether the subnets belonging
+          to the deleted shared network should also be deleted or preserved.
+          The <command>subnets-action</command> defaults to <command>keep</command>,
+          which preserves the subnets. If it is set to <command>delete</command>,
+          the subnets are deleted along with the shared network.</para>
+
+          <para>The following command:
+          <screen>
+{
+    "command": "remote-network6-del",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": "level3"
+            }
+        ],
+        "subnets-action": "keep",
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+            deletes the "level3" IPv6 shared network. The subnets are preserved
+            but they are disassociated from the deleted shared network and become
+            global. This behavior corresponds to the behavior of the
+            <command>network[46]-del</command> commands with respect to the
+            <command>subnets-action</command>.
+          </para>
+        </section>
+
+        <section id="command-remote-network4-get">
+          <title>remote-network4-get, remote-network6-get commands</title>
+          <para id="command-remote-network6-get">These commands are used to retrieve
+          the information about an IPv4 or IPv6 shared network. The optional
+          parameter <command>subnets-include</command> denotes whether the
+          subnets belonging to the shared network should also be returned. This
+          parameter defaults to <command>no</command> in which case the subnets are
+          not returned. If this parameter is set to <command>full</command>,
+          the subnets are returned together with the shared network.</para>
+
+          <para>The following command fetches the "level3" IPv6 shared network along
+          with the full information about the subnets belonging to it:
+          <screen>
+{
+    "command": "remote-network6-get",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": "level3"
+            }
+        ],
+        "subnets-include": "full",
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-network4-list">
+          <title>remote-network4-list, remote-network6-list commands</title>
+          <para id="command-remote-network6-list">These commands are used to list all
+          IPv4 or IPv6 shared networks in the particular database. The returned information
+          about each shared network merely contains the shared network name and the metadata. In
+          order to fetch the detailed information about the selected shared network,
+          use the <command>remote-network[46]-get</command> command.
+          </para>
+
+          <para>The <command>remote-network[46]-list</command> takes no argument except
+          the optional <command>remote</command> map.
+          </para>
+        </section>
+
+        <section id="command-remote-network4-set">
+          <title>remote-network4-set</title>
+          <para id="command-remote-network6-set">These commands creates new or replaces an
+          existing IPv4 or IPv6  shared network in the database. The structure of the
+          shared network information is the same as in the Kea configuration file
+          (see <xref linkend="shared-network4"/> and <xref linkend="shared-network6"/>
+          for details), except that it is not allowed to specify subnets along with
+          the shared network information. Including the <command>subnet4</command>
+          or <command>subnet6</command> parameter within the shared network information
+          will result in an error.</para>
+
+          <para>These commands are intended to be used for managing the shared network
+          specific information and DHCP options. In order to associate and disassociate
+          the subnets with the shared networks the <command>remote-subnet[46]-set</command>
+          commands should be used.
+          </para>
+
+          <para>
+            The following command adds the IPv6 shared network "level3" to the database:
+            <screen>
+{
+    "command": "remote-network6-set",
+    "arguments": {
+        "shared-networks": [
+            {
+                "name": "level3",
+                "interface": "eth0",
+                "option-data": [ {
+                    "name": "sntp-servers",
+                    "data": "2001:db8:1::1"
+                } ],
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+            </screen>
+          </para>
+          <para>
+            This command includes the <command>interface</command> parameter which sets
+            the shared network level interface name. Remaining shared network level
+            parameters, which are not specified with the command, will be marked as
+            "unspecified" in the database. The DHCP server will use the global values
+            for unspecified parameters or, if the global values are not specified,
+            the default values will be used.
+          </para>
+
+          <note>
+            <para>
+              Same as for other "set" commands, this command replaces the entire
+              information about the given shared network in the database if the
+              shared network already exists. Therefore, when sending this command,
+              make sure to always include all parameters that must be specified for
+              the updated shared network instance. Any unspecified parameter will
+              be marked unspecified in the database, even if its value was present
+              prior to sending the command.
+            </para>
+          </note>
+        </section>
+
+        <section id="command-remote-option-def4-del">
+          <title>remote-option-def4-del, remote-option-def6-del commands</title>
+          <para id="command-remote-option-def6-del">These commands are used to delete
+          a DHCP option definition from the database. The option definition is
+          identified by an option code and option space. For example:
+          <screen>
+{
+    "command": "remote-option-def6-del",
+    "arguments": {
+        "option-defs": [
+            {
+                "code": 1,
+                "space": "isc"
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+             deletes the definition of the option having the code of 1 and
+             belonging to the option space "isc". The default option spaces
+             are "dhcp4" and "dhcp6" for the DHCPv4 and DHCPv6 top level options
+             respectively.
+          </para>
+        </section>
+
+        <section id="command-remote-option-def4-get">
+          <title>remote-option-def4-get, remote-option-def6-get commands</title>
+          <para id="command-remote-option-def6-get">These commands are used to
+          fetch a specified DHCP option definition from the database. The option
+          definition is identified by the option code and option space. The default
+          option spaces are "dhcp4" and "dhcp6" for the DHCPv4 and DHCPv6 top level
+          options respectively.</para>
+
+          <para>The following command retrieves a DHCPv4 option definition
+          having the code of 1 and belonging to option space "isc":
+          <screen>
+{
+    "command": "remote-option-def4-get"
+    "arguments": {
+        "option-defs": [
+            {
+                "code": 1,
+                "space": "isc"
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-option-def4-get-all">
+          <title>remote-option-def4-get-all, remote-option-def6-get-all commands</title>
+          <para id="command-remote-option-def6-get-all">These commands are used to
+          fetch all DHCP option definitions from the database. It takes no
+          arguments except the optional <command>remote</command> map.</para>
+        </section>
+
+        <section id="command-remote-option-def4-set">
+          <title>remote-option-def4-set, remote-option-def6-set commands</title>
+          <para id="command-remote-option-def6-set">These commands create a new
+          DHCP option definition or replace an existing option definition in the
+          database. The structure of the option definition information is the
+          same as in the Kea configuration file (see <xref linkend="dhcp4-custom-options"/>
+          and <xref linkend="dhcp6-custom-options"/>).
+          The following command creates the DHCPv4 option definition in the top
+          level "dhcp4" option space:
+          <screen>
+{
+    "command": "remote-option-def4-set",
+    "arguments": {
+        "option-defs": [
+            {
+                "name": "foo",
+                "code": 222,
+                "type": "uint32",
+                "array": false,
+                "record-types": "",
+                "space": "dhcp4",
+                "encapsulate": ""
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-option4-global-del">
+          <title>remote-option4-global-del, remote-option6-global-del commands</title>
+          <para id="command-remote-option6-global-del">These commands are used to delete
+          a global DHCP option from the database. The option is identified by an option
+          code and option space. For example:
+          <screen>
+{
+    "command": "remote-option4-global-del",
+    "arguments": {
+        "options": [
+            {
+                "code": 5
+                "space": "dhcp4"
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+          <para>
+            The "dhcp4" is the top level option space where the standard DHCPv4
+            options belong.
+          </para>
+        </section>
+
+        <section id="command-remote-option4-global-get">
+          <title>remote-option4-global-get, remote-option6-global-get commands</title>
+          <para id="command-remote-option6-global-get">These commands are used to fetch
+          a global DHCP option from the database. The option is identified by the code
+          and option space. The top level option spaces where DHCP standard options
+          belong are called "dhcp4" and "dhcp6" for the DHCPv4 and DHCPv6 servers
+          respectively.
+          </para>
+          <para>
+            The following command retrieves the IPv6 "DNS Servers" (code 23) option:
+            <screen>
+{
+    "command": remote-option6-global-get",
+    "arguments": {
+        "options": [
+            {
+                "code": 23,
+                "space": "dhcp6"
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+            </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-option4-global-get-all">
+          <title>remote-option4-global-get-all, remote-option6-global-get-all commands</title>
+          <para id="command-remote-option6-global-get-all">These commands are used to fetch
+          all global DHCP options from the configuration database. It takes no arguments
+          except the optional <command>remote</command> map.</para>
+        </section>
+
+        <section id="command-remote-option4-global-set">
+          <title>remote-option4-global-set, remote-option6-global-set command</title>
+          <para id="command-remote-option6-global-set">These commands create a new
+          global DHCP option or replace an existing option in the database. The
+          structure of the option information is the same as in the Kea configuration
+          file (see <xref linkend="dhcp4-std-options"/> and
+          see <xref linkend="dhcp4-std-options"/>). For example:
+          <screen>
+{
+    "command": "remote-option6-global-set",
+    "arguments": {
+        "options": [
+            {
+                "name": "dns-servers",
+                "data": "2001:db8:1::1"
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+          <para>
+            Note that specifying an option name instead of the option code only works
+            reliably for the standard DHCP options. When specifying a value for the
+            user defined DHCP option, the option code should be specified instead of
+            the name. For example:
+            <screen>
+{
+    "command": "remote-option6-global-set",
+    "arguments": {
+        "options": [
+            {
+                "code": 1,
+                "space": "isc",
+                "data": "2001:db8:1::1"
+            }
+        ]
+    }
+}
+            </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-subnet4-del-by-id">
+          <title>remote-subnet4-del-by-id, remote-subnet6-del-by-id command</title>
+          <para id="command-remote-subnet6-del-by-id">This is the first variant of
+          the commands used to delete an IPv4 or IPv6 subnet from the database.
+          It uses subnet ID to identify the subnet. For example, in order to
+          delete the IPv4 subnet with ID of 5:
+          <screen>
+{
+    "command": "remote-subnet4-del-by-id",
+    "arguments": {
+        "subnets": [
+            {
+                "id": 5
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-subnet4-del-by-prefix">
+          <title>remote-subnet4-del-by-prefix, remote-subnet6-del-by-prefix commands</title>
+          <para id="command-remote-subnet6-del-by-prefix">This is the second variant
+          of the commands used to delete an IPv4 or IPv6 subnet from the database.
+          It uses the subnet prefix to identify the subnet. For example:
+          <screen>
+{
+    "command": "remote-subnet6-del-by-prefix",
+    "arguments": {
+        "subnets": [
+            {
+                "subnet": "2001:db8:1::/64"
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-subnet4-get-by-id">
+          <title>remote-subnet4-get-by-id, remote-subnet6-get-by-id commands</title>
+          <para id="command-remote-subnet6-get-by-id">This is the first variant of
+          the commands used to fetch an IPv4 or IPv6  subnet from the database. It
+          uses a subnet ID to identify the subnet. For example:
+          <screen>
+{
+    "command": "remote-subnet4-get-by-id",
+    "arguments": {
+        "subnets": [
+            {
+                "id": 5
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-subnet4-get-by-prefix">
+          <title>remote-subnet4-get-by-prefix, remote-subnet6-get-by-prefix command</title>
+          <para id="command-remote-subnet6-get-by-prefix">This is the second variant
+          of the commands used to fetch an IPv4 or IPv6 subnet from the database. It
+          uses a subnet prefix to identify the subnet. For example:
+          <screen>
+{
+    "command": "remote-subnet6-get-by-prefix",
+    "arguments": {
+        "subnets": [
+            {
+                "subnet": "2001:db8:1::/64"
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+        </section>
+
+        <section id="command-remote-subnet4-list">
+          <title>remote-subnet4-list, remote-subnet6-list commands</title>
+          <para id="command-remote-subnet6-list">These commands are used to list
+          all IPv4 or IPv6 subnets from the database. It takes no parameters
+          except the optional <command>remote</command> map.
+          The returned information about each subnet is limited to subnet identifier,
+          prefix and associated shared network name. In order to retrieve full
+          information about the selected subnet use the
+          <command>remote-subnet[46]-get-by-id</command> or
+          <command>remote-subnet[46]-get-by-prefix</command>.
+          </para>
+        </section>
+
+        <section id="command-remote-subnet4-set">
+          <title>remote-subnet4-set, remote-subnet6-set commands</title>
+          <para id="command-remote-subnet6-set">These commands are used to create
+          a new IPv4 or IPv6 subnet or replace an existing subnet in the database.
+          Setting the subnet also associates or disassociates the subnet with a
+          shared network.</para>
+
+          <para>The structure of the subnet information is similar to the structure
+          used in the configuration file (see <xref linkend="dhcp4-configuration"/>
+          and <xref linkend="dhcp6-configuration"/>). The subnet information
+          conveyed in the <command>remote-subnet[46]-set</command> must include
+          additional parameter <command>shared-network-name</command> which denotes
+          whether the subnet belongs to a shared network or not.
+          </para>
+
+          <para>Consider the following example:
+          <screen>
+{
+    "command": "remote-subnet4-set",
+    "arguments": {
+        "subnets": [
+            {
+                "id": 5,
+                "subnet": "192.0.2.0/24",
+                "shared-network-name": "level3",
+                "pools": [ { "pool": "192.0.2.100-192.0.2.200" } ],
+                "option-data": [ {
+                    "name": "routers",
+                    "data": "192.0.2.1"
+                } ]
+            }
+        ],
+        "remote": {
+            "type": "mysql"
+        }
+    }
+}
+          </screen>
+          </para>
+
+          <para>It creates the subnet and associates the subnet with the "level3"
+          shared network. The "level3" must be created with the
+          <command>remote-network4-set</command> prior to creating the subnet.
+          </para>
+
+          <para>If the created subnet must be global (not associated with any
+          shared network), the <command>shared-network-name</command> must be
+          explicitly set to <command>null</command>:
+          <screen>
+{
+    "command": "remote-subnet4-set",
+    "arguments": {
+        "subnets": [
+            {
+                "id": 5,
+                "subnet": "192.0.2.0/24",
+                "shared-network-name": null,
+                "pools": [ { "pool": "192.0.2.100-192.0.2.200" } ],
+                "option-data": [ {
+                    "name": "routers",
+                    "data": "192.0.2.1"
+                } ]
+           }
+        ]
+    }
+}
+          </screen>
+          </para>
+
+          <para>The subnet created in the previous example is replaced with the
+          new subnet having the same parameters but it becomes global.</para>
+
+          <para>The <command>shared-network-name</command> parameter is mandatory
+          for the <command>remote-subnet4-set</command> command.</para>
+
+          <note>
+            <para>
+              Same as for other "set" commands, this command replaces the entire
+              information about the particular subnet in the database, if the subnet
+              information is already present. Therefore, when sending this command,
+              make sure to always include all parameters that must be specified for
+              the updated subnet instance. Any unspecified parameter will be marked
+              as unspecified in the database, even if its value was present prior to
+              sending the command.
+            </para>
+          </note>
+        </section>
+
+      </section>
+
+    </section>
diff --git a/doc/guide/hooks.xml b/doc/guide/hooks.xml
index a1823ee0e286de0f2e931259e61dd339019257f9..8dfe69052016409adee139f9f3496d14f64247aa 100644
--- a/doc/guide/hooks.xml
+++ b/doc/guide/hooks.xml
@@ -595,10 +595,42 @@ $ <userinput>ls -l /usr/local/lib/hooks/*.so</userinput>
               need to restart the DHCP server.
               </entry>
             </row>
+            <row>
+              <entry>MySQL Configuration Backend</entry>
+              <entry>Kea sources</entry>
+              <entry>Kea 1.6.0</entry>
+              <entry>
+                <simplelist>
+                  <member>kea-dhcp4</member>
+                  <member>kea-dhcp6</member>
+                </simplelist>
+              </entry>
+              <entry>The MySQL CB hooks library is an implementation of the Kea
+              Configuration Backend for MySQL. It uses MySQL database as a
+              repository for the Kea configuration information. The Kea servers
+              use this library to fetch their configurations.
+              </entry>
+            </row>
+            <row>
+              <entry>Configuration Backend Commands</entry>
+              <entry>Support customers</entry>
+              <entry>Kea 1.6.0</entry>
+              <entry>
+                <simplelist>
+                  <member>kea-dhcp4</member>
+                  <member>kea-dhcp6</member>
+                </simplelist>
+              </entry>
+              <entry>The Configuration Backend Commands (CB Commands) hooks library
+              implements a collection of commands to manage the configuration
+              information of the Kea servers in the database. This library may
+              only be used in conjuction with one of the supported configuration
+              backend implementations.
+              </entry>
+            </row>
           </tbody>
           </tgroup>
           </table>
-
       </para>
       <para>
         ISC hopes to see more hooks libraries become available as time
@@ -2880,6 +2912,9 @@ both the command and the response.
     <!-- section class-cmds-library -->
     <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="hooks-class-cmds.xml"/>
 
+    <!-- section cb-cmds-library -->
+    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="hooks-cb-cmds.xml"/>
+
     <!-- section high-availability-library -->
     <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="hooks-ha.xml"/>