RE: [Mip4] Updated draft for Mobile IPv4 NAI-based Home AddressAssignment...

["Chowdhury, Kuntal" <kchowdhury at starentnetworks.com>]

"
If the home address field is 0.0.0.0 and the request has a NAI 
    extension as well the Dynamic-HoA extension, indicating that the 
    mobile node is capable of dynamic home address assignment, then the 
    home agent tries to assign a new address for the mobile node and 
    return a reply with the home address field containing the assigned 
    address. If the home agent is unable to assign an address, it 
    rejects the request with the code ADDR_ALLOC_FAILED. 
"

HoA=0.0.0.0 in the RRQ means the MN is dynamic HoA capable. So, why any
other extension would be needed for the HA to figure it out? 
    
"
    If the home address field is non-zero and the request has a NAI 
    extension as well as the Dynamic-HoA extension, indicating that the 
    mobile node is capable of dynamic home address assignment, the home 
    agent tries to assign the requested address specified in the home 
    address field and return the same address in the reply. If the home 
    agent is unable to assign the requested address, the home agent 
    tries to assign an alternative address and return the alternative 
    address in the reply. If the home agent is unable to assign an 
    alternative address, it rejects the request with the code 
    ADDR_ALLOC_FAILED.  

"

It seems you are proposing to piggyback MN's capability hint with
Dynamic-HoA extension. But, the I-D is about using NAI extension to
assist HA to process the RRQ. Hence, I am confused about the role of NAI
here. If the NAI is known, the HA can contact the AAA to and download
user/MN specific info which may very well include MN's capability (i.e.
whether the MN can handle dynamically assigned HoA). That is more
in-line with the goal of the I-D, I think.

-Kuntal
 


> -----Original Message-----
> From: Naveen Paulkandasamy [mailto:naveenpk at cisco.com]
> Sent: Wednesday, March 08, 2006 4:14 PM
> To: mip4 at ietf.org
> Cc: Kent Leung
> Subject: [Mip4] Updated draft for Mobile IPv4 NAI-based Home
> AddressAssignment...
> 
> Hi All,
> 
> we have submitted the updated draft for Mobile IPv4 NAI-based Home
> Address Assignment
> based on the comments received for the last version... please let us
> know your comments...
> 
> http://www.ietf.org/internet-drafts/draft-paulkandasamy-mobileip-nai-
> based-home-addres-01.txt
> 
> Abstract
> 
>     With the introduction of NAIs for identifying Mobile Nodes, RFC
>     2794 also enabled the Home Agents to be able to assign IP
addresses
>     to Mobile Nodes during their initial registration. Though the
>     concept of NAI-based home address assignment is referenced in both
>     RFC 2794 and RFC 3344, a comprehensive procedure for achieving
such
>     a NAI-based home address assignment has not been outlined. More
>     particularly, the Home Agent and Mobile Node behaviors including
>     the error recovery mechanisms for various scenarios related to
NAI-
>     based home address assignment have not yet been specified. This
>     document specifies a procedure that the Mobile IP entities should
>     follow in order to facilitate NAI-based home address assignment
>     under various circumstances.
> 
> thanks,
> naveen.
> 
> --
> Mip4 mailing list: Mip4 at ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/


--
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/