[Mip6] [issue95] Mention DHCPv6 based Home Agent discovery mechanism in section

[Kuntal Chowdhury <tracker-mip6 at mip4.org>]

New submission from Kuntal Chowdhury <kchowdhury at starentnetworks.com>:

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.

----------
category: Technical
draft: draft-ietf-mip6-nemo-v4traversal
messages: 346
nosy: kuntal
priority: Must fix
status: Text proposed
title: Mention DHCPv6 based Home Agent discovery mechanism in section

_________________________________________________
Mip6 issue tracker <tracker-mip6 at mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue95>
_________________________________________________

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