From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v4 net] net: sctp: Don't transition to PF state when transport has exhausted 'Path.Max.Retrans'. Date: Sun, 27 Apr 2014 23:41:50 -0400 (EDT) Message-ID: <20140427.234150.128600841189069583.davem@davemloft.net> References: <1398450390-23630-1-git-send-email-kheiss@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org, vyasevich@gmail.com, nhorman@tuxdriver.com To: kheiss@gmail.com Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:36346 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751386AbaD1Dlw (ORCPT ); Sun, 27 Apr 2014 23:41:52 -0400 In-Reply-To: <1398450390-23630-1-git-send-email-kheiss@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Karl Heiss 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 Applied and queued up for -stable, thanks.