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

arno@natisbad.org (Arnaud Ebalard) Tue, 28 July 2009 09:17 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 BAC503A6E14 for <mext@core3.amsl.com>; Tue, 28 Jul 2009 02:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level:
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 Wp3DnhyBIcRY for <mext@core3.amsl.com>; Tue, 28 Jul 2009 02:17:08 -0700 (PDT)
Received: from copper.chdir.org (copper.chdir.org [88.191.97.87]) by core3.amsl.com (Postfix) with ESMTP id 80FDD3A685A for <mext@ietf.org>; Tue, 28 Jul 2009 02:17:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=natisbad.org; s=mail; h=From:To:Cc:Subject:References:Date: In-Reply-To:Message-ID:MIME-Version:Content-Type; bh=Oa2J725XKOT hPlWxfMMR1f6sq4B9wNJVEyPwwgyGcP8=; b=FrJ0BvOcHMo1+U1e798uJnut4nG eUhEOw1xUK90LvtivoaPClVABaYZpW88cuxUiJYAPDnNGff9fFuDyAgZEgCSq7Di VAsqKDqmap6nOpCiraz9RDbztHCN7zmfKPFUIir8RgOG0XPP+wdG5TkR/s2YqNX0 tSNW60Kg9bkQtv7s=
Received: from [2001:7a8:78df:2:20d:93ff:fe55:8f79] (helo=small.ssi.corp) by copper.chdir.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <arno@natisbad.org>) id 1MVinw-0002Qi-TF; Tue, 28 Jul 2009 11:17:05 +0200
From: arno@natisbad.org
To: Basavaraj.Patil@nokia.com
References: <C68F84FA.2B9FF%basavaraj.patil@nokia.com> <87tz0xkjps.fsf@small.ssi.corp> <FAAB54171A6C764E969E6B4CB3C2ADD20A48B61378@NOK-EUMSG-03.mgdnok.nokia.com>
X-PGP-Key-URL: http://natisbad.org/arno@natisbad.org.asc
X-Fingerprint: 47EB 85FE B99A AB85 FD09 46F3 0255 957C 047A 5026
X-Hashcash: 1:20:090728:mext@ietf.org::8AP0mu7fFEye7jQP:00002Dhx
X-Hashcash: 1:20:090728:basavaraj.patil@nokia.com::xyh4NDnSjN0xVguH:0000000000000000000000000000000000005Pz+
Date: Tue, 28 Jul 2009 11:17:41 +0200
In-Reply-To: <FAAB54171A6C764E969E6B4CB3C2ADD20A48B61378@NOK-EUMSG-03.mgdnok.nokia.com> (Basavaraj Patil's message of "Tue, 28 Jul 2009 10:31:37 +0200")
Message-ID: <87k51t6ua2.fsf@small.ssi.corp>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/23.0.92 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: mext@ietf.org
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: Tue, 28 Jul 2009 09:17:09 -0000

Hi,

<Basavaraj.Patil@nokia.com> writes:

> I will respond to your other comments as soon as I get some time..

ok.

> Raj> MIP6 by itself is useless today. Maybe 10 years from now when we
> hopefully have some deployment of IPv6 networks and is available
> natively on links, it would be an option. 

Well, you should come to France ;-) At work, I have IPv6 (Nerim as a
provider). At Home, I have IPv6 (Free as a provider, which has more
than 5 millions clients who can activate IPv6 at home via a simple
clic (/64)).

> The only practical solution at this time is DSMIP6 because it deals
> with the reality of the fact that MNs will be mostly attached via IPv4
> and NATed networks.

In order to be more useful than MIPv6 (using Teredo when in IPv4
networks) or a direct use of the available private IPv4 address in a
common network, I think one needs a public IPv4 address as HoA. IMHO,
this is a non starter in term of deployment.

For me, MIPv6 provides address stability and e2e.

>> Thank you. I think you will realize the complexities of the
>> implementation when you go through an exercise of doing so.
>
> I won't. I just don't support DSMIPv6. Reread my email address more
> carefully ;-)
>
> Raj> Right... I noticed that already. I dont understand your reasons
> for not supporting DSMIP6.

 - Complexity
 - No availability of the protocol as an open source implementation
 - No public IPv4 address to use for a deployment (or expensive)
 - MIPv6 + Teredo works fine with me

> Is it only because of the fact that DSMIP6 has to deal with NATs ;) ?
> As I said for all practical purposes, implementing only MIP6 by itself
> is purely an academic exercise.

It may depend where you live. 

a+