IETF Logo Mail Archive

Re: [netlmm] Consensus call: Adopting draft-korhonen-netlmm-lma-discovery as a WG item

Julien Laganier <julien.laganier.ietf@googlemail.com> Fri, 15 May 2009 15:44 UTC

Return-Path: <julien.laganier.ietf@googlemail.com>
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FF9D3A68AC for <netlmm@core3.amsl.com>; Fri, 15 May 2009 08:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level:
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599]
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 1gKquFXcquMc for <netlmm@core3.amsl.com>; Fri, 15 May 2009 08:44:46 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by core3.amsl.com (Postfix) with ESMTP id B5CC03A6B71 for <netlmm@ietf.org>; Fri, 15 May 2009 08:44:44 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id 13so606517fge.18 for <netlmm@ietf.org>; Fri, 15 May 2009 08:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=WE7v9OGzYeX9dhSundXWbKxOv1imbGK0Mxdqhe30p7U=; b=mTlXIM0EJ4JhPAY9xDSugWzofHYcUAOxHxtV0Zm1EuC/Hap+TySIUNZiLuAUdQmy4c L984mtXbR6u3iEpnl54hc6/+dsZPAUgQdB2vDe+bCfvklyDxPPXy6uhwCXCVklt81Jlf CxtnNvH3mcJQU/GEYPuuOP5Z8vqLY60K+PzOY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=ofFe0DyjobemmoWaCDKe+ve6Xk2sFccJ4etjWceWvW1YJ9vNhWqY2+Q39NeRxOdkPe YcpEEotmirO/jGF+RQX6mzkMRw8N2bD0qEqEDm534hYG/slz3tGdT1xPY39VYbEP9ZVo aoilGa9kjZNaMzFfeEM5hWysg2h7RUI5nAFmM=
Received: by 10.86.70.20 with SMTP id s20mr3851425fga.1.1242402372073; Fri, 15 May 2009 08:46:12 -0700 (PDT)
Received: from klee.local ([212.119.9.178]) by mx.google.com with ESMTPS id l12sm830280fgb.21.2009.05.15.08.46.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 15 May 2009 08:46:11 -0700 (PDT)
From: Julien Laganier <julien.laganier.ietf@googlemail.com>
To: netlmm@ietf.org
Date: Fri, 15 May 2009 17:46:21 +0200
User-Agent: KMail/1.9.10
References: <C6324976.770B%vijay@wichorus.com>
In-Reply-To: <C6324976.770B%vijay@wichorus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200905151746.22402.julien.laganier.IETF@googlemail.com>
Cc: Christian Vogt <christian.vogt@ericsson.com>
Subject: Re: [netlmm] Consensus call: Adopting draft-korhonen-netlmm-lma-discovery as a WG item
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 May 2009 15:44:47 -0000

Hi Vijay,

On Friday 15 May 2009, Vijay Devarapalli wrote:
> Hi Christian,
>
> On 5/14/09 6:46 PM, "Christian Vogt" wrote:
> > - The handover considerations in section 5 currently say: 
> > "Obviously, relying on DNS during handovers is not a working
> > solution if the PMIPv6 domain has more than one LMA."  Here you
> > should add "..., unless the DNS consistently assigns a specific LMA
> > for each given mobile host."
>
> When the DNS server gets a request from the MAG, there is no
> information in the request that indicates that this request is
> associated with a specific mobile node. So how does the DNS
> consistently assign the same LMA for a given mobile node?.

Not sure what Christian had in mind, but it could be possible, when the 
LMA FQDN is constructed from a mobile node identity (such as the IMSI) 
to build the name in a way that assigns different mobile nodes to 
different LMAs.

A strawman with mobile node with IMSI 123456789 and six LMAs in the 
pool: 

1. query: 
	_lma_pool.example.com

2. receive reply:
	lma-nyc.example.com
	lma-lax.example.com
	lma-sfbay.example.com
	lma-west.example.com
	lma-east.example.com
	lma-central.example.com

3. sort the lma list in alphanumeric order:
	lma-central.example.com
	lma-east.example.com
	lma-lax.example.com
	lma-nyc.example.com
	lma-sfbay.example.com
	lma-west.example.com

4. compute IMSI MOD N_LMA:
	IMSI MOD N_LMA = 123456789 MOD 6
                       = 3

5. assign MN with LMA numbered IMSI MOD N_LMA in the ordered list:
	lma-lax.example.com

--julien

v2.23.0 | Report a Bug | By Email