Re: [MEXT] Home Link Detection [Fwd: I-D Action:draft-krishnan-mext-hld-01.txt]

[Julien Laganier <julien.IETF at laposte.net>]

Hi Suresh,

Two comments:

- The draft seems to assume that SLAAC is used by the MN. However that 
is not needed per se, DHCP could be used to configure the MN's address. 
The only requirement is that the MN obtain one or more PIOs, how the 
MN's address is configured is irrelevant. Thus, I think you should 
reword as:

4.  Mobile Node Operation

   When an MN arrives on a new link it performs the following steps to
   determine if it is on the home link.
   o  The MN sends out a Router Solicitation
   o  The MN receives a Router Advertisement in response with one or
      more Prefix Information Options as specified in [RFC4861].
   o  The MN configures one or more addresses, referred to as the
      Current MN Addresses (CMA), via DHCPv6 if the"Managed address
      configuration" (M) flag is set in the Router Solicitation, or via
      SLAAC if one or more of the received prefixes has the "autonomous
      address configuration" (A) flag set. 
   o  The MN stores all the prefix(es) received along with their prefix
      lengths in the RA in a conceptual list called the Current Link
      Prefix List (CLPL)
   o  The MN uses one of the addresses in the CMA to initiate the
      bootstrapping procedure described in [RFC5026].  The MN MUST
      include the MIP6_HOME_PREFIX attribute in the CFG_REQUEST message.
   o  The MN receives the home prefix and the corresponding prefix
      length from the HA contained in the MIP6_HOME_PREFIX attribute in
      the CFG_REPLY message.  The MN stores it in a conceptual variable

- The procedure could also be made generic to work with hiopt. The 
minimal specification could simply say that the "MN MUST obtain a home 
prefix as part of a bootstrapping procedure [RFC5026][hiopt], and 
compare it against prefixes in the list of PIOs"

What do you think?

--julien

On Monday 31 March 2008, Suresh Krishnan wrote:
> Hi Folks,
>    This draft talks about how to detect attachment to a home link
> when the split scenario is used for bootstrapping (RFC5026). Please
> take some time to review it.
>
> Thanks
> Suresh
>
> -------- Original Message --------
> Subject: I-D Action:draft-krishnan-mext-hld-01.txt
> Date: Mon, 31 Mar 2008 08:00:01 -0700 (PDT)
> From: Internet-Drafts at ietf.org
> Reply-To: internet-drafts at ietf.org
> To: i-d-announce at ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> 	Title           : MIPv6 Home Link Detection
> 	Author(s)       : S. Krishnan, G. Tsirtsis
> 	Filename        : draft-krishnan-mext-hld-01.txt
> 	Pages           : 6
> 	Date            : 2008-03-31
>
> The MIPv6 bootstrapping procedure allows the mobile node to
> dynamically discover its home prefix using an IKEv2 exchange.  Since
> the home prefix is not statically configured on the mobile node,
> there is a need to specify a mechanism for the mobile node to detect
> if it is on its home link.  This document specifies one such
> mechanism.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-krishnan-mext-hld-01.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
> _______________________________________________
> MEXT mailing list
> MEXT at ietf.org
> https://www.ietf.org/mailman/listinfo/mext


_______________________________________________
MEXT mailing list
MEXT at ietf.org
https://www.ietf.org/mailman/listinfo/mext