From d33d9a1c2667393a88415511aec80f0b287a7e83 Mon Sep 17 00:00:00 2001 From: ethan-thompson Date: Thu, 5 Sep 2024 11:43:49 -0400 Subject: [PATCH] Added text regarding the parallel connection requests detailed in RFC 6614 Section 2.3 Signed-off-by: ethan-thompson --- draft-ietf-radext-radiusdtls-bis.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/draft-ietf-radext-radiusdtls-bis.md b/draft-ietf-radext-radiusdtls-bis.md index 9363db9..1419761 100644 --- a/draft-ietf-radext-radiusdtls-bis.md +++ b/draft-ietf-radext-radiusdtls-bis.md @@ -210,6 +210,8 @@ As RADIUS has no provisions for capability signaling, there is also no way for a Servers and clients need to be preconfigured to use RADIUS/(D)TLS for a given endpoint. This action has to be taken by the administrators of the two systems. +When a RADIUS/(D)TLS node fails to connect, it leads to continuous retries, with exponentially growing intervals between every try. If multiple servers are defined, the node MAY attempt to establish a connection to these other servers in parallel in order to implement quick failover. + Implementations MUST follow the recommendations given in {{!RFC9325}}.[^add_which]{:jf} Additionally, the following requirements have to be met for the (D)TLS session: