Re: [netlmm] FW: a qtn on pmipv6 multi-homing
Sri Gundavelli <sgundave@cisco.com> Mon, 07 June 2010 21:59 UTC
Return-Path: <sgundave@cisco.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 500E23A677E for <netlmm@core3.amsl.com>; Mon, 7 Jun 2010 14:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UGQuNtFuhkva for <netlmm@core3.amsl.com>; Mon, 7 Jun 2010 14:59:17 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 176403A6407 for <netlmm@ietf.org>; Mon, 7 Jun 2010 14:59:17 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAL8IDUyrRN+K/2dsb2JhbACeIHGmCZoxhRcEg0o
X-IronPort-AV: E=Sophos;i="4.53,380,1272844800"; d="scan'208";a="140720229"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 07 Jun 2010 21:59:11 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o57LxBio019015; Mon, 7 Jun 2010 21:59:11 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Jun 2010 14:59:11 -0700
Received: from 10.32.246.211 ([10.32.246.211]) by xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) with Microsoft Exchange Server HTTP-DAV ; Mon, 7 Jun 2010 21:59:10 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 07 Jun 2010 14:59:39 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Sam Jeyaseelan <Sam.Jeyaseelan@jdsu.com>, "netlmm@ietf.org" <netlmm@ietf.org>
Message-ID: <C832B9DB.432EB%sgundave@cisco.com>
Thread-Topic: [netlmm] FW: a qtn on pmipv6 multi-homing
Thread-Index: AQHLBoQld/yHxJoSq06HM8VWqUlrP5J3CVmMgAADEho=
In-Reply-To: <F36C6302717C59478890A7775A4C8CC72542ADB1C1@MILEXCH2.ds.jdsu.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 07 Jun 2010 21:59:11.0470 (UTC) FILETIME=[A93C98E0:01CB068C]
Subject: Re: [netlmm] FW: a qtn on pmipv6 multi-homing
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: Mon, 07 Jun 2010 21:59:18 -0000
> In this paragraph, Does multiple-interface mean multiple > Proxy-care-of-addressess? Would someone throw some light on this? A mobile node with multiple interfaces, lets say LTE and WIFI, attaches to two different access networks one over LTE to MAG-1 and the other over WiFI to MAG-2. In this case, there would be two Proxy Care-of Addresses, two MIP tunnels and two MIP sessions/BCE's. Each of those MAG's will have security relation to the LMA/PGW. Sri On 6/7/10 2:48 PM, "Sam Jeyaseelan" <Sam.Jeyaseelan@jdsu.com> wrote: > forwarding to the correct forum....( i guess).. > > ________________________________________ > From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Sam > Jeyaseelan [Sam.Jeyaseelan@jdsu.com] > Sent: Monday, June 07, 2010 2:58 PM > To: ietf@ietf.org > Subject: a qtn on pmipv6 multi-homing > > As per the section 5.4 from rfc 5213: > ... > ... > When a mobile node connects to a Proxy Mobile IPv6 domain through > multiple interfaces for simultaneous access, the local mobility > anchor MUST allocate a mobility session for each of the attached > interfaces. Each mobility session should be managed under a > separate Binding Cache entry and with its own lifetime. > > In this paragraph, Does multiple-interface mean multiple > Proxy-care-of-addressess? > Would someone throw some light on this? > > thanks in advance. > > -Sam > > 4G R&D engineer > JDSU > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ > netlmm mailing list > netlmm@ietf.org > https://www.ietf.org/mailman/listinfo/netlmm
- [netlmm] FW: a qtn on pmipv6 multi-homing Sam Jeyaseelan
- Re: [netlmm] FW: a qtn on pmipv6 multi-homing Sri Gundavelli
- Re: [netlmm] FW: a qtn on pmipv6 multi-homing Sam Jeyaseelan
- Re: [netlmm] FW: a qtn on pmipv6 multi-homing Sri Gundavelli