RE: [netlmm] Network-based mobility - NETLMM DT Solution VsAsolutionbased on MIP6

"Narayanan, Vidya" <vidyan@qualcomm.com> Fri, 27 October 2006 21:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdZjM-0002BD-Pz; Fri, 27 Oct 2006 17:59:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdZjL-0002B8-M5 for netlmm@ietf.org; Fri, 27 Oct 2006 17:59:11 -0400
Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdZjK-0004X3-83 for netlmm@ietf.org; Fri, 27 Oct 2006 17:59:11 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9RLx6G0009731 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 27 Oct 2006 14:59:07 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9RLwLZr024686; Fri, 27 Oct 2006 14:59:05 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Oct 2006 14:58:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [netlmm] Network-based mobility - NETLMM DT Solution VsAsolutionbased on MIP6
Date: Fri, 27 Oct 2006 14:58:51 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325132D413A@NAEX13.na.qualcomm.com>
In-Reply-To: <9018559E7B637042AFBA86C7BE62706FC77027@de01exm67.ds.mot.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [netlmm] Network-based mobility - NETLMM DT Solution VsAsolutionbased on MIP6
Thread-Index: Acb529JqEQb+yWXPEdudHQARJNUNiAADWbXgAAPjpAAAAWZDMAAFHD+A
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: Roberts Phil-APR042 <Phil.Roberts@motorola.com>, "Soliman, Hesham" <hsoliman@qualcomm.com>, Basavaraj Patil <basavaraj.patil@nokia.com>, ext James Kempf <kempf@docomolabs-usa.com>, netlmm@ietf.org
X-OriginalArrivalTime: 27 Oct 2006 21:58:49.0003 (UTC) FILETIME=[14FC27B0:01C6FA13]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc:
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org

I don't think the degree of closeness to MIP6 needs to be debated at
this time. That's why I said PMIP-like in my email. 

Vidya

> -----Original Message-----
> From: Roberts Phil-APR042 [mailto:Phil.Roberts@motorola.com] 
> Sent: Friday, October 27, 2006 12:32 PM
> To: Narayanan, Vidya; Soliman, Hesham; Basavaraj Patil; ext 
> James Kempf; netlmm@ietf.org
> Subject: RE: [netlmm] Network-based mobility - NETLMM DT 
> Solution VsAsolutionbased on MIP6 
> 
> 
> I think there are two separate questions.  One is "Why didn't 
> the design team choose PMIP6?" and the other is "Why did the 
> design team produce the protocol it did?"  You're not 
> presuming that the DT should have chosen PMIP6 are you?
> 
> 
> > -----Original Message-----
> > From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> > Sent: Friday, October 27, 2006 1:54 PM
> > To: Soliman, Hesham; Basavaraj Patil; ext James Kempf; 
> Roberts Phil- 
> > APR042; netlmm@ietf.org
> > Subject: RE: [netlmm] Network-based mobility - NETLMM DT Solution 
> > VsAsolutionbased on MIP6
> > 
> > I fully agree with Hesham here. I think the NETLMM DT 
> really needs to 
> > provide an explanation of why a PMIP-like solution was not chosen as
> the
> > network-mobility protocol. The answer that "the DT 
> deliberated it and 
> > decided against it" is unacceptable. Clearly, the folks 
> outside the DT 
> > have no visibility to this. And, having talked to folks from the DT,
> I'm
> > still not clear on the reasons.
> > 
> > I think this is the responsibility of the DT to prove to the rest of
> the
> > community why the solution chosen best satisfies the 
> requirement for 
> > network-based mobility.
> > 
> > Regards,
> > Vidya
> > 
> > > -----Original Message-----
> > > From: Soliman, Hesham
> > > Sent: Friday, October 27, 2006 9:04 AM
> > > To: Basavaraj Patil; ext James Kempf; Phil Roberts; Narayanan, 
> > > Vidya; netlmm@ietf.org
> > > Subject: RE: [netlmm] Network-based mobility - NETLMM DT Solution 
> > > VsAsolutionbased on MIP6
> > >
> > >
> > >  > I don't think that there is much to be gained by doing a
> > > > comparison of the  > NETLMM DT protocol solution vs "pure
> > > PMIP solution". This is  > not a question  > of whether 
> one protocol 
> > > is better suited or superior in  > terms or performance  
> > or simple 
> > > etc. I am not commenting in any way about the use  > of 
> the mobility  
> > > > header to implement the NETLMM protocol here, but rather  > 
> > > presenting another  > view about NETLMM and PMIP6.
> > >  > Given that the IETFs mainstream solution for IPv6 
> mobility  > is 
> > > MIP6 (I hope  > we are not going to get into a debate about this 
> > > statement  > :) ), there is or  > may be a desire by 
> either SDOs or 
> > > operators considering  > deployment of MIP6  > to also have the 
> > > capability to use the same infrastructure (HA and  > 
> associated AAA) 
> > > for hosts that do not have MIP6 capability or for  > 
> transparently 
> > > supporting mobility for
> > > IPv6 hosts (for  > whatever reason such  > transparent 
> mobility is 
> > > needed).
> > >
> > > => I completely agree with Raj. Let's save the excitement, there 
> > > isn't going to be any significant performance differences between 
> > > the the netlmm protocol and the "hypothetical" PMIPv6 protocol. 
> > > Think about it from a simulation point of view, there is not 
> > > difference. The difference comes from the ability to reuse MIPv6 
> > > infrastructure and its extensions, in a seamless manner.
> > >
> > >  >
> > >  > So instead of a prolonged discussion about the 
> (de)merits of  > 
> > > NETLMM and  > PMIP, we should maybe consider that the IETF 
> > > standardize  > both and let the  > industry pick and choose which 
> > > protocol makes sense in a  > certain deployment
> > >
> > > => It would be preferrable to do one protocol. But before we even 
> > > decide on this, why can't the netlmm WG (DT, chairs
> > > ...etc) explain the reasons for not choosing PMIP and we can at 
> > > least use that as a starting point for the discussion of 
> whether we 
> > > should do 1 or 2 protocols. I find it counter intuitive to simply 
> > > ignore PMIP as a viable option. That is, unless I missed some 
> > > explanations that were already documented somewhere.
> > >
> > > Hesham
> > >
> 

_______________________________________________
netlmm mailing list
netlmm@ietf.org
https://www1.ietf.org/mailman/listinfo/netlmm