Re: [MEXT] Review of draft draft-patil-mext-mip6issueswithipsec-01

jouni korhonen <jouni.nospam@gmail.com> Mon, 27 July 2009 21:32 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C2F93A6D64 for <mext@core3.amsl.com>; Mon, 27 Jul 2009 14:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 UCQwit+2Nv71 for <mext@core3.amsl.com>; Mon, 27 Jul 2009 14:32:34 -0700 (PDT)
Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by core3.amsl.com (Postfix) with ESMTP id 588143A6B29 for <mext@ietf.org>; Mon, 27 Jul 2009 14:32:34 -0700 (PDT)
Received: by ewy26 with SMTP id 26so3530401ewy.37 for <mext@ietf.org>; Mon, 27 Jul 2009 14:32:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=ARzLNCx9vpK+1/a1kbcCpyqAoznFyj7sG5JgtLkAkwI=; b=wF4TokMTKdlq/PscLCdEMcQpJlHd30UlEZcLewVxHgq72E+X9zt5gQ0jchHQ4vM3y7 2MHwaA2VECQYzNR9sUw3nitPp1xHghK7lZ9G1UjdwS2wCjkmqDm9YSnh72YWtH/6FKpU FJ1SxbaiTd3SwmkfNC1BX7s/nkVJcUvMlNAd0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=Pfto78a5ZB7ht7jVSlt07GAffs4kmFIH/8/FDYJECdIeoWOnZ7osaoq+6Wnagt7rku qXofDPkGgwV7zs7wIu6sKzVETEz07d25uasxUG00kkZ+QI6yj7gRHUKYnhKxyaAvGpEH UvA+tBCrUAJA7fJ0uaL20bLnrrM/RKz+pN/S4=
Received: by 10.210.86.1 with SMTP id j1mr8921892ebb.27.1248730352962; Mon, 27 Jul 2009 14:32:32 -0700 (PDT)
Received: from ?10.102.80.55? ([77.241.100.67]) by mx.google.com with ESMTPS id 24sm761184eyx.33.2009.07.27.14.32.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 27 Jul 2009 14:32:32 -0700 (PDT)
Message-Id: <B98198A1-D668-45C1-A95E-82FA80535CC2@gmail.com>
From: jouni korhonen <jouni.nospam@gmail.com>
To: Arnaud Ebalard <arno@natisbad.org>
In-Reply-To: <87r5w1j280.fsf@small.ssi.corp>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 28 Jul 2009 00:32:27 +0300
References: <C68F84FA.2B9FF%basavaraj.patil@nokia.com> <87tz0xkjps.fsf@small.ssi.corp> <F4B05442-4556-4514-AD51-E89575E1E6BF@gmail.com> <87r5w1j280.fsf@small.ssi.corp>
X-Mailer: Apple Mail (2.935.3)
Cc: mext@ietf.org, Basavaraj.Patil@nokia.com
Subject: Re: [MEXT] Review of draft draft-patil-mext-mip6issueswithipsec-01
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 21:32:35 -0000

Hi Arnaud,

On Jul 27, 2009, at 11:33 PM, Arnaud Ebalard wrote:

> Hi,
>
> jouni korhonen <jouni.nospam@gmail.com> writes:
>
>> Hi Arnaud,
>>
>> Commenting one point here at this time.
>>
>> On Jul 27, 2009, at 10:29 PM, Arnaud Ebalard wrote:
>>
>> [snip]
>>
>>>
>>> o You use the IPsec stack to protect traffic using ESP. You use SA  
>>> for
>>>  that purpose. There is nothing in the document about associated
>>>  Security Policies (SP). Are the ones defined in 3776 reused?
>>>  Can you clarify that point?
>>
>> This is a common misunderstanding due to using term 'ESP' in the
>> I-D. There is no reference nor intent to use IPsec as per RFC4301.  
>> The
>> I-D  only *reuses* the ESP format for encapsulation as what we came  
>> up
>> ourselves looked more or less ESP format. We will (most probably)
>> remove all references to 'ESP' in the future to avoid this mixup.
>
> Just to be sure: you mean you will not use the algorithms  
> implemented in
> the IPsec kernel stack but reimplement everything in userland?

No IPsec kernel stack involved. I am not sure what algorithms you are  
referring here.

Cheers,
	Jouni


>
> Cheers,
>
> a+