Re: draft-ietf-ipsec-udp-encaps-06 comments.

Ari Huttunen <Ari.Huttunen@f-secure.com> Wed, 11 June 2003 15:31 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13700 for <ipsec-archive@lists.ietf.org>; Wed, 11 Jun 2003 11:31:56 -0400 (EDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id JAA08371 Wed, 11 Jun 2003 09:27:40 -0400 (EDT)
Message-ID: <3EE72FB1.1040507@f-secure.com>
Date: Wed, 11 Jun 2003 16:33:37 +0300
From: Ari Huttunen <Ari.Huttunen@f-secure.com>
Organization: F-Secure Corporation
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Francois Dive <jef@linuxbe.org>
CC: ipsec@lists.tislabs.com
Subject: Re: draft-ietf-ipsec-udp-encaps-06 comments.
References: <20030611113650.GD1043@gardafou.assamite.eu.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Jun 2003 13:33:37.0830 (UTC) FILETIME=[105EB460:01C3301E]
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jean-Francois Dive wrote:
> Hi all,
> 
> I am actually busy with implementing NAT-T in IKEv1 context and found something which may have been
> overlooked (or that i missed the discussion on this list). In section 3.1.2, the author talk about the
> procedure to follow for udp encpasulated transport mode NAT decapsulation. I totally agress with the 
> first point (point (a)) but think the second point (point (b)) is totally wrong and should never be 
> implemented as such: it is suggested that if we dont have the original source or destination ip 
> addresses, the TCP/UDP checksum of the packet should be recomputed to match the NAT'ed ip pseudo header. 
> This cant happen as it would make corrupted packets appears as proper packets, the checksum "mangling"
> or update beeing right as a wrong checksum at the start would remain wrong. The only proper way to 
> deal with this would be to go with checksum update when you have the information and no checksum 
> at all if you dont have the information. 
> 
> Any comments ?

You wouldn't use ESP without authentication, would you? In transport
mode there's no chance that the packet contents accidentally changed
if the packet is authenticated. It wouldn't pass authentication checking.

Ari

-- 
I play it cool and dig all jive,
  that's the reason I stay alive.
   My motto as I live and learn,
    is dig and be dug in return. <Langston Hughes>

Ari Huttunen                   phone: +358 9 2520 0700
Software Architect             fax  : +358 9 2520 5001

F-Secure Corporation       http://www.F-Secure.com

F(ully)-Secure products: Securing the Mobile Enterprise