Subject: Re: [MEXT] Consensus call on Home Link Detection

From: Behcet Sarikaya <[email-masked]>
Date: Thu, 27 Mar 2008 07:50:08 -0700 (PDT)

I would also say yes (without of course ).
Please include work on the home prefix assignment that assures MN is alone. Someone told me that with IKEv2, MN does not receive PIOs first, at least in 3GPP links (a little correction).

Regards,

Behcet

----- Original Message ----
From: Vijay Devarapalli <[email-masked]>
To: Julien Laganier <[email-masked]>
Cc: [email-masked]
Sent: Thursday, March 27, 2008 9:08:08 AM
Subject: Re: [MEXT] Consensus call on Home Link Detection

Yes, of course.

But don't treat this issue in isolation. We also need to address
a few other thinks like configuring the IPv4 home address, setting
up forwarding for mobile network prefixes, conveying flow filters
to the home agent, etc.. when booting up on the home link.

Vijay

Julien Laganier wrote:
> Folks,
> 
> This is a consensus call on whether we should include a deliverable for 
> Home Link Detection in our updated charter. I have reviewed the 
> discussion on Home Link Detection that happened so far and you can find 
> below my interpretation of the WG consensus. Please reply to the list 
> stating whether you agree (YES) or not (NO) with that interpretation of 
> the WG consensus. Please DO NOT engage in additional discussion within 
> this discussion thread.
> 
> Thanks for your support.
> 
> -- julien & marcelo, MEXT chairs
> 
> -----------------------------------------------------------------------
> There's a consensus that an RFC5026-enabled MN detects it is at home by 
> comparing the prefixes in RA's PIOs received via Router Discovery and 
> in IKEv2's MIP6_HOME_PREFIX received via RFC5026 Bootstrapping.
> 
> There's also a consensus that it is useful to document in an 
> INFORMATIONAL document the above since it seems it is not that obvious 
> to anyone by reading RFC5026.
> -----------------------------------------------------------------------
> _______________________________________________
> MEXT mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/mext

_______________________________________________
MEXT mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/mext

_______________________________________________
MEXT mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/mext