[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [netlmm] I-D Action:draft-ietf-netlmm-lma-discovery-01.txt
Hi Vijay,
In my understanding, LMA is a functional element of mobility
management, the mobile node with only simple IP stack can't
recognize the information of LMA and can't transmit it to MAG.
If the mobile node can't send this information to MAG,
MAG can't receive this information from mobile node.
Regards/Xiangsong
----- Original Message -----
From: "Vijay Devarapalli" <vijay at wichorus.com>
To: "jouni korhonen" <jouni.nospam at gmail.com>; "Xiangsong Cui"
<Xiangsong.Cui at huawei.com>
Cc: <netlmm at ietf.org>
Sent: Tuesday, August 25, 2009 1:47 AM
Subject: Re: [netlmm] I-D Action:draft-ietf-netlmm-lma-discovery-01.txt
Hello,
On 8/24/09 1:56 AM, "jouni korhonen" wrote:
Section 3.2,
" This usually means the MN is the
originator of the LMA information and explicitly participates to the
mobility management signaling "
In NETLMM, the principle is that the MN should not be involved in
mobility management, right?
So the solution "Receiving LMA FQDN or IP Address" should be
deleted in the netlmm WG draft.
I would be fine deleting this section. Others?
I disagree. The section explicitly says the MAG receives the LMA FQDN or IP
address from the MN in the lower layers. This is not the same as the MN
doing mobility management.
Vijay