IETF Logo Mail Archive

Re: [IPsec] Working Group LC: draft-ietf-ipsecme-ipsec-ha-03

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 25 May 2010 18:14 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 0F1E63A6987 for <ipsec@core3.amsl.com>; Tue, 25 May 2010 11:14:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
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 wBLcEuRM9jci for <ipsec@core3.amsl.com>; Tue, 25 May 2010 11:14:52 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 95A023A6998 for <ipsec@ietf.org>; Tue, 25 May 2010 11:14:48 -0700 (PDT)
Received: by fxm6 with SMTP id 6so590257fxm.31 for <ipsec@ietf.org>; Tue, 25 May 2010 11:14:35 -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:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=LelLnAgdiqndH7jZ+8B1MNgsuvOLnXz782qGfC02yVI=; b=fV59dvjQFSjmdChrtRlXQwkgZldGN605b8TC4N4Nqja8jLORSqD6HEcfcaOb4Wq0qG CWFYiOx2ObKC2r2dPIDXqqs9ICScPaHjZxT9FB1d6JOaFepRwetTvQHUr27FOxkEBFgP sYHD08GgX/uixjbYy3tGYzzg9HERoDBop9S2c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=jAQiWqrtbRN4LKQ8qh88Ke7ofnVetlBtRej5BrjqXFu15h4Gp1qAaibos7qdAe4BEK aOUdnohmwNuuL9FX+f1OpMM4DoiauM987W2razqIBdn33Ylz+51ypG5m0pyzkSJJbdHe nk3w2z08AVLlS4/ebs//DgRqKoIwvalhSi9VY=
Received: by 10.223.144.77 with SMTP id y13mr6848995fau.86.1274811273471; Tue, 25 May 2010 11:14:33 -0700 (PDT)
Received: from [10.0.0.1] (bzq-79-178-45-8.red.bezeqint.net [79.178.45.8]) by mx.google.com with ESMTPS id r25sm25902418fai.11.2010.05.25.11.14.31 (version=SSLv3 cipher=RC4-MD5); Tue, 25 May 2010 11:14:32 -0700 (PDT)
Message-ID: <4BFC1384.2030905@gmail.com>
Date: Tue, 25 May 2010 21:14:28 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Lightning/1.0b1 Thunderbird/3.0.4
MIME-Version: 1.0
To: IPsecme WG <ipsec@ietf.org>
References: <4BEFEAE6.2060700@gmail.com>
In-Reply-To: <4BEFEAE6.2060700@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [IPsec] Working Group LC: draft-ietf-ipsecme-ipsec-ha-03
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, 25 May 2010 18:14:55 -0000

With 5 more days to go, this is a quick reminder to review the problem 
statement draft so we can move it along, and get to the juicy protocol 
stuff.

This time around, we will take silence as agreement.

Thanks,
	Yaron

On 05/16/2010 03:53 PM, Yaron Sheffer wrote:
> This is to begin a 2 week working group last call for
> draft-ietf-ipsecme-ipsec-ha-03
> (http://tools.ietf.org/html/draft-ietf-ipsecme-ipsec-ha-03). The target
> status for this document is Informational.
>
> Please send your comments to the ipsec list by May 30, 2010, as
> follow-ups to this message.
>
> Brief comments of the form: "I have read this draft and it looks fine"
> are also welcome.
>
> Quick heads up: this is a requirements definition draft. Once we have
> determined consensus around it, we would like to move forward with
> solutions. Individual solution drafts are welcome as usual, but we would
> like to establish at some point a design team to hash out a common
> solution document. Let us know by private mail if you're interested.
>
> Thanks,
> Yaron

v2.23.0 | Report a Bug | By Email