Re: [IPsec] WESP and reliability

RJ Atkinson <rja.lists@gmail.com> Wed, 04 January 2012 18:59 UTC

Return-Path: <rja.lists@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B97A21F855B for <ipsec@ietfa.amsl.com>; Wed, 4 Jan 2012 10:59:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.629
X-Spam-Level:
X-Spam-Status: No, score=-3.629 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GspJ66+qvtJv for <ipsec@ietfa.amsl.com>; Wed, 4 Jan 2012 10:59:13 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 79BE821F8558 for <ipsec@ietf.org>; Wed, 4 Jan 2012 10:59:13 -0800 (PST)
Received: by qcsf15 with SMTP id f15so12586128qcs.31 for <ipsec@ietf.org>; Wed, 04 Jan 2012 10:59:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=rvEpAnRl6j7lxoFhSIR962GpSIim+a3G24H2/AEqKcA=; b=VWlJNwwd3CuppPBxvdQKwZUKNoSCJvK5lm5h8yuikmZBuCKr0BpPzhCZFgMakrOSa1 7eFR3oEL+RtzGF99UJnzTIeOrS0Dz4fTM8uhmU5BAITEp+NPAplf+mPUO3WYLOtIDyCG W7nLrkg69KtMg4cM3ZikMw4/KrTi1Wa0TvcEE=
Received: by 10.229.75.149 with SMTP id y21mr21302341qcj.69.1325703552952; Wed, 04 Jan 2012 10:59:12 -0800 (PST)
Received: from [10.30.20.12] (pool-96-225-134-175.nrflva.fios.verizon.net. [96.225.134.175]) by mx.google.com with ESMTPS id dh10sm108916046qab.19.2012.01.04.10.59.11 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 04 Jan 2012 10:59:12 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <493ECD00-71C7-4471-9B33-9F7F903ECB14@vpnc.org>
Date: Wed, 04 Jan 2012 13:59:11 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <541DCEA7-C5A6-42C6-A1CB-DCF91677FB08@gmail.com>
References: <12533D04-6B3F-490F-935B-4F1FA612C938@gmail.com> <7C362EEF9C7896468B36C9B79200D8350D027BB46F@INBANSXCHMBSA1.in.alcatel-lucent.com> <F1B15794-3291-4E71-BE26-A3559F408B01@gmail.com> <7C362EEF9C7896468B36C9B79200D8350D027BB484@INBANSXCHMBSA1.in.alcatel-lucent.com> <23AFA108-5B72-4CB0-8498-6CC27FC79F96@gmail.com> <CAA1nO734gfXYJLeLU9iYxoArPZJ3Xo3MsXy0Rt9zgoTciBCZbQ@mail.gmail.com> <CAK3OfOg0Gsxxf8T66XNVLHtR1Tk9yHFDGw96tr0UkEh6x5uYpQ@mail.gmail.com> <48CB2A9F-D59C-462F-8C7A-82127A217703@gmail.com> <7C362EEF9C7896468B36C9B79200D8350D028A2AE4@INBANSXCHMBSA1.in.alcatel-lucent.com> <5C745AC3-FA25-42BE-9848-DDEA3078A1FF@gmail.com> <493ECD00-71C7-4471-9B33-9F7F903ECB14@vpnc.org>
To: IPsec ME WG List <ipsec@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [IPsec] WESP and reliability
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 04 Jan 2012 18:59:14 -0000

On 04  Jan 2012, at 13:46 , Paul Hoffman wrote:

> On Jan 4, 2012, at 10:37 AM, RJ Atkinson wrote:
>> Neither WESP nor the other document provide a 100% reliable way 
>> to parse-into/parse-past/deep-inspect ESP packets.  One might 
>> wish otherwise, but the reality is that there is no 100%
>> reliable method today.
> 
> Can you give an example where WESP (a protocol that was
> done in this WG) is not 100% reliable for parse-into
> or parse-past? If we need to change the protocol, we should.

Such packets have been encountered by prototype 
implementations in at least one firewall.  I will
certainly encourage those folks to share a sample
packet here, but they don't usually show up at IETF
and can be very shy.

I think WESP was a valiant try, and it seems to work
most of the time.  It is just sad that the result 
just doesn't work in all cases.  

An entirely separate issue is that WESP is not generally
available yet.  One hopes that WESP support will become
available soon, but that's not generally true now.

Yours,

Ran