From: Tomek Mrugalski <tomasz@isc.org>
Date: Thu, 8 Aug 2019 13:47:02 +0000 (+0200)
Subject: [#623,!442] Added RFCs related to DNS updates
X-Git-Tag: Kea-1.6.0~41^2~131
X-Git-Url: http://git.ipfire.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=9017ed0ef21ebd7ccb53721f6c34a00678d8accb;p=thirdparty%2Fkea.git

[#623,!442] Added RFCs related to DNS updates
---

diff --git a/doc/sphinx/arm/ddns.rst b/doc/sphinx/arm/ddns.rst
index 5e496ce4cf..49cc13b1d9 100644
--- a/doc/sphinx/arm/ddns.rst
+++ b/doc/sphinx/arm/ddns.rst
@@ -817,3 +817,21 @@ The following are the current limitations of the DHCP-DDNS Server.
 -  Requests received from the DHCP servers are placed in a queue until
    they are processed. Currently, all queued requests are lost if the
    server shuts down.
+
+Supported Standards
+===================
+
+The following RFCs are supported by the DHCP-DDNS server:
+
+- *Secret Key Transaction Authentication for DNS (TSIG)*, `RFC 2845
+  <https://tools.ietf.org/html/rfc2845>`__: All DNS Update packets sent and
+  received by DHCP-DDNS server can be protected by TSIG signatures.
+
+- *Dynamic Updates in the Domain Name System (DNS UPDATE)*, `RFC 2136
+  <https://tools.ietf.org/html/rfc2136>`__: The whole DNS Update mechanism is
+  supported.
+
+- *A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol
+  (DHCP) Information (DHCID RR)*, `RFC 4701
+  <https://tools.ietf.org/html/rfc4701>`__: The DHCP-DDNS server uses the DHCID
+  records.
diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst
index 835cd5bf0d..95a0c0f8bf 100644
--- a/doc/sphinx/arm/dhcp4-srv.rst
+++ b/doc/sphinx/arm/dhcp4-srv.rst
@@ -5503,6 +5503,18 @@ The following standards are currently supported:
    Vendor Class and Vendor-Identifying Vendor-Specific Information
    options are supported.
 
+-  *The Dynamic Host Configuration Protocol (DHCP) Client Fully
+   Qualified Domain Name (FQDN) Option*, `RFC 4702
+   <https://tools.ietf.org/html/rfc4702>`__: The Kea server is able to
+   handle the Client FQDN option. Also, it is able to use
+   kea-dhcp-ddns compontent do initiate appropriate DNS Update
+   operations.
+
+-  *Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host
+   Configuration Protocol (DHCP) Clients*, `RFC 4703
+   <https://tools.ietf.org/html/rfc4703>`__: The DHCPv6 server uses DHCP-DDNS
+   server to resolve conflicts.
+
 -  *Client Identifier Option in DHCP Server Replies*, `RFC
    6842 <https://tools.ietf.org/html/rfc6842>`__: Server by default sends
    back client-id option. That capability may be disabled. See :ref:`dhcp4-echo-client-id` for details.
diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst
index 1b9c1e6b9d..8a013a1520 100644
--- a/doc/sphinx/arm/dhcp6-srv.rst
+++ b/doc/sphinx/arm/dhcp6-srv.rst
@@ -5543,6 +5543,11 @@ The following standards are currently supported:
    4649 <https://tools.ietf.org/html/rfc4649>`__: REMOTE-ID option is
    supported.
 
+-  *Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host
+   Configuration Protocol (DHCP) Clients*, `RFC 4703
+   <https://tools.ietf.org/html/rfc4703>`__: The DHCPv6 server uses DHCP-DDNS
+   server to resolve conflicts.
+
 -  *The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client
    Fully Qualified Domain Name (FQDN) Option*, `RFC
    4704 <https://tools.ietf.org/html/rfc4704>`__: Supported option is