Re: [netlmm] Consensus call: RFC5107 based DHCP message interceptat MAG

[Vijay Devarapalli <[e-mail]>]

Sri,

Sri Gundavelli wrote:
>>>  3. MAG will certainly synchroized the state from LMA through PMIP
>>>  signaling, only after each handoff. The MAG will not be in path for
>>>  subsequent DHCP events after handoff. This option will enable the MAG
>>>  to register itself to be in path for all messages. If a MN releases
>>>  an address, if the LMA recycles the address and allocates to some
>>>  other node. 
>>
>> This will not happen. If the LMA has a valid binding cache entry for 
>> the mobile node's IPv4 address, it is not going to allocate the IPv4 
>> address to another mobile node.
>>
> 
> We can argue, even if the MN releases the address, the LMA should
> keep a floating BCE, or it can cleanup the state. 

The MAG has not removed the binding yet. So the LMA cannot cleanup the 
state or remove the binding. It has to at least send a binding 
revocation message to the MAG and get a response to the that. It won't 
allocate the IPv4 address to another mobile node until that. It is a 
really bad idea for the LMA to remove the binding that the MAG created 
based on the DHCP release message from the mobile node.

Vijay

> The point is the
> need for the PMIP and DHCP entities aware of all transactions,
> ensuring the address that the MN requests is the same as what it
> obtained PMIP or being aware of MN releasing its address, or about
> extending lifetimes for the MAG to ensure the PMIP tunnel life is
> valid for the DHCP state.