Subject: RE: [Mip6] comments to boostrapping (split)

From: Gerardo Giaretta <[email-masked]>
Date: Thu, 01 Dec 2005 16:37:53 +0100

Hi Ryuji, 

> 
> Hello Authors
> 
> Thanks for this documentation and sorry for my delay comments. 
> Some comments maybe already pointed out.
> 
> Editorial
> - MIP6 and Mobile IPv6 are mixed in the document.
> - Mobile Node, Host, MN are also mixed.
>   (This split scenario is applied to MR as well, using mobile host
>   should be avoided. Mobile Node is safer)
> - Fig3, 4 HA must send BA instead of BU.
>

Fixed.

Thanks,
--Gerardo
 
> 
> Overall 
> 
> - The draft mentions localized HA for route optimization and load
>   balancing etc.  The provided texts are a bit unclear. what is the
>   relationship between home prefix and home agents? When MN gets a
>   localized HA, will it associate different home network served by
>   each localized HA?
> 
> - The section 5.3.2 for autoconfigured home address assignment looks
>   weak.  Although the document recommends some operations, but what is
>   the statement of DT? There are several limitation compared to IKE
>   HoA assignment in terms of pre-configured homeprefix/length, assumed
>   64 length. Shouldn't MIP6 use autoconfigured address?
> 
> - When HA assigns static HoA to MN (from HA's address pool), can HA
>   skip proxy DAD? It looks redundant. 
> 
> - When the static address configuration through IKE, is it possible MN
>   requests the previous used HoA to HA? (sorry I did not 
> check IKE doc)
> 
> - For DNS refreshment, the document proposes a new timer for DNS
>   address expiration. Why not HA delete the HoA from DNS when BC for
>   the target MN is expired?
> 
> - For DNS refreshment, HA has to wait for sending BA till DNS update
>   is completed. It depends on how long it takes for DNS update,
>   but MN cannot start communication before the BA. I am not sure using
>   BU and BA for DNS update is right way. Defining other message is
>   possible solution.
> 
> - No alignment requirement for DNS update mobility option? 
> - What the MN's operation when DNS update is fail?
>   (i.e. return code 128-130).
> 
> - The document makes clear how to bootstrap when MN does not have any
>   information. However, MN needs to do all the steps every time it
>   boots up?  what is the trigger for the bootstrapping operation? 
>   For example, my PDA often turn off the power (or WLAN goes to the
>   dormant mode). When the node is up or WLAN is up, how does MN
>   recover the MIP operation? Is this up to implementations?  Is it
>   possible to cache bootstrapping information such as Home
>   prefix/length, HA, etc?
>   
> - This document relies on IKEv2. It might be helpful if it gives
>   information or pointer for the case of IKEv1.
> 
> regards,
> ryuji
> 
> _______________________________________________
> Mip6 mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/mip6
> 

Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to 
[email-masked]. Thank you
====================================================================

_______________________________________________
Mip6 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mip6