Multicast TTL is not set according to TCP attribute value 8

Value of attribute 8 of TCP/IP object seems to be ignored completely for connections which are producing into multicast groups.

This affects V3.4.0.0 RC3 as presented on the plugfest.

Further investigations:
Currently, always the value 64 is used for the TTL value for sent Class 0/1 frames. This is ok for frames sent to unicast IP addresses. For frames sent to multicast IP addresses the value from attribute 8 must be used.

In addition, the specification state the following:
"[...] When set, the TTL Value attribute shall be saved in non-volatile memory. If a device does not
support applying the TTL Value immediately, the Mcast Pending bit in the Interface Status
attribute shall be set, indicating that there is pending configuration. For devices that support
applying the TTL Value immediately, if there are existing multicast connections, an Object
State Conflict error (0xC) shall be returned and the Mcast Pending bit shall not be set. [...]"

The desired way for the stack should be to immediately apply the TTL value (whithout setting the MCast pending bit).