RE: [nemo] Request for your comments on a new RO draft

"Na, Jong Keun" <jkna@popeye.snu.ac.kr> Mon, 16 June 2003 07:31 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04459 for <nemo-archive@lists.ietf.org>; Mon, 16 Jun 2003 03:31:14 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G1E0a08876; Sun, 15 Jun 2003 21:14:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5G1Dfm08862 for <nemo@optimus.ietf.org>; Sun, 15 Jun 2003 21:13:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15972 for <nemo@ietf.org>; Sun, 15 Jun 2003 21:13:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RiWs-0006KE-00 for nemo@ietf.org; Sun, 15 Jun 2003 21:11:26 -0400
Received: from dns1.nal.motlabs.com ([195.212.111.242] helo=jessica.nal.motlabs.com) by ietf-mx with esmtp (Exim 4.12) id 19RiWo-0006KA-00 for nemo@ietf.org; Sun, 15 Jun 2003 21:11:24 -0400
Received: from popeye.snu.ac.kr (popeye.snu.ac.kr [147.46.240.214]) by jessica.nal.motlabs.com (8.12.9/8.12.9) with ESMTP id h5G1DVTN012317 for <nemo@nal.motlabs.com>; Mon, 16 Jun 2003 03:13:32 +0200
Received: from jongkn02 (chaesira.snu.ac.kr [147.46.240.219]) by popeye.snu.ac.kr (8.12.2/8.12.2) with ESMTP id h5G1BWgx008924; Mon, 16 Jun 2003 10:11:34 +0900
From: "Na, Jong Keun" <jkna@popeye.snu.ac.kr>
To: 'Jaehoon Jeong' <paul@etri.re.kr>, nemo@nal.motlabs.com
Subject: RE: [nemo] Request for your comments on a new RO draft
Date: Mon, 16 Jun 2003 10:15:23 +0900
Message-ID: <01e201c333a4$c58f1e90$dbf02e93@jongkn02>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E3_01C333F0.3576C690"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-reply-to: <005d01c332ed$b6058980$c470fe81@etri.re.kr>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>

Hi Jaehoon,
 
I have a concern in your draft.
Is it right direction to give the burden of mobility management to each
MNNs, not MRs?
To the best of my knowledge, In NEMO, it's a basic principal for MR to
manage the mobility of mobile network transparently to nodes behind it.
If nodes behind MR get new CoA of the access link via Proxy-ND each time
MR changes the point of attachment, all of nodes have to directly
process each their handover(L3 address changed). How do you think of my
point?
If something missed, please correct me. Thanks.
 
/Jong
 
-----Original Message-----
From: nemo-admin@ietf.org [mailto:nemo-admin@ietf.org] On Behalf Of
Jaehoon Jeong
Sent: Sunday, June 15, 2003 12:25 PM
To: nemo@nal.motlabs.com
Subject: [nemo] Request for your comments on a new RO draft
 
Hello, nemo guys! 
 
I submitted a new draft about the Route Optimization (RO) for mobile
nodes in mobile network. 
 
 Title : ND-Proxy based Route Optimization for Mobile Nodes in Mobile
Network 
 URL for the Draft :
http://www.ietf.org/internet-drafts/draft-jeong-nemo-ro-ndproxy-00.txt 
 
It is based on ND-Proxy for supporting multi-link subnet.
Whenever a mobile router moves into another access network, 
it provides its mobile network nodes with the network prefix of the
access network.
This scheme makes the access network and mobile network become a
multi-link subnet, 
allowing the local or visiting mobile nodes within the mobile network
to perform binding update for route optimization.
 
Though RO is not the current issue in nemo wg, I think, the research for
RO is important in nemo. 
Through on-line discussion about RO, it may be good for us to prepare RO
issue 
that can be discussed in earnest next year. 
So, I'd like to request your comments on my draft. 
Thanks. 
 
Regards, 
Jaehoon