[#4356] New proposal

diff --git a/doc/sphinx/arm/ext-radius.rst b/doc/sphinx/arm/ext-radius.rst
index af7763e952386f935031e7a36c1d928d14a1ee18..29779be20ab6279c852c1310e84b1c0a263cd44f 100644 (file)
--- a/doc/sphinx/arm/ext-radius.rst
+++ b/doc/sphinx/arm/ext-radius.rst
@@ -26,15 +26,17 @@ on HMAC-MD5 so not vulnerable and supported by Kea 3.1.5) so even when
 the infrastructure is protected, the RADIUS deployment is impacted by
 Blast-RADIUS.
 
-The proposed solutions for Kea release 3.1.6 are to support
-RADIUS/TLS which provides a built-in cryptographic protection
-of communication between RADIUS clients and servers, known as
-the long-term solution, and also the short-term solution so
-add a Message-Authenticator attribute in all sent messages
-and require it in all received messages (note the second point
-is enforced only by recent RADIUS servers). These solutions
-are experimental.
+The solutions provided by Kea release 3.1.6 are:
 
+1. To support RADIUS/TLS which provides a built-in cryptographic
+protection of communication between RADIUS clients and servers. 
+This is known as the long-term solution.
+
+2. To support the short-term solution by adding a Message-Authenticator
+attribute in all sent messages and requiring it in all received messages
+(note the second point is enforced only by recent RADIUS servers).
+
+These solutions are experimental.
 
 .. _radius-overview: