Re: [netext] Consensus call: Work on specifying prefix delegation for Proxy Mobile IPv6?

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sat, 20 August 2011 13:52 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 3046821F8661 for <netext@ietfa.amsl.com>; Sat, 20 Aug 2011 06:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.116
X-Spam-Level:
X-Spam-Status: No, score=-0.116 tagged_above=-999 required=5 tests=[AWL=0.055, 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 At2fZiUVb8Ol for <netext@ietfa.amsl.com>; Sat, 20 Aug 2011 06:52:41 -0700 (PDT)
Received: from smtp1-g21.free.fr (unknown [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB9521F85A3 for <netext@ietf.org>; Sat, 20 Aug 2011 06:52:39 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id E92FD94001B; Sat, 20 Aug 2011 15:53:33 +0200 (CEST)
Message-ID: <4E4FBC5B.9030504@gmail.com>
Date: Sat, 20 Aug 2011 15:53:31 +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: jouni korhonen <jouni.nospam@gmail.com>
References: <CA728881.25763%sgundave@cisco.com> <CA72923B.2576F%sgundave@cisco.com> <CABk4tj948RNefsD+HsTmOjEQiO0SejCvCDfP9AV62AHJTuYJrA@mail.gmail.com> <4E0D0C6B-1A81-4330-A9ED-873A2E8F4088@gmail.com> <4E4E6A1D.70302@gmail.com> <AA05D913-9AC4-437A-BE50-BDFB14A69DB2@gmail.com>
In-Reply-To: <AA05D913-9AC4-437A-BE50-BDFB14A69DB2@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 110820-0, 20/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: Sat, 20 Aug 2011 13:52:42 -0000

Le 19/08/2011 23:11, jouni korhonen a écrit :
>
> Alex,
>
> FWIW is to make sure prefix delegation works when the MN in a RR
> role uses DHCPv6-PD to get its prefixes.

MN in a RR role?  Is the MN going to use the delegated prefix as an HNP?

Alex

> It looks straight forward but there are few things to clarify in
> general operation and PBU/PBA signaling: what happens after a
> handover as the new MAG needs to learn delegated prefixes to setup a
> proper forwarding state, and how DHCPv6 (relay in a MAG) and LMA
> coordinate delegated prefixes to get the delegation work ok&
> establish proper forwarding state... etc.
>
> There might be other cases and solutions but the above stuff is
> actually needed..
>
> - Jouni
>
>
>
> On Aug 19, 2011, at 4:50 PM, Alexandru Petrescu wrote:
>
>> Le 18/08/2011 23:52, Jouni a écrit :
>>>
>>> It is about providing mobility for delegated prefixes.
>>
>> Thanks Jouni.  Is it for an MR?  If yes, then there may exist
>> other solutions possible as well.  Have you considered them?
>>
>> Alex
>>
>>>
>>> - Jouni (as a co-author)
>>>
>>>
>>> On Aug 19, 2011, at 12:00 AM, Jong-Hyouk Lee wrote:
>>>
>>>> Hi, Sri.
>>>>
>>>> Thanks for sharing your opinions. I would like to also hear a
>>>> reply from Joy. Joy, could you clearly state your views on the
>>>> question from Alex?
>>>>
>>>> Cheers.
>>>>
>>>> On Thu, Aug 18, 2011 at 6:56 PM, Sri
>>>> Gundavelli<sgundave@cisco.com>   wrote:
>>>>> #2 Assigning MNP to NEMO Mobile Router = RFC3963. NEMO MR
>>>>> per definition is CMIP enabled.
>>>>
>>>> To ensure the terminology is right:
>>>>
>>>> Delegated Prefix - Prefixes hosted by the mobile node, or the
>>>> network elements behind the mobile node
>>>>
>>>> Hosted Prefixes - prefixes hosted by the PMIPv6 mobility
>>>> elements on the MN-AR access link. These are not delegated
>>>> prefixes. An IP host behind the mobile node cannot use this
>>>> prefix to generate an address, it wont receive RA's with these
>>>> PIO's.
>>>>
>>>> HNP typically implied prefixes delivered on PMIPv6 signaling
>>>> plane. If DHCP PD is used by MN or a node behind for obtaining
>>>> prefixes, those are simple IP prefixes. However, if mobility
>>>> is provided to those prefixes, in the form of this draft, we
>>>> can group them as HNP's, as mobility is provided and those
>>>> prefixes are anchored on the LMA, from routing perspective.
>>>>
>>>> MN/MR Distinction is clear I assume. But, NEMO MR, I may have
>>>> implied, as mobile router with CMIP functionality in my prev
>>>> mail. But, probably NEMO is a generic term. Any case, the
>>>> distinction is understood, with or without CMIP ...
>>>>
>>>> Sri
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 8/18/11 9:14 AM, "Sri Gundavelli"<sgundave@cisco.com>
>>>> wrote:
>>>>
>>>>> 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
>>>>>
>>>>>> 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)
>>>>>
>>>>> #2 Assigning MNP to NEMO Mobile Router = RFC3963. NEMO MR
>>>>> per definition is CMIP enabled.
>>>>>
>>>>>
>>>>> So, the draft is supporting #1.
>>>>>
>>>>>
>>>>> Sri
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 8/18/11 8:50 AM, "Alexandru
>>>>> Petrescu"<alexandru.petrescu@gmail.com> wrote:
>>>>>
>>>>>> Hello Raj,
>>>>>>
>>>>>> Le 10/08/2011 23:34, Basavaraj.Patil@nokia.com a écrit :
>>>>>>>
>>>>>>> At IETF81, Carl Williams presented the I-D: "Prefix
>>>>>>> Delegation for Proxy Mobile
>>>>>>> IPv6"<draft-zhou-netext-pd-pmip-01.txt>
>>>>>>>
>>>>>>> General consensus at the Netext WG meeting was that
>>>>>>> prefix delegation is a required feature for PMIP6.
>>>>>>
>>>>>> Please specify whether this prefix delegation feature is
>>>>>> for the goal of supporting Network Mobility with PMIP?
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> This to help formulate a problem for prefix delegation for
>>>>>> PMIP.
>>>>>>
>>>>>> [...]
>>>>>>> We are now following up with the questions on the ML.
>>>>>>>
>>>>>>> Question to WG:
>>>>>>>
>>>>>>> 1. Should the WG specify prefix-delegation support for
>>>>>>> PMIP6?
>>>>>>>
>>>>>>> Yes   [ ] No    [ ]
>>>>>>
>>>>>> Yes, if it is for MNP for Mobile Router.
>>>>>>
>>>>>>> 2. Can we adopt as WG document the solution proposed in
>>>>>>> I-D: draft-zhou-netext-pd-pmip-01.txt as the starting
>>>>>>> point of this feature?
>>>>>>>
>>>>>>> Yes   [ ] No    [ ]
>>>>>>
>>>>>> No, unless the problem is clearer.
>>>>>>
>>>>>> I hope this helps.
>>>>>>
>>>>>> Alex
>>>>>>
>>>>>>>
>>>>>>> Please respond by August 18th on the ML.
>>>>>>>
>>>>>>> -Chairs
>>>>>>>
>>>>>>> Please see the discussion at the IETF81 WG meeting on
>>>>>>> this topic at:
>>>>>>> http://www.ietf.org/proceedings/81/minutes/netext.txt
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________ netext
>>>>>>> mailing list netext@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/netext
>>>>>>>
>>>>>>
>>>>>> _______________________________________________ netext
>>>>>> mailing list netext@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/netext
>>>>>
>>>>> _______________________________________________ netext
>>>>> mailing list netext@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/netext
>>>>
>>>> _______________________________________________ netext mailing
>>>> list netext@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/netext
>>>>
>>>>
>>>>
>>>> -- IMARA Team, INRIA, France. Jong-Hyouk Lee, living somewhere
>>>> between /dev/null and /dev/random.
>>>>
>>>> #email: hurryon (at) gmail (dot) com || jong-hyouk.lee (at)
>>>> inria (dot) fr #webpage: https://sites.google.com/site/hurryon/
>>>>  _______________________________________________ netext
>>>> mailing list netext@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/netext
>>>
>>> _______________________________________________ netext mailing
>>> list netext@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netext
>>>
>>
>> _______________________________________________ netext mailing list
>> netext@ietf.org https://www.ietf.org/mailman/listinfo/netext
>
>