Re: [IPsec] WG Last Call on draft-ietf-ipsecme-ipsecha-protocol

Yaron Sheffer <yaronf.ietf@gmail.com> Wed, 23 March 2011 21:58 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 CB8703A6957 for <ipsec@core3.amsl.com>; Wed, 23 Mar 2011 14:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 cmJwQ0+ZjJ-o for <ipsec@core3.amsl.com>; Wed, 23 Mar 2011 14:58:33 -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 BE15E3A68B3 for <ipsec@ietf.org>; Wed, 23 Mar 2011 14:58:32 -0700 (PDT)
Received: by fxm15 with SMTP id 15so8436921fxm.31 for <ipsec@ietf.org>; Wed, 23 Mar 2011 15:00:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6yLVhl0J6ztgUFvqTdQaUWwEEjAsh2t9f4VnN3e6tew=; b=NbD5TiBEUAI5rTir/GaEV516VdiiBiCx1EkqsJk2rNtsJry3bZ7WOjS/AW/iw1U7dl HJgcTnMnSP/pwncz6HquPYQmc4tkNrYCWB8OuiKrLJu5KfOBVKiinA/vwasEdJPwE0gz DbFfolxugQv0KzXHetLLz7zZ8Y/0PUtT/eLxo=
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=SvEwowqAS8bXae5H6fQTqXuYnYhdrjhoP4abljgPLda8ajj410gMvtxbK4/+4JWv9w NUOD+rkL7IQR7LgAWv1B21J1oKW5AeRG75dgD7xwzeffo5uNVHU1+tDRPGdwAyR6PZYb T8oRTYTKDsn29isDypOOcg0MsKawB7I0k4dII=
Received: by 10.223.55.12 with SMTP id s12mr3634985fag.124.1300917606480; Wed, 23 Mar 2011 15:00:06 -0700 (PDT)
Received: from [10.0.0.1] (bzq-79-177-11-1.red.bezeqint.net [79.177.11.1]) by mx.google.com with ESMTPS id 21sm3653995fav.41.2011.03.23.15.00.04 (version=SSLv3 cipher=OTHER); Wed, 23 Mar 2011 15:00:04 -0700 (PDT)
Message-ID: <4D8A6D63.5070204@gmail.com>
Date: Thu, 24 Mar 2011 00:00:03 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: IPsecme WG <ipsec@ietf.org>
References: <4D77D633.8070903@gmail.com>
In-Reply-To: <4D77D633.8070903@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [IPsec] WG Last Call on draft-ietf-ipsecme-ipsecha-protocol
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, 23 Mar 2011 21:58:34 -0000

Hi everyone,

The 2-week LC period is up today. I'm afraid we got much less review 
than we would have liked, and further review/comments would be very welcome.

However since we've had good WG input on earlier iterations of this 
document, we are asking Sean, the security AD, to progress the draft.

Thanks,
     Yaron

On 03/09/2011 09:34 PM, Yaron Sheffer wrote:
> This begins a two-week Working Group Last Call on
> draft-ietf-ipsecme-ipsecha-protocol. You can find the current version at
> http://tools.ietf.org/html/draft-ietf-ipsecme-ipsecha-protocol-04. We
> want everyone in the WG to read the document and comment on it, even if
> the comment is "I support this" or "I am neutral on this". If you oppose
> moving the draft forwards, or you have technical changes you want made,
> please be explicit in your message. Feel free to start new threads if
> you are objecting or suggesting changes. The authors will manage any
> such discussions using the issue tracker.
>
> The WG previously reached consensus on a problem statement for IPsec
> High Availability, http://tools.ietf.org/html/rfc6027. You may wish to
> refer to that RFC, first, to frame the problem, and second, to convince
> yourselves that the current document actually addresses it in full.
>
> Thanks,
> Yaron
>