[Mip6] Concensus on text for [issue95] Mention DHCPv6 based Home Agent discoverymechanism in section

["Hesham Soliman" <Hesham at elevatemobile.com>]

Folks,

This is a straighforward issue that needs a small editorial change. Please
see Kuntal's issue text and my suggestion below:

 > This issue has been discussed on the list. The current text 
 > in section 2.1 needs
 > to cover cases when DHCPv6 can be used to discover Home 
 > Agent information. The
 > email thread on this issue:
 > 
 > http://www1.ietf.org/mail-archive/web/mip6/current/msg05877.html
 > 
 > Proposed text:
 > -------------
 > Current:
 > 
 > "....If a mobile
 >    node is located in an IPv4-only foreign network, it cannot rely on
 >    native IPv6 routing. The preferred solution for 
 > discovering the home
 >    agent's IPv4 address is through the Domain Name System (DNS).
 > "
 > 
 > New:
 > 
 > If a mobile node is located in an IPv4-only foreign network, 
 > it cannot rely on
 >    native IPv6 routing. In this scenario, the solution for 
 > discovering the home
 > agent's IPv4 address is through the Domain Name System (DNS).
 > 
 > Also add the following in this section:
 > 
 > If the MN is attached to an IPv6-only or it is attached to 
 > an IPv6 and IPv4 Dual
 > stack foreign network, it shall use procedures defined in
 > draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt [add 
 > this reference] to
 > discover Home Agent information.


I suggest modifying the text above to:

If a mobile node is located in an IPv4-only foreign network, 
it cannot rely on native IPv6 routing. In this scenario, the solution for 
discovering the home agent's IPv4 address is through the Domain Name System
(DNS). If the MN is attached to an IPv6-only or dual stack network, it may
also use procedures defined in [INTBOOT] to discover Home Agent information.
Note that the use of [INTBOOT] cannot give the mobile node information that
allows it to continue to communicate with the Home Agent if, for example,
the mobile node moved from an IPv6-enabled network to an IPv4-only network.
In such scenario, the mobile node would need to discover the IPv4 address of
its home agent through the DNS. 



[INTBOOT] draft-ietf-mip6-bootstrapping-integrated-dhc-02.txt


I think it's important to make sure that the consequences of the choice are
clear to the implementer, that's why I added the last two sentences.




_______________________________________________
Mip6 mailing list
Mip6 at ietf.org
https://www1.ietf.org/mailman/listinfo/mip6