[MEXT] [mext] #13: Home Link Detection [Suresh Krishnan <suresh.krishnan@ericsson.com>]
"mext" <trac@tools.ietf.org> Fri, 11 July 2008 18:00 UTC
Return-Path: <mext-bounces@ietf.org>
X-Original-To: mext-archive@optimus.ietf.org
Delivered-To: ietfarch-mext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 953FB28C26B; Fri, 11 Jul 2008 11:00:48 -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 B1D8728C26B for <mext@core3.amsl.com>; Fri, 11 Jul 2008 11:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 MttG0KCFBvyr for <mext@core3.amsl.com>; Fri, 11 Jul 2008 11:00:46 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [194.146.105.14]) by core3.amsl.com (Postfix) with ESMTP id 4098F28C26A for <mext@ietf.org>; Fri, 11 Jul 2008 11:00:46 -0700 (PDT)
Received: from localhost ([127.0.0.1]:45020 helo=merlot.tools.ietf.org) by merlot.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1KHMvT-0001Y3-2a; Fri, 11 Jul 2008 20:00:59 +0200
MIME-Version: 1.0
From: mext <trac@tools.ietf.org>
X-Trac-Version: 0.10.4
X-Mailer: Trac 0.10.4, by Edgewall Software
To: charliep@computer.org
X-Trac-Project: mext
Date: Fri, 11 Jul 2008 18:00:58 -0000
X-URL: http://tools.ietf.org/wg/mext/
X-Trac-Ticket-URL: http://wiki.tools.ietf.org/wg/mext/trac/ticket/13
Message-ID: <063.44d72bbd38b42b8497376e892521c1fd@tools.ietf.org>
X-Trac-Ticket-ID: 13
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: charliep@computer.org, suresh.krishnan@ericsson.com, mext@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false
Cc: mext@ietf.org
Subject: [MEXT] [mext] #13: Home Link Detection [Suresh Krishnan <suresh.krishnan@ericsson.com>]
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mext@ietf.org
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org
Ticket #13: Home Link Detection [Suresh Krishnan <suresh.krishnan@ericsson.com>] Suresh Krishnan <suresh.krishnan@ericsson.com> [edited by CEP] The WG had consensus to fold in text from draft-krishnan-mext-hld into rfc3775bis. Here is the proposed text for doing so. [This change to be made in a new (sub)section called "Home Link Detection"] 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. {{{ #!html <UL> <LI> 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). </UL> }}} {{{ #!html <UL> <LI> 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. </UL> }}} {{{ #!html <UL> <LI> 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. </UL> }}} --------------------------------------------------------------------- "Charles E. Perkins" <charliep@wichorus.com> I would like to suggest a textual revision and simplification. Most of the revision relies on pointing out that one has to get a home network prefix before using it to compare against the list of prefixes received in the RA. The other revision, which I hope is O.K., is to dispense with creating the new acronyms CMA and CLPL. I am biased against having acronyms that are not used elsewhere in the document. Here is my result: NEW TEXT ======== Section 11.5.X Home Link Detection When an MN detects that it has arrived on a new link using the movement detection algorithm in use (Section 11.5.1x) it performs the following steps to determine if it is on the home link. {{{ #!html <UL> <LI> The MN performs the procedure described in Section 11.5.2x and configures an address. It also keeps track of all the on-link prefix(es) received in the RA along with their prefix lengths. </UL> }}} {{{ #!html <UL> <LI> 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. </UL> }}} {{{ #!html <UL> <LI> Given the availability of the home prefix, the MN checks whether or not the home prefix matches one of the prefixes received in the RA. If it does, the MN concludes that it has returned home. </UL> }}} ================================================ It is also a bit tricky to determine where to locate this new section. The current organization of section 11.5 is as follows: {{{ 11.5. Movement . . . . . . . . . . . . . . . . . . . . . 123 11.5.1. Movement Detection . . . . . . . . . . . . . . 123 11.5.2. Forming New Care-of Addresses . . . . . . . . . 125 11.5.3. Using Multiple Care-of Addresses . . . . . . . 126 11.5.4. Returning Home . . . . . . . . . . . . . . . . 127 }}} After reading through the text, I think the new subsection would fit best after the current 11.5.1, making it a new subsection 11.5.2. ----------------------------------------+----------------------------------- Reporter: charliep@computer.org | Owner: charliep@computer.org Type: defect | Status: new Priority: major | Milestone: Component: draft-ietf-mext-rfc3775bis | Version: Severity: Active WG Document | Keywords: Home Link Detection ----------------------------------------+----------------------------------- -- Ticket URL: <http://wiki.tools.ietf.org/wg/mext/trac/ticket/13> mext <http://tools.ietf.org/wg/mext/> _______________________________________________ MEXT mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext