 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
Hi all,
I hope that the following can hepl:
If the MN has no configuration then A otherwise B.
A: Bootstrap
o The MN has neither IP address, nor the HA IP address, nor home IP prefix,
o The MN connects to a network, obtains a link IP prefix and acquires or forms an IP address (MN@)
o The MN discovers the HA IP address and its home IP prefixes
o The MN compares the prefix of its IP address (MN@) with the home IP prefixes
- If those prefixes match then the MN is in its home network, HoA=MN@, and the HA is the HA for this HoA. The MN initiates IP sessions with classical routing.
- If not then the MN is in a foreign network, CoA=MN@, the HA is a HA for the MN. The MN will form a HoA from home prefixes or will request a HoA from the HA and will exchange a BU/BA with the HA. The MN initiates IP sessions using MIP.
B. Handover
o The MN has a HoA, the HA IP address and its home IP prefixes
o The MN connects to the network and obtains a link IP prefix
o The MN compares the link IP prefix with the HoA IP prefix
- If those prefixes match then the MN is in its home network
+ If the MN has no CoA: It means that the MN is always on its home network. It has made no IP handover therefore it does not need to send a BU. The MN continues its IP sessions with classical routing.
+ If the MN already has a CoA: It means that the MN returns at its home network then it has to sends a BU to deregister. The MN continues its IP sessions with classical routing.
- If the prefixes do not match then the MN is in a foreign network
+ if the MN has no CoA: It means that the MN comes from its home network then it forms (or acquires) a CoA with the link prefix on which it has just connected and sends a BU to its HA. The MN continues its IP sessions using MIP.
+ If the MN already has a CoA:
* If the link prefixes and the CoA prefix match: It means that the MN is always on the same foreign network. It has made no IP handover therefore it does not need to send a BU. The MN continues its IP sessions using MIP.
* If the link prefixes and the CoA prefix do not match: it means that the MN has made IP handover towards another foreign network therefore it has to form (or acquire) a CoA with the link prefix on which it has just connected and to send a BU to its HA to update its registration. The MN continues its IP sessions using MIP.
o Note that when the mobile node connects on a new visited network it may need to discover the HA of this network if available. The mobile node may have to use this HA for next IP sessions.
Sincerly,
Kassi
-----Message d'origine-----
De : mext-bounces at ietf.org [mailto:mext-bounces at ietf.org] De la part de Suresh Krishnan
Envoyé : mercredi 2 juillet 2008 20:16
À : fan zhao
Cc : mext at ietf.org
Objet : Re: [MEXT] New Text for home link detection in RFC3775bis
Hi Fan,
Sounds like a good idea.
Cheers
Suresh
fan zhao wrote:
> Hi Suresh,
>
> I have a quick comment:
> the Home Link Detection is not only performed during handover, but
> also during initial attach. The new text is proposed into section
> 11.5.4. "Returning Home", which seems to me that the new text only
> applies to the handover case.
>
> Therefore, my oponion is to have a new (sub)section called "Home Link
> Detection" somewhere, and refer to this new section in section 11.5.4.
> What do you think?
>
> Sincerely,
> fan
>
> On Wed, Jul 2, 2008 at 7:21 AM, Suresh Krishnan
> <suresh.krishnan at ericsson.com> wrote:
>> The WG had consensus to fold in text from draft-krishnan-mext-hld
>> into RFC3775bis. Here is the proposed text for doing so. Feel free to edit.
>>
>>
>>
>> This change is made in Section 11.5.4
>>
>> OLD TEXT
>> ========
>> A mobile node detects that it has returned to its home link through
>> the movement detection algorithm in use (Section 11.5.1), when the
>> mobile node detects that its home subnet prefix is again on-link.
>>
>> NEW TEXT
>> ========
>> When an MN detects that it has arrived on a new link using the
>> movement detection algorithm in use (Section 11.5.1) it performs the
>> following steps to determine if it is on the home link.
>>
>> o The MN performs the procedure described in Section 11.5.2 and
>> configures an address referred to as the Current MN Address (CMA).
>> It also stores all the on-link prefix(es) received in the RA along
>> with their prefix lengths in a conceptual list called the Current
>> Link Prefix List (CLPL).
>>
>> o If the home prefix has been statically pre-configured on the MN
>> it checks if the home prefix matches one of the prefixes in the
>> CLPL. If it does, the MN concludes that it has returned home.
>>
>> o If the home prefix has not been statically configured the MN uses
>> some form of bootstrapping procedure (e.g. RFC5026) to determine
>> the home prefix. It then checks if the home prefix matches one of
>> the prefixes in the CLPL. If it does, the MN concludes that it has
>> returned home.
>>
>> _______________________________________________
>> 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
_______________________________________________ MEXT mailing list MEXT at ietf.org https://www.ietf.org/mailman/listinfo/mext