Re: [IPsec] Issue #177

Yoav Nir <ynir@checkpoint.com> Tue, 13 April 2010 11:53 UTC

Return-Path: <ynir@checkpoint.com>
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 91EC328C0EC for <ipsec@core3.amsl.com>; Tue, 13 Apr 2010 04:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.763
X-Spam-Level:
X-Spam-Status: No, score=-2.763 tagged_above=-999 required=5 tests=[AWL=0.836, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 8eATKntbl560 for <ipsec@core3.amsl.com>; Tue, 13 Apr 2010 04:53:01 -0700 (PDT)
Received: from michael.checkpoint.com (michael.checkpoint.com [194.29.32.68]) by core3.amsl.com (Postfix) with ESMTP id CF6193A6AF4 for <ipsec@ietf.org>; Tue, 13 Apr 2010 04:52:55 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id o3DBqlph015142; Tue, 13 Apr 2010 14:52:47 +0300 (IDT)
X-CheckPoint: {4BC468BE-0-1211DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Tue, 13 Apr 2010 14:53:14 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Date: Tue, 13 Apr 2010 14:52:46 +0300
Thread-Topic: [IPsec] Issue #177
Thread-Index: Acra/+WjU+0NtJx/Ra2m7Q0bxj3CwA==
Message-ID: <B9D46A20-9BC0-4922-B60F-6FE3C3260F06@checkpoint.com>
References: <5168444B-8DBF-4638-B2E5-BDFD5F1F6BB8@checkpoint.com> <1271150696.3977.11.camel@yaronf-linux> <1271153827.2090.0.camel@yaronf-linux>
In-Reply-To: <1271153827.2090.0.camel@yaronf-linux>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipsec@ietf.org WG" <ipsec@ietf.org>
Subject: Re: [IPsec] Issue #177
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: Tue, 13 Apr 2010 11:53:02 -0000

On Apr 13, 2010, at 1:17 PM, Yaron Sheffer wrote:

> Looks good. A few comments down below.
> 
> 	Yaron
> 
> On Tue, 2010-04-13 at 11:49 +0300, Yoav Nir wrote:
>> 
>>   "Fault Tolerance" is a condition related to high availability, where
>>   a system maintains service availability, even when a specified set of
>>   fault conditions occur.  In clusters, we expect the system to
>>   maintain service availability, when one of the cluster members fails.
> 
> one or more

Agreed. Fixed.

>> 
>>   "Hot Standby Cluster", or "HS Cluster" is a cluster where only one of
>>   the members is active at any one time.  This member is also referred
>>   to as the the "active", whereas the others are referred to as "stand-
>>   bys".  [VRRP] is one method of building such a cluster.
> 
> [Please ignore if you're sick and tired of terminology discussions:] I
> look at the term "hot standby" as contrasted with "warm/cold
> standby" (see http://www.webopedia.com/TERM/H/hot_standby.html). This is
> not what we mean here. Can we use "active-standby" instead?

I can live with that. What do other think?

>>   "Failover" is the event where a one member takes over some load from
>>   some other member.  In a hot standby cluster, this hapens when a
>>   standby memeber becomes active due to a failure of the former active
>>   member, or because of an administrator command.  In a load sharing
>>   cluster this usually happens because of a failure of one of the
>>   members, but certain load-balancing technologies may allow a
>>   particular load (an SA) to move from one member to another to even
>>   out the load, even without any failures.
> 
> The parenthetical "an SA" implies that SAs are never shared between
> members. I suggest that the initial definition of "cluster" mention
> whether we expect IKE and IPsec SAs to be shared between members.

That is not part of terminology. It's mentioned in section 3. How about I change the parenthetical remark to "such as all the flows associated with a particular SA" ?

>>   "Loose Cluster" is a cluster where each member has a different IP
>>   address.  Peers find the correct member using some method such as DNS
>>   queries or [REDIRECT].
> 
> Upon failure, members' IP addresses are reallocated to other members.

They are?