From: Tomek Mrugalski Date: Wed, 21 Oct 2020 10:57:23 +0000 (+0200) Subject: [#1460] updated RFC8925 references X-Git-Tag: Kea-1.9.1~25 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=65b621cb6a2c26f08b338c7c73bee82c4ee76a89;p=thirdparty%2Fkea.git [#1460] updated RFC8925 references --- diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst index 7b21330b20..71e0a44883 100644 --- a/doc/sphinx/arm/dhcp4-srv.rst +++ b/doc/sphinx/arm/dhcp4-srv.rst @@ -3919,9 +3919,8 @@ Our tests reported best results when: IPv6-only Preferred Networks ---------------------------- -A recent Internet-Draft `draft-ietf-dhc-v6only -`_ soon to be published by IETF as -RFC specifies a DHCPv4 option to indicate that a host supports an IPv6-only mode and is willing to +A `RFC8925 `_ recently published by IETF +specifies a DHCPv4 option to indicate that a host supports an IPv6-only mode and is willing to forgo obtaining an IPv4 address if the network provides IPv6 connectivity. The general idea is that a network administrator can enable this option to signal to compatible dual-stack devices that the IPv6 connectivity is available and they can shut down their IPv4 stack. The new option @@ -6391,8 +6390,8 @@ The following standards are currently supported: message, remembers the UDP port and sends back reply to the same relay agent using this UDP port. -- *IPv6-Only-Preferred Option for DHCPv4*, `draft-ietf-dhc-v6only-08 - `__: The Kea +- *IPv6-Only Preferred Option for DHCPv4*, `RFC 8925 + `__: The Kea server is able to designate its pools and subnets as v6only-preferred and send back the `v6-only-preferred` option to clients that requested it.