Re: quick failover in SCTP

Preethi Natarajan <prenatar@cisco.com> Thu, 14 October 2010 20:35 UTC

Return-Path: <prenatar@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3479C3A69A8 for <tsvwg@core3.amsl.com>; Thu, 14 Oct 2010 13:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.632
X-Spam-Level:
X-Spam-Status: No, score=-7.632 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_28=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2JbRCbFt3vlY for <tsvwg@core3.amsl.com>; Thu, 14 Oct 2010 13:35:05 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id E89163A6A0A for <tsvwg@ietf.org>; Thu, 14 Oct 2010 13:35:03 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFABcGt0ytJV2d/2dsb2JhbAChIAJxpS2dAYVIBIRThXODCYRe
X-IronPort-AV: E=Sophos;i="4.57,332,1283731200"; d="scan'208";a="170590807"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rtp-iport-1.cisco.com with ESMTP; 14 Oct 2010 20:36:23 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id o9EKaM9J028354; Thu, 14 Oct 2010 20:36:22 GMT
Received: from xmb-rcd-208.cisco.com ([72.163.62.215]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 14 Oct 2010 15:36:23 -0500
Received: from 171.71.57.122 ([171.71.57.122]) by XMB-RCD-208.cisco.com ([72.163.62.215]) with Microsoft Exchange Server HTTP-DAV ; Thu, 14 Oct 2010 20:36:22 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Thu, 14 Oct 2010 13:36:21 -0700
Subject: Re: quick failover in SCTP
From: Preethi Natarajan <prenatar@cisco.com>
To: Michael Tüxen <Michael.Tuexen@lurchi.franken.de>
Message-ID: <C8DCB7D5.981D%prenatar@cisco.com>
Thread-Topic: quick failover in SCTP
Thread-Index: Actr33Xk6fMFFfZ4Y02ZTN+ru5a8uQ==
In-Reply-To: <73957417-9AE7-4C7E-A042-BC29033E9865@lurchi.franken.de>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 14 Oct 2010 20:36:23.0128 (UTC) FILETIME=[77298580:01CB6BDF]
X-Mailman-Approved-At: Wed, 27 Oct 2010 08:21:09 -0700
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 20:35:06 -0000

On 10/11/10 10:01 AM, "Michael Tüxen" <Michael.Tuexen@lurchi.franken.de>
wrote:
>> 
>> Preethi: Michael can you clarify this a bit? Looks like we want to confirm
>> the following -- apps can control only those HBs that get sent (or not sent)
>> during path failure. Apps do not have control over PF HBs; i.e., apps cannot
>> enable/disable PF HBs. Is that right?
> The socket API allows to configure the HB.interval and to enable/disable
> HBs at all. What I suggest is the no matter if the HB are disabled, they
> are sent for
> * initial path verification (not within the scope of your ID, but noted
>   to make things clear)
> * getting a path out of potentially failed or failed.
> In other words: If the application disables HBs, it only enables the
> ones which do path supervision when the path is active and not potentially
> failed.
> 
> Does this clarify things?

Yes, thanks.

Preethi