Re: [MEXT] Review of I-D draft-korhonen-mext-mip6-altsec-06

arno@natisbad.org (Arnaud Ebalard) Thu, 20 January 2011 09:42 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 24D803A70E7 for <mext@core3.amsl.com>; Thu, 20 Jan 2011 01:42:25 -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 qv7hHg177zAS for <mext@core3.amsl.com>; Thu, 20 Jan 2011 01:42:24 -0800 (PST)
Received: from copper.chdir.org (copper.chdir.org [88.191.97.87]) by core3.amsl.com (Postfix) with ESMTP id 196593A6EAA for <mext@ietf.org>; Thu, 20 Jan 2011 01:42:23 -0800 (PST)
Received: from enough (unknown [IPv6:2001:7a8:1161:20:baac:6fff:fe41:5166]) by copper.chdir.org (Postfix) with ESMTPSA id D2A05450053; Thu, 20 Jan 2011 10:40:03 +0100 (CET)
From: arno@natisbad.org
To: "Jan Zorz @ go6.si" <jan@go6.si>
References: <4D37F38A.4080602@go6.si> <B96E2661-6C08-46A1-9C3D-915D604DDF0B@gmail.com> <4D380226.3020108@go6.si>
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:110120:mext@ietf.org::2iBb/C7AN5xQwZCQ:00000E1J
X-Hashcash: 1:20:110120:jan@go6.si::k9wiBjsr3FopxTwY:00000000dyj
X-Hashcash: 1:20:110120:jouni.nospam@gmail.com::mQE0oXiFd4IjUizy:0000000000000000000000000000000000000001CsI
Date: Thu, 20 Jan 2011 10:35:08 +0100
In-Reply-To: <4D380226.3020108@go6.si> (Jan Zorz's message of "Thu, 20 Jan 2011 10:36:38 +0100")
Message-ID: <87lj2f3okz.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: jouni korhonen <jouni.nospam@gmail.com>, mext@ietf.org
Subject: Re: [MEXT] Review of I-D draft-korhonen-mext-mip6-altsec-06
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: Thu, 20 Jan 2011 09:42:25 -0000

"Jan Zorz @ go6.si" <jan@go6.si> writes:

> On 1/20/11 10:31 AM, jouni korhonen wrote:
>>> - Route optimization is an important feature of Mobile IPv6. Hence
>>> this alternate security solution should explain how the route
>>> optimization signaling messages are secured.
>>
>> Currently the I-D scopes route optimization out. That is stated at
>> the very end of the document though. We have been thinking to add
>> route optimization support though.
>
> Jouni, hi.
>
> I think this is essential and *must* be in there. Of what use is all
> mobility stuff if there is no route optimization?
>
> I understand that mobile operators are a bit nervous about that, but
> this shouldn't be a reason not describing/defining route optimization
> in I-D and do it in implementation.

+1