Re: [netext] Consensus call: Work on specifying prefix delegation for Proxy Mobile IPv6?
Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 19 August 2011 13:35 UTC
Return-Path: <alexandru.petrescu@gmail.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 410C821F8B10 for <netext@ietfa.amsl.com>; Fri, 19 Aug 2011 06:35:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.061
X-Spam-Level:
X-Spam-Status: No, score=-0.061 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
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 V2KURs1ZeIbz for <netext@ietfa.amsl.com>; Fri, 19 Aug 2011 06:35:01 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 9AAE921F8B04 for <netext@ietf.org>; Fri, 19 Aug 2011 06:35:00 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id C8D229400C2; Fri, 19 Aug 2011 15:35:51 +0200 (CEST)
Message-ID: <4E4E66B5.9090206@gmail.com>
Date: Fri, 19 Aug 2011 15:35:49 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
References: <CA728881.25763%sgundave@cisco.com>
In-Reply-To: <CA728881.25763%sgundave@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 110819-0, 19/08/2011), Outbound message
X-Antivirus-Status: Clean
Cc: netext@ietf.org
Subject: Re: [netext] Consensus call: Work on specifying prefix delegation for Proxy Mobile IPv6?
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: Fri, 19 Aug 2011 13:35:02 -0000
Le 18/08/2011 18:14, Sri Gundavelli a écrit : > Alex: > > If I may comment. > > >> Please specify whether this prefix delegation feature is for the >> goal of > supporting Network Mobility with PMIP? > > #1 Implies, mobility for the delegated prefixes Hm. I thought it was only for initial assignment of prefixes (DHCP), not for mobility (PBU). I.e. assign prefix(es) upon initial attachment, with DHCP, and then do PBU to support mobility. >> Or is it to assign the HNP to the Mobile Host (not necessarily to >> assign > MNP for NEMO Mobile Router)? The two goals are distinctive IMHO. > > Assigning HNP to mobile = mobility + delegated prefix (Same as #1) I am not sure. Initial assignment is different than PBU upon each movement. And the PMIP spec has a need (IIRC) to assign that HNP somehow. > #2 Assigning MNP to NEMO Mobile Router = RFC3963. NEMO MR per > definition is CMIP enabled. Yes, NEMO MR by definition is CMIP enabled (and CMIP/NEMO does not assign MNP to MR). I meant to say that PMIP may need, in some cases only, to assign an HNP for MR (HoA) _and_ an MNP for the LFNs behind MR. In some cases these two prefixes are different. > So, the draft is supporting #1. Does the draft imply that the same delegated prefix is used to form addresses for LFNs _and_ to form the HoA of MR? Alex
- [netext] Consensus call: Work on specifying prefi… Basavaraj.Patil
- Re: [netext] Consensus call: Work on specifying p… Jouni
- Re: [netext] Consensus call: Work on specifying p… Sri Gundavelli
- Re: [netext] Consensus call: Work on specifying p… zhou.xingyue
- Re: [netext] Consensus call: Work on specifying p… zhu.chunhui
- Re: [netext] Consensus call: Work on specifying p… Jiang Dong
- Re: [netext] Consensus call: Work on specifying p… Dirk.von-Hugo
- Re: [netext] Consensus call: Work on specifying p… Jong-Hyouk Lee
- Re: [netext] Consensus call: Work on specifying p… Hidetoshi Yokota
- Re: [netext] Consensus call: Work on specifying p… 马骁
- [netext] 答复: Re: Consensus call: Work on specifyi… zhou.xingyue
- Re: [netext] Consensus call: Work on specifying p… jonne.soininen
- Re: [netext] 答复: Re: Consensus call: Work on spec… Jong-Hyouk Lee
- Re: [netext] Consensus call: Work on specifying p… liu dapeng
- Re: [netext] Consensus call: Work on specifying p… Hui Deng
- Re: [netext] Consensus call: Work on specifying p… Alexandru Petrescu
- Re: [netext] Consensus call: Work on specifying p… Sri Gundavelli
- Re: [netext] Consensus call: Work on specifying p… Sri Gundavelli
- Re: [netext] Consensus call: Work on specifying p… Jong-Hyouk Lee
- Re: [netext] Consensus call: Work on specifying p… Basavaraj.Patil
- Re: [netext] Consensus call: Work on specifying p… Jouni
- Re: [netext] Consensus call: Work on specifying p… Alexandru Petrescu
- Re: [netext] Consensus call: Work on specifying p… Alexandru Petrescu
- Re: [netext] 答复: Re: Consensus call: Work on spec… Daniel Migault
- Re: [netext] Consensus call: Work on specifying p… Alexandru Petrescu
- Re: [netext] Consensus call: Work on specifying p… Alexandru Petrescu
- Re: [netext] Consensus call: Work on specifying p… Alexandru Petrescu
- Re: [netext] Consensus call: Work on specifying p… jouni korhonen
- Re: [netext] Consensus call: Work on specifying p… Alexandru Petrescu