This object is the current T3-rtx retransmission timeout in effect for one specific remote address of this association. Since SCTP tracks RTO per destination address, not just per association, in a multihomed setup, this lets an admin see that one particular path to the peer has a much higher computed RTO than another, revealing that specific path is slower or lossier. A secondary remote address with RTO climbing to 8000 milliseconds while the primary address's RTO sits at 400 milliseconds shows that backup path is far slower and would introduce noticeable delay if failover to it occurred.