Re: [netext] PMIP purists - is PMIP-NEMO impossible? draft-bernardos-netext-pmipv6-nemo-ps

Hesham Soliman <hesham@elevatemobile.com> Sun, 15 July 2012 09:42 UTC

Return-Path: <hesham@elevatemobile.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51CD121F85CE for <netext@ietfa.amsl.com>; Sun, 15 Jul 2012 02:42:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnCPGL+3Nd8c for <netext@ietfa.amsl.com>; Sun, 15 Jul 2012 02:42:48 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id 41AA221F85CC for <netext@ietf.org>; Sun, 15 Jul 2012 02:42:47 -0700 (PDT)
Received: from [60.242.128.199] (helo=[192.168.0.3]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1SqLLy-0008Sg-Mr; Sun, 15 Jul 2012 19:43:03 +1000
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Sun, 15 Jul 2012 19:42:53 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Seil Jeon <seiljeon@av.it.pt>
Message-ID: <CC28CD62.26818%hesham@elevatemobile.com>
Thread-Topic: [netext] PMIP purists - is PMIP-NEMO impossible? draft-bernardos-netext-pmipv6-nemo-ps
In-Reply-To: <000301cd621d$57cbcc80$07636580$@av.it.pt>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-User: hesham@elevatemobile.com
Cc: netext@ietf.org
Subject: Re: [netext] PMIP purists - is PMIP-NEMO impossible? draft-bernardos-netext-pmipv6-nemo-ps
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 15 Jul 2012 09:42:49 -0000

>

>
>[SJ] Actually, there's no standard draft yet for PMIP-NEMO we're
>discussing.
>Protocol designs for MR would be varied depending on the design
>perspective.
>But one example could be as follows. Moving MAG would attach to PMIPv6
>domain and have unique prefix assigned from a LMA. For attaching and
>detaching mobile node, moving MAG should send PBU instead of MN
>individually. However, in the case of mobile network's moving, PBU sent
>by a
>MAG detecting mMAG's attachment to a LMA would be enough. Moving MAG
>doesn't
>need to send anything for network moving event itself. Following extended
>LMA binding cache entry can be an example.
>When the LMA receives PBU sent by the MAG regarding on moving MAG
>attachment
>(MAG1 -> MAG2), it only changes tunnel endpoint of mMAG to MAG 2 and
>doesn't
>need to touch MNs' entries belonging to mMAG.

=> Doesn't sound like something you would deploy on shared links, but I
guess that's a generic statement for PMIP.
Anyway, lets see when a draft is proposed.

Hesham

>
>
>ID		Prefix		AR		M flag
>--------------------------------------------------------------------
>mMAG 1	Pref1::/64	MAG 2	no
>MN 1		Pref2::/64	mMAG 1	yes
>
>
>Actually, the above might be one example among many possible ways .. and
>it's not my idea. FYI, you can see following.
>I just wanted to describe possibility of PMIPv6-NEMO support using moving
>MAG.
>
>http://dx.doi.org/10.1109/MCOM.2009.4939291
>
>
>
>