Re: [nemo] Some questions about the basic of NEMO ...

Ryuji Wakikawa <ryuji@sfc.wide.ad.jp> Tue, 19 July 2005 02:05 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuhTm-0003JQ-Cz; Mon, 18 Jul 2005 22:05:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuhTk-0003JD-QY for nemo@megatron.ietf.org; Mon, 18 Jul 2005 22:05:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09343 for <nemo@ietf.org>; Mon, 18 Jul 2005 22:05:02 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuhxH-0006Do-O6 for nemo@ietf.org; Mon, 18 Jul 2005 22:35:36 -0400
Received: from [192.168.0.4] (p4080-ipbf903marunouchi.tokyo.ocn.ne.jp [58.88.27.80]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 2D4E34C1F8; Tue, 19 Jul 2005 11:03:23 +0900 (JST)
In-Reply-To: <20050719015652.2355.qmail@web32710.mail.mud.yahoo.com>
References: <20050719015652.2355.qmail@web32710.mail.mud.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <6ACB3C27-1874-42F5-A926-83433793368E@sfc.wide.ad.jp>
Content-Transfer-Encoding: 7bit
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Subject: Re: [nemo] Some questions about the basic of NEMO ...
Date: Tue, 19 Jul 2005 11:04:30 +0900
To: Patrick Lam <allmailinglist@yahoo.com>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Content-Transfer-Encoding: 7bit
Cc: IETF NEMO WG <nemo@ietf.org>, Vijay Devarapalli <vijayd@iprg.nokia.com>
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Sender: nemo-bounces@ietf.org
Errors-To: nemo-bounces@ietf.org

Hello Patrick

Try to read  draft-ietf-nemo-home-network-models-03.
Similar scenario is described in Section8.

ryuji


On 2005/07/19, at 10:56, Patrick Lam wrote:

> Hi Vijay,
>
> Thanks for your reply.  You are right that IPv6
> doesn't have NAT.  I was thinking NAT64 when I was
> typing, but I guess that won't be applicable to NEMO
> scenarios ... or should it be?
>
> Regarding MNN getting a CoA, I am just wondering the
> following scenario.
>
> Say, a MNN is associated with MR1 at the home network
> and moved together with MR1, then I guess it won't
> need a CoA in this case (because MR1 is handling all
> the handoff duties), right?  But then when it is
> handed off to a new MR2, it will need to get a CoA.
>
> As a result, as long as the MNN is associated with an
> appropriate MR (i.e., MR1), it will "feel" like at
> home, no matter where MR1 is.  On the other hand,
> whenever the MNN is not associated with the right MR
> (say, moved to MR2), it will "feel" like at a foreign
> network even MR2 is actually inside the home network
> of the MNN.
>
> It doesn't seem to be a correct interpretation.  Where
> did I misunderstand?
>
> Thanks again.
>
> Regards,
>
> Patrick
>
> --- Vijay Devarapalli <vijayd@iprg.nokia.com> wrote:
>
>
>> Patrick Lam wrote:
>>
>>> Hi,
>>>
>>> As I thought about NEMO more, more questions I
>>>
>> have
>>
>>> ... :)
>>>
>>> 1.  For the MNNs inside a MR, can they be NAT'ed?
>>>
>> Or
>>
>>> do they have to be addressed according to the MR's
>>> prefix?
>>>
>>
>> first of all, there is no NAT in IPv6.
>>
>>
>>> 2.  Under the definition of NEMO, can a MNN be
>>>
>> handed
>>
>>> off from one MR to another?  If so, the MNN will
>>>
>> have
>>
>>> to have a globally unique IPv6 address (i.e.,
>>>
>> can't
>>
>>> use NAT), right?
>>>
>>
>> the MNN will have a globally unique IPv6 address
>> from
>> the mobile network prefix advertised by the mobile
>> router. it is possible that the mobile network
>> prefix
>> is of the type described in
>> draft-ietf-ipv6-unique-local-addr-09.txt. in this
>> case,
>> the MNN's IPv6 address will not be globally
>> routable,
>> only inside the home network. this is not explicity
>> addressed in RFC 3963. as long the MNN stays put in
>> the mobile network, it will work.
>>
>>
>>> 3.  If the MNNs can be handed off from one MR to
>>> another, it seems like they will have to be
>>>
>> addressed
>>
>>> by a CoA as well, right?
>>>
>>
>> yes.
>>
>> Vijay
>>
>>
>
>
>
>
> ____________________________________________________
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
>
>
>