Re: [MEXT] Home Link Detection [Fwd: I-DAction:draft-krishnan-mext-hld-01.txt]
"George Tsirtsis" <tsirtsis@googlemail.com> Thu, 03 April 2008 08:28 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 core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59CCC28C13E; Thu, 3 Apr 2008 01:28:15 -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 B8F933A6A2A for <mext@core3.amsl.com>; Thu, 3 Apr 2008 01:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.636
X-Spam-Level:
X-Spam-Status: No, score=-0.636 tagged_above=-999 required=5 tests=[AWL=0.741, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_37=0.6]
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 e4SpwpjjUHBd for <mext@core3.amsl.com>; Thu, 3 Apr 2008 01:28:12 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id 7081328C13E for <mext@ietf.org>; Thu, 3 Apr 2008 01:28:12 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so3233084wfa.31 for <mext@ietf.org>; Thu, 03 Apr 2008 01:28:15 -0700 (PDT)
Received: by 10.142.131.18 with SMTP id e18mr6825441wfd.39.1207211295270; Thu, 03 Apr 2008 01:28:15 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Thu, 3 Apr 2008 01:28:15 -0700 (PDT)
Message-ID: <d3886a520804030128h13f1f8dbk60b3e6f99a42e200@mail.gmail.com>
Date: Thu, 03 Apr 2008 09:28:15 +0100
From: George Tsirtsis <tsirtsis@googlemail.com>
To: jouni.korhonen@teliasonera.com
In-Reply-To: <59D7431DE2527D4CB0F1EFEDA5683ED302C7C89C@SEHAN021MB.tcad.telia.se>
MIME-Version: 1.0
Content-Disposition: inline
References: <47F10628.1040001@ericsson.com> <200804011151.50135.julien.IETF@laposte.net> <59D7431DE2527D4CB0F1EFEDA5683ED302C7C89C@SEHAN021MB.tcad.telia.se>
Cc: mext@ietf.org, julien.IETF@laposte.net
Subject: Re: [MEXT] Home Link Detection [Fwd: I-DAction:draft-krishnan-mext-hld-01.txt]
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org
Hi Jouni, I think your comments as well as comments from Julien and others correctly suggest that the way address allocation is performed on a link does not matter. So the draft should not assume anything. This essentially means that the first 4 bullets of section 4: " 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 autoconfigures an address from one of the received prefixes that have the autonomous address configuration flag set. This address is referred to as the Current MN Address (CMA) 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)" ...should be replaced with one bullet that says something like "the MN learns the on-link prefixes and configures an address according to mechanisms available on the link-type it is connected to." Suresh can also add an arbitrary number of acronyms to make it sound more importnant :-) Regards George On Wed, Apr 2, 2008 at 11:25 PM, <jouni.korhonen@teliasonera.com> wrote: > Suresh, Julien, > > The MN might also configure the IPv6 address the MIP6 client > sees using e.g. IKEv2 (in a case of a remote VPN access and > assuming MIP6 is run on top of this VPN tunnel, which is > possible). In that case the CMA is learned via IKEv2 signaling, > and the CLPL is updated accordingly based on the configured > IPv6 address and its prefix (e.g. from the IKEv2 INTERNAL_IP6_ADDRESS > payload). > > IMHO, it might be better not to define the MN operation on > how CMA and CLPL get populated. Just assume they exist > somehow. The last 5 bullets in section 4 are fine with > Julien's changes. > > What do you think? > > Cheers, > Jouni > > > > > -----Original Message----- > > From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On > > Behalf Of Julien Laganier > > Sent: 1. huhtikuuta 2008 12:52 > > To: mext@ietf.org > > Subject: Re: [MEXT] Home Link Detection [Fwd: > > I-DAction:draft-krishnan-mext-hld-01.txt] > > > > > > 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@ietf.org > > > Reply-To: internet-drafts@ietf.org > > > To: i-d-announce@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@ietf.org > > > https://www.ietf.org/mailman/listinfo/mext > > > > > > _______________________________________________ > > 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 mailing list MEXT@ietf.org https://www.ietf.org/mailman/listinfo/mext
- [MEXT] Home Link Detection [Fwd: I-D Action:draft… Suresh Krishnan
- Re: [MEXT] Home Link Detection [Fwd: I-DAction:dr… mohamed.kassilahlou
- Re: [MEXT] Home Link Detection [Fwd: I-D Action:d… Behcet Sarikaya
- Re: [MEXT] Home Link Detection [Fwd: I-DAction:dr… Suresh Krishnan
- Re: [MEXT] Home Link Detection [Fwd: I-D Action:d… Suresh Krishnan
- Re: [MEXT] Home Link Detection [Fwd: I-D Action:d… Behcet Sarikaya
- Re: [MEXT] Home Link Detection [Fwd: I-DAction:dr… Benjamin Lim
- Re: [MEXT] Home Link Detection [Fwd: I-DAction:dr… mohamed.kassilahlou
- Re: [MEXT] Home Link Detection [Fwd: I-D Action:d… Julien Laganier
- Re: [MEXT] Home Link Detection [Fwd: I-DAction:dr… jouni.korhonen
- Re: [MEXT] Home Link Detection [Fwd: I-DAction:dr… George Tsirtsis