From: Karl Heiss <kheiss@xxxxxxxxx> Date: Fri, 25 Apr 2014 14:26:30 -0400 > Don't transition to the PF state on every strike after 'Path.Max.Retrans'. > Per draft-ietf-tsvwg-sctp-failover-03 Section 5.1.6: > > Additional (PMR - PFMR) consecutive timeouts on a PF destination > confirm the path failure, upon which the destination transitions to the > Inactive state. As described in [RFC4960], the sender (i) SHOULD notify > ULP about this state transition, and (ii) transmit heartbeats to the > Inactive destination at a lower frequency as described in Section 8.3 of > [RFC4960]. > > This also prevents sending SCTP_ADDR_UNREACHABLE to the user as the state > bounces between SCTP_INACTIVE and SCTP_PF for each subsequent strike. > > Signed-off-by: Karl Heiss <kheiss@xxxxxxxxx> Applied and queued up for -stable, thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
