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

[Alexandru Petrescu <[e-mail]>]

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<[e-mail]>   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"<[e-mail]>
>>>> 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"<[e-mail]> wrote:
>>>>>
>>>>>> Hello Raj,
>>>>>>
>>>>>> Le 10/08/2011 23:34, [e-mail] 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 [e-mail]
>>>>>>> https://www.ietf.org/mailman/listinfo/netext
>>>>>>>
>>>>>>
>>>>>> _______________________________________________ netext
>>>>>> mailing list [e-mail]
>>>>>> https://www.ietf.org/mailman/listinfo/netext
>>>>>
>>>>> _______________________________________________ netext
>>>>> mailing list [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/netext
>>>>
>>>> _______________________________________________ netext mailing
>>>> list [e-mail]
>>>> 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 [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/netext
>>>
>>> _______________________________________________ netext mailing
>>> list [e-mail]
>>> https://www.ietf.org/mailman/listinfo/netext
>>>
>>
>> _______________________________________________ netext mailing list
>> [e-mail] https://www.ietf.org/mailman/listinfo/netext
>
>