IETF Logo Mail Archive

Re: [IPsec] New version of IPsec Cluster Solution Draft posted [earliar, HA design team started]

Yaron Sheffer <yaronf.ietf@gmail.com> Mon, 19 July 2010 17:25 UTC

Return-Path: <yaronf.ietf@gmail.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 5D53C3A687D for <ipsec@core3.amsl.com>; Mon, 19 Jul 2010 10:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 pLfnNjo7KnJn for <ipsec@core3.amsl.com>; Mon, 19 Jul 2010 10:25:58 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 40ACB3A67AC for <ipsec@ietf.org>; Mon, 19 Jul 2010 10:25:58 -0700 (PDT)
Received: by wwb39 with SMTP id 39so349638wwb.13 for <ipsec@ietf.org>; Mon, 19 Jul 2010 10:26:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=U+A7/ekK22z+R217B5UEf5qPh8YVCVmjGgtVTriUmvU=; b=AljlD6te/WIVL/7Et48VDlPUp9/2hYa87AfEiZsMBl61JJbIXR9dCWkNnV/TV7/h3j UGlpvJYojgSsTkr/xwMKBUgANGLeCRdg6yFlAb+1zQuwwhFa55W4dsLvTW7K48ky3T/I KtobGmqCOh7NqceEO638trp/AEYqnOy2YZnc4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=rNoIElEVQBB/ihZIURERES9pQLGIXuFCrUqhTqyvgIubIo1kcjWvIHuhQGRCfr6yyv nxTBhA2sVYINrA/IAxuwpMse+yZZ3ibd6XTLsJuaiaPabY3zKvBowSmzBsgMEIWNbFW/ B1IozrheQhA33cV2iYeDhTGYLL3q5W/PE04a8=
Received: by 10.227.138.5 with SMTP id y5mr4347175wbt.204.1279560372339; Mon, 19 Jul 2010 10:26:12 -0700 (PDT)
Received: from [10.0.0.1] (bzq-79-177-34-148.red.bezeqint.net [79.177.34.148]) by mx.google.com with ESMTPS id g37sm42441067wbg.15.2010.07.19.10.26.10 (version=SSLv3 cipher=RC4-MD5); Mon, 19 Jul 2010 10:26:11 -0700 (PDT)
Message-ID: <4C448AB1.5080305@gmail.com>
Date: Mon, 19 Jul 2010 20:26:09 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100527 Lightning/1.0b1 Thunderbird/3.0.5
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <AANLkTinsIhov3aVuKqVRf7gmHG5oG70e5OoM6yWc7NAQ@mail.gmail.com> <4C447891.8060708@gmail.com> <p06240812c86a35022352@[10.20.30.158]>
In-Reply-To: <p06240812c86a35022352@[10.20.30.158]>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IPsecme WG <ipsec@ietf.org>
Subject: Re: [IPsec] New version of IPsec Cluster Solution Draft posted [earliar, HA design team started]
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: Mon, 19 Jul 2010 17:25:59 -0000

Sec. 3 of the draft lists each of the issues described in the Problem 
Statement, and explains how it is resolved.

Thanks,
	Yaron

On 07/19/2010 08:02 PM, Paul Hoffman wrote:
> First off: thank you to the design team for the work you put into this. The rest of the WG didn't see this, but the group worked hard and met often.
>
> One of the things that interests me as chair is: does this proposed protocol meet the requirement set out in our RFC-to-be<http://www.ietf.org/internet-drafts/draft-ietf-ipsecme-ipsec-ha-09.txt>? If not, what is missing, and can it be added easily to the proposed protocol?
>
> This will definitely be one of the points of discussion a week from now in Maastricht, but folks can start discussing it here on the list now in preparation for the meeting.
>
> --Paul Hoffman, Director
> --VPN Consortium
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

v2.23.0 | Report a Bug | By Email