Re: [MEXT] New Text for home link detection in RFC3775bis
Suresh Krishnan <suresh.krishnan@ericsson.com> Wed, 02 July 2008 18:13 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CFE43A6CA2; Wed, 2 Jul 2008 11:13:42 -0700 (PDT)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0051C3A6CA2 for <mext@core3.amsl.com>; Wed, 2 Jul 2008 11:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.364
X-Spam-Level:
X-Spam-Status: No, score=-6.364 tagged_above=-999 required=5 tests=[AWL=0.235, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glV7o4EjLGXd for <mext@core3.amsl.com>; Wed, 2 Jul 2008 11:13:40 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 089823A6C84 for <mext@ietf.org>; Wed, 2 Jul 2008 11:13:39 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m62IDmOs007644; Wed, 2 Jul 2008 13:13:48 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Jul 2008 13:14:28 -0500
Received: from [142.133.10.113] ([142.133.10.113]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Jul 2008 13:14:27 -0500
Message-ID: <486BC5C4.8000900@ericsson.com>
Date: Wed, 02 Jul 2008 14:15:32 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: fan zhao <fanzhao828@gmail.com>
References: <486B8EDD.4070807@ericsson.com> <b6d6bbe00807021101y223a8dc3tcba5152e4bdf8a91@mail.gmail.com>
In-Reply-To: <b6d6bbe00807021101y223a8dc3tcba5152e4bdf8a91@mail.gmail.com>
X-OriginalArrivalTime: 02 Jul 2008 18:14:27.0864 (UTC) FILETIME=[7727D980:01C8DC6F]
Cc: mext@ietf.org
Subject: Re: [MEXT] New Text for home link detection in RFC3775bis
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org
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@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@ietf.org >> https://www.ietf.org/mailman/listinfo/mext >> _______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] New Text for home link detection in RFC377… Suresh Krishnan
- Re: [MEXT] New Text for home link detection in RF… fan zhao
- Re: [MEXT] New Text for home link detection in RF… Suresh Krishnan
- Re: [MEXT] New Text for home link detection in RF… mohamed.kassilahlou
- Re: [MEXT] New Text for home link detection in RF… Charles E. Perkins
- Re: [MEXT] New Text for home link detection in RF… Charles E. Perkins
- Re: [MEXT] New Text for home link detection in RF… Suresh Krishnan
- Re: [MEXT] New Text for home link detection in RF… Christian.Kaas-Petersen
- Re: [MEXT] New Text for home link detection in RF… Julien Laganier
- Re: [MEXT] New Text for home link detection in RF… Christian.Kaas-Petersen