Maintain ClientConnection after "Failed to parse ASDU"

[mkroesen]

The following ASDU leads to the termination of the ClientConnection:

CS104 SLAVE CONNECTION 348: Handle received ASDU
CS104 SLAVE CONNECTION 348: RCVD: 68-24-0C-00-00-00-87-01-14-00-FC-19-0D-94-01-0D-14-FE-FC-19-02-83-DE-C0-04-01-01-09-00-00-5C-44-03-8D-63-08-16-FF
CS104 SLAVE CONNECTION 348: Received I frame: N(S) = 6 N(R) = 0
CS104 SLAVE CONNECTION 348: Enqueue received I-message for processing
CS104 SLAVE CONNECTION 348: Failed to parse ASDU --> close connection
CS104 SLAVE CONNECTION 348: CLOSE CONNECTION!
CS104 SLAVE CONNECTION 348: CONNECTION CLOSED!

This ASDU (TypeID = 135) is not supported by your stack.
Is there a possibility to maintain the connection in case of an unknown ASDU and to handle the ASDU manually or is this behaviour desired and if yes, with which reasoning?

In theory, one would need a RawASDUHandler to decide how to handle these ASDUs to prevent the connection from being terminated.