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

<Basavaraj.Patil@nokia.com> Mon, 24 January 2011 22:00 UTC

Return-Path: <Basavaraj.Patil@nokia.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 881623A696F for <mext@core3.amsl.com>; Mon, 24 Jan 2011 14:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.543
X-Spam-Level:
X-Spam-Status: No, score=-103.543 tagged_above=-999 required=5 tests=[AWL=-0.944, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HmpPaPGWVSO4 for <mext@core3.amsl.com>; Mon, 24 Jan 2011 14:00:57 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by core3.amsl.com (Postfix) with ESMTP id 54BF53A69A6 for <mext@ietf.org>; Mon, 24 Jan 2011 14:00:57 -0800 (PST)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-sa01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p0OM3mGr008802; Tue, 25 Jan 2011 00:03:48 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 25 Jan 2011 00:03:36 +0200
Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 24 Jan 2011 23:03:36 +0100
Received: from 008-AM1MPN1-004.mgdnok.nokia.com ([169.254.5.187]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi; Mon, 24 Jan 2011 23:03:35 +0100
From: Basavaraj.Patil@nokia.com
To: arno@natisbad.org, jan@go6.si
Thread-Topic: [MEXT] Call for WG adoption of I-D: draft-korhonen-mext-mip6-altsec
Thread-Index: AQHLvBKLTg4gV2FeYUKwegM9zkfBrQ==
Date: Mon, 24 Jan 2011 22:03:33 +0000
Message-ID: <C963527A.D013%basavaraj.patil@nokia.com>
In-Reply-To: <878vyarmku.fsf@natisbad.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.0.101115
Content-Type: text/plain; charset="us-ascii"
Content-ID: <a0e04f7a-e4b8-4f3b-a673-35d82f358f83>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 24 Jan 2011 22:03:36.0627 (UTC) FILETIME=[8CB49830:01CBBC12]
X-Nokia-AV: Clean
Cc: julien.laganier.ietf@googlemail.com, 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: Mon, 24 Jan 2011 22:00:58 -0000

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.
We are reusing TLS which is widely implemented today. I do not see a
problem with reuse.

>
>Additionally, it does not support RO.

We are adding RO support to the spec. It is not a big deal to support RO
between MIP6 nodes. Securing the RO signaling messages between the MN-HA
uses the same method used for the BU/BAck messages.

-Raj

>
>Cheers,
>
>a+
>
>[1]: http://permalink.gmane.org/gmane.ietf.mip6/10368
>_______________________________________________
>MEXT mailing list
>MEXT@ietf.org
>https://www.ietf.org/mailman/listinfo/mext