RadSec Keep-Alive mechanism not effective for all RadSec servers

[fkm-gk]

We have noticed that the RadSec Keep-Alive feature is currently implemented by triggering period empty TCP headers with ACK flag. While this is sufficient to keep TLS sessions open with most (intermediate) firewalls, some RadSec server implementations require application data (Status-Server) messages to be delivered for them to keep the session open (freeRADIUS, RADIUSaaS). Hence, the feature might be uneffective in some cases.

Based on this, is there a possibility for Meraki to making this feature more robust by sending Status Server messages?

------------------------------------------------------------------

Initially posted here: https://community.meraki.com/t5/API-Early-Access-Discussions/RadSec-Keep-Alive-mechanism-not-effecti...

[MaghM]

Status-Server packets are sent by a RADIUS client to a RADIUS server in order to test the status of that server.
The Status-Server packet is not a "Keep-Alive" as discussed in [RFC2865], Section 2.6.