Re: [netlmm] Some comments // RE: Fwd: New Version Notification for draft-ietf-netlmm-lma-discovery-05

Xiangsong Cui <Xiangsong.Cui@huawei.com> Tue, 21 September 2010 03:03 UTC

Return-Path: <Xiangsong.Cui@huawei.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 C21B63A6861 for <netlmm@core3.amsl.com>; Mon, 20 Sep 2010 20:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.075
X-Spam-Level:
X-Spam-Status: No, score=-0.075 tagged_above=-999 required=5 tests=[AWL=0.420, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 4EVPhzM00Ar0 for <netlmm@core3.amsl.com>; Mon, 20 Sep 2010 20:03:33 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 981CA3A6829 for <netlmm@ietf.org>; Mon, 20 Sep 2010 20:03:33 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L92006NFTUA53@szxga02-in.huawei.com> for netlmm@ietf.org; Tue, 21 Sep 2010 11:03:46 +0800 (CST)
Received: from c00111037 ([10.111.16.128]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9200C0VTUAG0@szxga02-in.huawei.com> for netlmm@ietf.org; Tue, 21 Sep 2010 11:03:46 +0800 (CST)
Date: Tue, 21 Sep 2010 11:03:45 +0800
From: Xiangsong Cui <Xiangsong.Cui@huawei.com>
In-reply-to: <4C979C8A.7030000@gmail.com>
To: 'Vijay Devarapalli' <dvijay@gmail.com>, 'jouni korhonen' <jouni.nospam@gmail.com>
Message-id: <005d01cb5939$9ad13180$d0739480$%cui@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: ActY6uuwcZ6EOQ9/RlKolcsULTMF5AAS4+Lw
References: <20100913093616.B6F433A6954@core3.amsl.com> <E6A9CB0C-41C3-48F7-A5A2-3CD1FA51DFD5@gmail.com> <003f01cb553d$acd29900$0677cb00$%cui@huawei.com> <6EB3A011-D90A-41E0-847B-EE4EC35A37EC@gmail.com> <006901cb557f$4e5482c0$eafd8840$%cui@huawei.com> <6D56C9EB-84BE-4CF6-8CD1-8C153AF23450@gmail.com> <4C979C8A.7030000@gmail.com>
Cc: netlmm@ietf.org
Subject: Re: [netlmm] Some comments // RE: Fwd: New Version Notification for draft-ietf-netlmm-lma-discovery-05
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: Tue, 21 Sep 2010 03:03:34 -0000

I don't think so.
As I said in my earlier mail, I think there is some circulation on RFC5149
reference.

RFC5149 reads,
   This document describes a Service Selection Mobility Option for
   Mobile IPv6 that is intended to *assist home agents* to make specific
   service selections for the mobility service subscription **during the
   binding registration procedure.**

I think this is clear enough, RFC5149 is "assist HA ... during registration
procedure", right?
While in this draft, we are talking about "assist LMA-discoverer to select a
LMA, before registration procedure", right?

How can we mix them together?

Desired service may be used for purpose A, and may be used for purpose B,
but this not means A and B *MUST* be free to be cross-referenced, imho.
So I agree LMA-discovery refer on desired service, and I disagree
LMA-discovery refer on RFC5149.
And I am open for any clarification on desired service, if it is not clear.

Xiangsong


> -----Original Message-----
> From: Vijay Devarapalli [mailto:dvijay@gmail.com]
> Sent: Tuesday, September 21, 2010 1:40 AM
> To: jouni korhonen
> Cc: Xiangsong Cui; netlmm@ietf.org
> Subject: Re: [netlmm] Some comments // RE: Fwd: New Version Notification
for
> draft-ietf-netlmm-lma-discovery-05
> 
> On 9/16/10 2:44 AM, jouni korhonen wrote:
> > Hi,
> >
> > Inline..
> >
> > On Sep 16, 2010, at 12:12 PM, Xiangsong Cui wrote:
> >
> > [snip]
> >
> >>>
> >>> Anyway, I have no problem of removing RFC5149 reference if that is
> >> offending.
> >>> It only appeared in -04 version of this draft.
> >>
> >> I prefer "selecting a LMA based on desired services." Thanks!
> >
> > Ok. Good.
> 
> No, this is too vague. It is hard for someone not familiar with 3GPP to
> figure out what it means to select LMA based on the services desired.
> Service specific mobility anchor points are very 3GPP specific. So I
> think we should have the reference to RFC 5149. That RFC clearly
> explains what a "service" means in addition to defining a new mobility
> option. I think you should put back this reference.
> 
> Vijay