Re: [IPsec] WESP - Roadmap Ahead

Stephen Kent <kent@bbn.com> Thu, 12 November 2009 03:29 UTC

Return-Path: <kent@bbn.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 D335A3A67AD for <ipsec@core3.amsl.com>; Wed, 11 Nov 2009 19:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level:
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082, 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 Fr08PMYRlDUD for <ipsec@core3.amsl.com>; Wed, 11 Nov 2009 19:29:44 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 18F123A676A for <ipsec@ietf.org>; Wed, 11 Nov 2009 19:29:44 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15] helo=[133.93.16.246]) by smtp.bbn.com with esmtp (Exim 4.63) (envelope-from <kent@bbn.com>) id 1N8QNu-0000gK-9x; Wed, 11 Nov 2009 22:30:10 -0500
Mime-Version: 1.0
Message-Id: <p0624080ac7212e67c860@[133.93.16.246]>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350A681DDBDB@INBANSXCHMBSA1.in.alcatel-luce nt.com>
References: <dc8fd0140911110805q67759507t6cf75a1e9d81c5aa@mail.gmail.com> <p06240800c720d4538dd2@[133.93.112.234]> <7C362EEF9C7896468B36C9B79200D8350A681DDBDB@INBANSXCHMBSA1.in.alcatel-luce nt.com>
Date: Wed, 11 Nov 2009 22:28:25 -0500
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Cc: "ipsec@ietf.org" <ipsec@ietf.org>, Jack Kohn <kohn.jack@gmail.com>
Subject: Re: [IPsec] WESP - Roadmap Ahead
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: Thu, 12 Nov 2009 03:29:44 -0000

At 7:44 AM +0530 11/12/09, Bhatia, Manav (Manav) wrote:
>Steve,
>
>>  I would have no problem deprecating AH in the context of the IPsec
>>  architecture document, if others agree. It is less efficient  than
>>  ESP-NULL. However, other WGs have cited AH as the IPsec protocol of
>>  choice for integrity/authentication in their environments, so there
>>  will be a need to coordinate with them, and it may be unacceptable to
>>  kill AH as a standalone protocol for them.
>
>I agree that it is a trifle too early to start deprecating AH, 
>though I wouldn't mind doing so. OTOH, don't most WGs already 
>suggest AH as a MAY, and ESP-NULL as a MUST?

Not always. For example, I believe that OSPF security makes use of 
AH, outside the IPsec context.

>In any case what should be the stand for the newer work that comes 
>out of these WGs. Should they spell out support for AH, or should 
>they just be talking about ESP (or ESP-NULL or WESP)?

I'd recommend ESP-NULL, unless the context on which the operate might 
require inspection by an intermediate system.

>If we want to deprecate AH, or at least discourage its use in the 
>context of the IPSec architecture in the near future then shouldn't 
>we be working on this?

Part of the problem is that some WGs want to make use of IPsec 
protocols outside of the IPsec architecture.

>  > I am not comfortable with the notion of ESP with WESP.  WESP adds
>  > more per-packet overhead than ESP, and some users are very sensitive
>>  to this aspect of IPsec use. Also, other WG rely on ESP and we would
>>  need to convince them that the packet inspection features of WESP
>>  merit making changes to their standards, which might be a tough sell.
>
>I agree. However, we should start socializing WESP in other WGs so 
>that folks are at least aware of it.

Agree.