IETF Logo Mail Archive

Re: [MEXT] Call for WG adoption of I-D: draft-korhonen-mext-mip6-altsec

arno@natisbad.org (Arnaud Ebalard) Tue, 25 January 2011 08:16 UTC

Return-Path: <arno@natisbad.org>
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 045B03A6B76 for <mext@core3.amsl.com>; Tue, 25 Jan 2011 00:16:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 m-32XFNojhWm for <mext@core3.amsl.com>; Tue, 25 Jan 2011 00:15:50 -0800 (PST)
Received: from copper.chdir.org (copper.chdir.org [88.191.97.87]) by core3.amsl.com (Postfix) with ESMTP id 52D2D3A6A87 for <mext@ietf.org>; Tue, 25 Jan 2011 00:15:49 -0800 (PST)
Received: from enough (unknown [IPv6:2001:7a8:1161:20:baac:6fff:fe41:5166]) by copper.chdir.org (Postfix) with ESMTPSA id EE005450053; Tue, 25 Jan 2011 09:18:40 +0100 (CET)
From: arno@natisbad.org
To: Basavaraj.Patil@nokia.com
References: <C963527A.D013%basavaraj.patil@nokia.com>
X-PGP-Key-URL: http://natisbad.org/arno@natisbad.org.asc
X-Fingerprint: D3A5 B68A 839B 38A5 815A 781B B77C 0748 A7AE 341B
X-Hashcash: 1:20:110125:mext@ietf.org::7fiWXaN+m+69Scg9:000016YT
X-Hashcash: 1:20:110125:basavaraj.patil@nokia.com::m3hBHu6g09pqrb/A:0000000000000000000000000000000000001RQi
X-Hashcash: 1:20:110125:julien.laganier.ietf@googlemail.com::EYVWdF9ynKoYeNb4:000000000000000000000000002X/5
X-Hashcash: 1:20:110125:jan@go6.si::/MmuPc5y4UrocE3I:000000056u6
Date: Tue, 25 Jan 2011 09:13:15 +0100
In-Reply-To: <C963527A.D013%basavaraj.patil@nokia.com> (Basavaraj Patil's message of "Mon, 24 Jan 2011 22:03:33 +0000")
Message-ID: <87fwshv1t0.fsf@natisbad.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: julien.laganier.ietf@googlemail.com, jan@go6.si, mext@ietf.org
Subject: Re: [MEXT] Call for WG adoption of I-D: draft-korhonen-mext-mip6-altsec
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: Tue, 25 Jan 2011 08:16:02 -0000

Hi,

<Basavaraj.Patil@nokia.com> writes:

> Inline:
>
> On 1/24/11 3:58 PM, "ext Arnaud Ebalard" <arno@natisbad.org> wrote:
>
>>
>>To me, what the draft describes is a patchwork based on MIPv6, ESP and
>>TLS. Instead of building on top of those protocols (read modularity and
>>interoperability), it reuses (hijacks) various blocks of associated
>>standards in a non-modular way. For instance, one has to reimplement ESP
>>in userspace to support the protocol.
>
> We are specifying an encapsulation method in the I-D. To say that one has
> to reimplement ESP in userspace is incorrect.

Then please explain how one is supposed to get the format described in
section 6.4 which is *explicitly* borrowed from RFC 4303 w/o
reimplementing it in userspace?

Or are you pushing SP and SA in order to reuse what is already
implemented in the IPsec stack?

BTW, is the packages/sources of your implementation still available
somewhere? I expected the patches to be pushed upstream at some point.

Cheers,

a+

v2.23.0 | Report a Bug | By Email