Re: [netext] PMIP purists - is PMIP-NEMO impossible? draft-bernardos-netext-pmipv6-nemo-ps

["Seil Jeon" <[e-mail]>]

Hi Hesham,

Regards,

Seil

-----Original Message-----
From: Hesham Soliman [mailto:[e-mail]] 
Sent: Saturday, July 14, 2012 3:15 PM
To: Seil Jeon
Cc: [e-mail]
Subject: Re: [netext] PMIP purists - is PMIP-NEMO impossible?
draft-bernardos-netext-pmipv6-nemo-ps

>
>>
>>[SJ] In my knowledge, an MN doesn't need to be changed if the MR acts 
>>as a moving MAG, which has the responsibility of MN detection i.e. 
>>MN's attach and detach, and sending/receiving PBU/PBA instead of the MN.
>>Regarding on this issue, it was described at the Paris meeting I 
>>remember.
>
>=> Moving MAG = MR in RFC 3963 basically. So it's not PMIP anymore it's 
>normal MIPv6.
>
>[SJ] Moving MAG is not a MR defined in RFC 3963. See above how I 
>defined the moving MAG.

=> Apart from calling it a PBU, as opposed to a BU, what is the real
difference between a moving MAG and MR?
Ironically, people called the Prefix Binding Updates PBUs in early
discussions of NEMO.

[SJ] It sounds to me what is difference between HA - MN (MIPv6 client) and
LMA - MAG. PBU is meant to be Proxy Binding Update as defined in RFC 5213.

Are you saying it sends one BU per address, as opposed to one BU for the
entire prefix? If so, why? a prefix BU is much more efficient. That would
just be a less efficient version of MIP-based MRs.

[SJ] Actually, there's no standard draft yet for PMIP-NEMO we're discussing.
Protocol designs for MR would be varied depending on the design perspective.
But one example could be as follows. Moving MAG would attach to PMIPv6
domain and have unique prefix assigned from a LMA. For attaching and
detaching mobile node, moving MAG should send PBU instead of MN
individually. However, in the case of mobile network's moving, PBU sent by a
MAG detecting mMAG's attachment to a LMA would be enough. Moving MAG doesn't
need to send anything for network moving event itself. Following extended
LMA binding cache entry can be an example.
When the LMA receives PBU sent by the MAG regarding on moving MAG attachment
(MAG1 -> MAG2), it only changes tunnel endpoint of mMAG to MAG 2 and doesn't
need to touch MNs' entries belonging to mMAG.


ID		Prefix		AR		M flag
--------------------------------------------------------------------
mMAG 1	Pref1::/64	MAG 2	no
MN 1		Pref2::/64	mMAG 1	yes


Actually, the above might be one example among many possible ways .. and
it's not my idea. FYI, you can see following.
I just wanted to describe possibility of PMIPv6-NEMO support using moving
MAG.

http://dx.doi.org/10.1109/MCOM.2009.4939291