Re: [netlmm] Some comments // RE: Fwd: New Version Notification for draft-ietf-netlmm-lma-discovery-05
"Narayanan, Vidya" <vidyan@qualcomm.com> Sun, 26 September 2010 19:49 UTC
Return-Path: <vidyan@qualcomm.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 570C23A6B82 for <netlmm@core3.amsl.com>; Sun, 26 Sep 2010 12:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.11
X-Spam-Level:
X-Spam-Status: No, score=-105.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 HG+BDmbT1B5D for <netlmm@core3.amsl.com>; Sun, 26 Sep 2010 12:49:18 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id BF4B43A6B52 for <netlmm@ietf.org>; Sun, 26 Sep 2010 12:49:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=vidyan@qualcomm.com; q=dns/txt; s=qcdkim; t=1285530596; x=1317066596; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Narayanan,=20Vidya"=20<vidyan@qualcomm.com>|To: =20Vijay=20Devarapalli=20<dvijay@gmail.com>,=20Xiangsong =20Cui=0D=0A=09<Xiangsong.Cui@huawei.com>|CC:=20"netlmm@i etf.org"=20<netlmm@ietf.org>|Date:=20Sun,=2026=20Sep=2020 10=2012:49:54=20-0700|Subject:=20RE:=20[netlmm]=20Some=20 comments=20//=20RE:=20Fwd:=20New=20Version=20Notification =20for=0D=0A=20draft-ietf-netlmm-lma-discovery-05 |Thread-Topic:=20[netlmm]=20Some=20comments=20//=20RE:=20 Fwd:=20New=20Version=20Notification=0D=0A=20for=20draft-i etf-netlmm-lma-discovery-05|Thread-Index:=20ActZ2AHThH/D9 p2dTDO7y6gcsG/7OAD263Ew|Message-ID:=20<BE82361A0E26874DBC 2ED1BA244866B91E9C4D00A6@NALASEXMB08.na.qualcomm.com> |References:=20<20100913093616.B6F433A6954@core3.amsl.com >=0D=0A=09<E6A9CB0C-41C3-48F7-A5A2-3CD1FA51DFD5@gmail.com >=0D=0A=09<003f01cb553d$acd29900$0677cb00$%cui@huawei.com >=0D=0A=09<6EB3A011-D90A-41E0-847B-EE4EC35A37EC@gmail.com >=0D=0A=09<006901cb557f$4e5482c0$eafd8840$%cui@huawei.com >=0D=0A=09<6D56C9EB-84BE-4CF6-8CD1-8C153AF23450@gmail.com >=0D=0A=09<4C979C8A.7030000@gmail.com>=0D=0A=09<005d01cb5 939$9ad13180$d0739480$%cui@huawei.com>=20<4C992A3F.205050 9@gmail.com>|In-Reply-To:=20<4C992A3F.2050509@gmail.com> |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=OgthRNwgwBpE1ElqKZM817jVdnbJrRO8EHreoz81sHg=; b=FxpjaiOr0YSFiN1WUgswgeW7XM4eIrp5j6kArupqJ8vWu7WL72ngjwC4 nSMFaQetUlXcgAFewX4sTS292x5TqQd1oAxhWL6S3VyFkBNLgG+L4UuoJ kCH8gVfnGmgFCanQBOpcBFUKAjkVLmwLh1OQ3QL1AafFwvW1TavEXQ3yu Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,6118"; a="55775733"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 26 Sep 2010 12:49:55 -0700
X-IronPort-AV: E=Sophos;i="4.57,239,1283756400"; d="scan'208";a="9731856"
Received: from nasanexhub04.qualcomm.com (HELO nasanexhub04.na.qualcomm.com) ([129.46.134.222]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-MD5; 26 Sep 2010 12:49:55 -0700
Received: from nalasexhc02.na.qualcomm.com (10.47.129.186) by nasanexhub04.na.qualcomm.com (129.46.134.222) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 26 Sep 2010 12:49:55 -0700
Received: from NALASEXMB08.na.qualcomm.com ([10.47.16.13]) by nalasexhc02.na.qualcomm.com ([10.47.129.186]) with mapi; Sun, 26 Sep 2010 12:49:55 -0700
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: Vijay Devarapalli <dvijay@gmail.com>, Xiangsong Cui <Xiangsong.Cui@huawei.com>
Date: Sun, 26 Sep 2010 12:49:54 -0700
Thread-Topic: [netlmm] Some comments // RE: Fwd: New Version Notification for draft-ietf-netlmm-lma-discovery-05
Thread-Index: ActZ2AHThH/D9p2dTDO7y6gcsG/7OAD263Ew
Message-ID: <BE82361A0E26874DBC2ED1BA244866B91E9C4D00A6@NALASEXMB08.na.qualcomm.com>
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> <005d01cb5939$9ad13180$d0739480$%cui@huawei.com> <4C992A3F.2050509@gmail.com>
In-Reply-To: <4C992A3F.2050509@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "netlmm@ietf.org" <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: Sun, 26 Sep 2010 19:49:21 -0000
It seems to me that a reference to RFC5149 and a description of how it applies is appropriate. Vijay, can this be handled as RFC-Editor notes? I'm wondering if there is any reason we can't move this document along to IESG review in its current state. Vidya > -----Original Message----- > From: netlmm-bounces@ietf.org [mailto:netlmm-bounces@ietf.org] On > Behalf Of Vijay Devarapalli > Sent: Tuesday, September 21, 2010 2:57 PM > To: Xiangsong Cui > Cc: netlmm@ietf.org > Subject: Re: [netlmm] Some comments // RE: Fwd: New Version > Notification for draft-ietf-netlmm-lma-discovery-05 > > On 9/20/10 8:03 PM, Xiangsong Cui wrote: > > 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? > > No. Read through the rest of the Introduction in RFC 5149. It > specifically talks about distinguishing between multiple services that > can be provided to a mobile node and how to identify the service that > the mobile node wants to use when it sends a Binding Update to the home > agent. (in PMIPv6, it would be the PBU from the MAG to the LMA). > > Vijay > > > > > 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 > > > > _______________________________________________ > netlmm mailing list > netlmm@ietf.org > https://www.ietf.org/mailman/listinfo/netlmm
- [netlmm] Fwd: New Version Notification for draft-… jouni korhonen
- [netlmm] Some comments // RE: Fwd: New Version No… Xiangsong Cui
- Re: [netlmm] Some comments // RE: Fwd: New Versio… jouni korhonen
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Xiangsong Cui
- Re: [netlmm] Some comments // RE: Fwd: New Versio… jouni korhonen
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Xiangsong Cui
- Re: [netlmm] Some comments // RE: Fwd: New Versio… jouni korhonen
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Vijay Devarapalli
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Xiangsong Cui
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Vijay Devarapalli
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Narayanan, Vidya
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Jari Arkko
- Re: [netlmm] Some comments // RE: Fwd: New Versio… Narayanan, Vidya