Re: [IPsec] Issue #177. (was: HA/LS terminology)

"Dan Harkins" <dharkins@lounge.org> Wed, 24 March 2010 01:05 UTC

Return-Path: <dharkins@lounge.org>
X-Original-To: ipsec@core3.amsl.com
Delivered-To: ipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01FCC3A6BD1 for <ipsec@core3.amsl.com>; Tue, 23 Mar 2010 18:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level:
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 1DhtLSfiFxou for <ipsec@core3.amsl.com>; Tue, 23 Mar 2010 18:05:32 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by core3.amsl.com (Postfix) with ESMTP id E424C3A6BB2 for <ipsec@ietf.org>; Tue, 23 Mar 2010 18:05:32 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 03AF91022404A; Tue, 23 Mar 2010 18:05:52 -0700 (PDT)
Received: from 130.129.26.143 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Tue, 23 Mar 2010 18:05:52 -0700 (PDT)
Message-ID: <f0aa47a3042adbe0b70d3befbcc8f468.squirrel@www.trepanning.net>
In-Reply-To: <3B0BF1DE-83E0-413E-A09E-146F8B2C7C9B@checkpoint.com>
References: <7EF09073-9D20-4077-A8DD-59B84B1732D0@sfc.wide.ad.jp> <7bc30fde97954c9f651eb436c822dab7.squirrel@webmail.arsc.edu> <118D7A1E-6090-4D71-9FEB-89AEB189CA94@sfc.wide.ad.jp> <1699285A-BDB7-40A6-BA58-5228AAE1133A@checkpoint.com> <1eac10bbf0fee9817dbc4c681868daa2.squirrel@webmail.arsc.edu> <3B0BF1DE-83E0-413E-A09E-146F8B2C7C9B@checkpoint.com>
Date: Tue, 23 Mar 2010 18:05:52 -0700 (PDT)
From: "Dan Harkins" <dharkins@lounge.org>
To: "Yoav Nir" <ynir@checkpoint.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Rodney Van Meter <rdv@sfc.wide.ad.jp>, "ipsec@ietf.org" <ipsec@ietf.org>, Melinda Shore <shore@arsc.edu>
Subject: Re: [IPsec] Issue #177. (was: HA/LS terminology)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 01:05:34 -0000

  Hi,

  "hot standby" implies a box sitting ("hot") twiddling its thumbs doing
little but waiting for another box to fail ("standby"). It's the VRRP
model.

  There is a HA model which supports dynamic load balancing as well as
active session failover. Nodes in such a cluster are not "standby". They
each have loads that they can shed and add to based upon some heuristic.
A neat attribute of such a system is that an IPsec SA can be established
on node A, move to node B after a while, and come back to A some time
later without any actual node failure. State moves around to keep the
cluster balanced.

  I would very much prefer "session failover" to "hot standby" and a
mild preference of "load balancing" over "load sharing". An HA model
doing VRRP could be termed "session failover" but the HA model described
above really can't be called "hot standby". And load can be shared but
just sharing a load can result in a mis-balanced cluster if sessions on
one node terminate naturally and it sits doing little while another node
whose sessions haven't terminated is huffing-and-puffing. Balancing can
imply sharing but not vice versa.

  regards,

  Dan.

On Tue, March 23, 2010 2:43 pm, Yoav Nir wrote:
> On Mar 23, 2010, at 2:31 PM, Melinda Shore wrote:
>
>> On Tue, March 23, 2010 1:20 pm, Yoav Nir wrote:
>>> - For the cluster with just one member doing IKE and IPsec, I propose
>>> "hot-standby cluster"
>>> - For the cluster with several members doing IKE and IPsec, I propose
>>> to
>>> keep "load-sharing cluster"
>>
>> I think "failover" is in broader use than "hot standby"
>> and would tend to prefer it myself, but I think either is clear.
>>
>> Melinda
>>
> I did not want to use "fault tolerant" because some would take that term
> is broad and sometimes taken to mean things I would not like to specify,
> like RAID arrays, and dual power supplies.  I don't think we should use
> this item to mandate that the two cluster members should not be connected
> to the same power strip.
>
> Anyway, "failover cluster" is OK, except that we've already used
> "failover" to describe an event that happens to both types of clusters.
> So I think we can stay with "hot standby" and "load sharing"
>
> Yoav
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>