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

Hesham Soliman <hesham@elevatemobile.com> Sat, 14 July 2012 14:14 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 2FCA021F86A8 for <netext@ietfa.amsl.com>; Sat, 14 Jul 2012 07:14:29 -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 s2vw+fV3Rukn for <netext@ietfa.amsl.com>; Sat, 14 Jul 2012 07:14:27 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD2E21F8698 for <netext@ietf.org>; Sat, 14 Jul 2012 07:14:23 -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 1Sq37Z-0006Ay-Mv; Sun, 15 Jul 2012 00:14:58 +1000
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Sun, 15 Jul 2012 00:14:52 +1000
From: Hesham Soliman <hesham@elevatemobile.com>
To: Seil Jeon <seiljeon@av.it.pt>
Message-ID: <CC27BB2E.267EF%hesham@elevatemobile.com>
Thread-Topic: [netext] PMIP purists - is PMIP-NEMO impossible? draft-bernardos-netext-pmipv6-nemo-ps
In-Reply-To: <000601cd61ca$03068760$09139620$@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: Sat, 14 Jul 2012 14:14:29 -0000

>
>>
>>[SJ] In my knowledge, an MN doesn't need to be changed if the MR acts
>>as a moving MAG, which has the responsibility of MN detection i.e. MN's
>>attach and detach, and sending/receiving PBU/PBA instead of the MN.
>>Regarding on this issue, it was described at the Paris meeting I
>>remember.
>
>=> Moving MAG = MR in RFC 3963 basically. So it's not PMIP anymore it's
>normal MIPv6. 
>
>[SJ] Moving MAG is not a MR defined in RFC 3963. See above how I defined
>the
>moving MAG.

=> Apart from calling it a PBU, as opposed to a BU, what is the real
difference between a moving MAG and MR?
Ironically, people called the Prefix Binding Updates PBUs in early
discussions of NEMO.

Are you saying it sends one BU per address, as opposed to one BU for the
entire prefix? If so, why? a prefix BU is much more efficient. That would
just be a less efficient version of MIP-based MRs.

Hesham