IETF Logo Mail Archive

Re: [netext] Scope of Prefixes in Flow Mobility

"Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com> Thu, 05 August 2010 13:38 UTC

Return-Path: <JuanCarlos.Zuniga@InterDigital.com>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E4D83A6B1B for <netext@core3.amsl.com>; Thu, 5 Aug 2010 06:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level:
X-Spam-Status: No, score=-2.077 tagged_above=-999 required=5 tests=[AWL=0.522, 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 P66kt3fiDE3y for <netext@core3.amsl.com>; Thu, 5 Aug 2010 06:38:47 -0700 (PDT)
Received: from idcout.InterDigital.com (idcexmail.interdigital.com [12.32.197.135]) by core3.amsl.com (Postfix) with ESMTP id 4348228B23E for <netext@ietf.org>; Thu, 5 Aug 2010 06:38:47 -0700 (PDT)
Received: from SAM.InterDigital.com ([10.30.2.12]) by idcout.InterDigital.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 5 Aug 2010 09:39:17 -0400
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
Date: Thu, 05 Aug 2010 09:39:16 -0400
Message-ID: <D60519DB022FFA48974A25955FFEC08C032BB016@SAM.InterDigital.com>
In-Reply-To: <C87F7BB3.46B04%sgundave@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [netext] Scope of Prefixes in Flow Mobility
Thread-Index: Acs0TPHaLUso1ER5u0iZyc9iouMV1wAVU2Cg
References: <AANLkTik8gg5AOaH8TjjgfHMz9Da=4qcnyp5DFufDSYoM@mail.gmail.com> <C87F7BB3.46B04%sgundave@cisco.com>
From: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>
To: Sri Gundavelli <sgundave@cisco.com>, Tran Minh Trung <trungtm@etri.re.kr>
X-OriginalArrivalTime: 05 Aug 2010 13:39:17.0258 (UTC) FILETIME=[99AA4EA0:01CB34A3]
Cc: netext@ietf.org
Subject: Re: [netext] Scope of Prefixes in Flow Mobility
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Aug 2010 13:38:48 -0000

Sri, Tran Minh,

> -----Original Message-----
> From: netext-bounces@ietf.org [mailto:netext-bounces@ietf.org] On
> Behalf Of Sri Gundavelli
> Sent: Wednesday, August 04, 2010 11:19 PM
> To: Tran Minh Trung
> Cc: netext@ietf.org
> Subject: Re: [netext] Scope of Prefixes in Flow Mobility
> 
> Tran:
> 
> >> However, the LMA may choose to assign the same prefix(es) as well
as
> new
> >> prefix(es) if it so chooses based on the ATT field. This would be
> scenario 3
> >> below.
> >>
> 
> Right. We assume the network provides the handover hints. We do not
> have the
> MN-AR interface at this point. When we were writing the base spec, the
> MN-AR
> interface was factored into the design. Julien was working on this and
> some
> where we lost track of this critical interface.
> 
> http://tools.ietf.org/html/draft-ietf-netlmm-mn-ar-if-03
> 
> We need to revive this at some point. I was hoping
Telemaco/Carlos/Juan
> Carlos will revive this in for different SDO architectures, at least
> that
> was our understanding.

Indeed, the HO or Flow Mobility hints can come from L2 or L2.5 and they
can be sent either to the MAG or even better to the LMA. We have some
text regarding these in
http://tools.ietf.org/html/draft-melia-netext-logical-interface-support-
01, but it still needs to be cleared out.

The next version should provide a better picture of the way the system
should work.

Jc

v2.23.0 | Report a Bug | By Email