Re: [nemo] NEMO RO problem draft submit
Park KiYong <kypark@cclab.konkuk.ac.kr> Mon, 18 October 2004 19:42 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17001 for <nemo-archive@lists.ietf.org>; Mon, 18 Oct 2004 15:42:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJd2N-00066G-Ii; Mon, 18 Oct 2004 15:19:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJcXc-0007ye-GR for nemo@megatron.ietf.org; Mon, 18 Oct 2004 14:47:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11781 for <nemo@ietf.org>; Mon, 18 Oct 2004 14:47:24 -0400 (EDT)
Received: from [203.252.134.6] (helo=cclab.konkuk.ac.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJcjI-0006um-7D for nemo@ietf.org; Mon, 18 Oct 2004 14:59:53 -0400
Received: from cclab.konkuk.ac.kr (cclab.konkuk.ac.kr [127.0.0.1]) by cclab.konkuk.ac.kr (8.12.8/8.12.8) with ESMTP id i9IIkRiK004243; Tue, 19 Oct 2004 03:46:27 +0900
Received: (from apache@localhost) by cclab.konkuk.ac.kr (8.12.8/8.12.8/Submit) id i9IIkRcl004241; Tue, 19 Oct 2004 03:46:27 +0900
From: Park KiYong <kypark@cclab.konkuk.ac.kr>
X-Authentication-Warning: cclab.konkuk.ac.kr: apache set sender to kypark@cclab.konkuk.ac.kr using -f
Received: from 220.72.200.15 ([220.72.200.15]) by cclab.konkuk.ac.kr (IMP) with HTTP for <kypark@cclab.konkuk.ac.kr>; Tue, 19 Oct 2004 03:46:27 +0900
Message-ID: <1098125187.41740f8394f40@cclab.konkuk.ac.kr>
Date: Tue, 19 Oct 2004 03:46:27 +0900
To: Alexandru.Petrescu@motorola.com
Subject: Re: [nemo] NEMO RO problem draft submit
References: <200410180717.i9I7H1pY001536@phaenicia.ucdavis.edu> <001e01c4b50e$f230cab0$a486fccb@nbclearsky> <4173E4C2.2090609@motorola.com> <1098122955.417406cb46cde@cclab.konkuk.ac.kr>
In-Reply-To: <1098122955.417406cb46cde@cclab.konkuk.ac.kr>
MIME-Version: 1.0
Content-Type: text/plain; charset="EUC-KR"
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.1
X-Originating-IP: 220.72.200.15
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 8bit
Cc: nemo@ietf.org
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
Content-Transfer-Encoding: 8bit
Dear Alex. Please, ignore my opinion. I didn't think about the case that the MR moves from old Foreign Network to new Foreign Network. I'll think over the solution. Best regard. Kiyong Park. kypark@cclab.konkuk.ac.kr wrote: > Dear Alex, > > I have different opinion > > If the case is MN behind MR, it is right as you said. > > If the case is LFN behind MR, it can be solved by existing IPv6 techniques > > the case of LFN behind MR must be routed through HA. > > I think that the MR keeps home network prefixes it received from Home > Network's Router. > > And CN to LFN will be routed through CN-HA-LFN, because the MR did > registration > request with its home network prefixes to its HA. > > Although the network prefixes was changed and LFN's address was changed in > new > network, the communication will be kept by 'Address renumbering mechanism in > IPv6'. > > Because of that, the communication will not be lost. > > Please, reply me with your opinion. > > Best regard. > Kiyong Park. > > Alexandru Petrescu <Alexandru.Petrescu@motorola.com> wrote: > > > Kiyong Park wrote: > > > I already read a draft about the solution of NEMO RO problem using > > > Prefix Delegation Mechanism in IPv6 You can access it at : > > > > > > http://www-users.cs.umn.edu/~jjeong/publications/ietf-internet-draft/draft-leekj- > nemo-ro-pd-01.txt > > > > > > I think it is abolutely correct solution of NEMO RO problem. Any > > > other opinion, it will be great to me. > > > > Hello Kiyong Park. > > > > IMHO it is debatable whether that PD with Neighbour Discovery solution > > is a correct solution for the NEMO RO problem since we don't know > > exactly what the RO problem is. > > > > If the RO problem is that MN-behind-MR communication to CN goes through > > HA (instead of directly) then yes, that PD solution is solving it. If > > on the other hand the problem is that LFN-behind-MR communication to CN > > goes through HA (instead of directly) then no, that PD solution is not > > solving it, because that draft does not describe how MR performs RO on > > behalf of LFN (LFN does not do Mobile IPv6). In my understanding. > > > > Alex > > > > > > > -------------------------------------------- > This mail sent through CCLab web mail server > -------------------------------------------- This mail sent through CCLab web mail server
- [nemo] NEMO RO problem draft submit Fan Zhao
- Re: [nemo] NEMO RO problem draft submit 박기용_건국대
- Re: [nemo] NEMO RO problem draft submit Alexandru Petrescu
- Re: [nemo] NEMO RO problem draft submit Park KiYong
- Re: [nemo] NEMO RO problem draft submit Park KiYong