Re: [Dime] Fwd: New Version Notification fordraft-korhonen-dime-mip6-feature-bits-01

Hi Qin,

It is yet another subscription related policy decision.  An operator  
might, for some reason, to have such functionality to be disabled. If  
you go back to draft-ietf-dime-mip6-split-12, you can find all these  
feature vector flag bits there.

If the AAA does not authorize the use of MCoA the HA shall act as it  
would not support MCoA in the first place.

Cheers,
	Jouni

On Jun 10, 2009, at 2:45 PM, Qin Wu wrote:

> Hi, Jouni:
> When the HA support Multiple CoA feature, why should the AAA server   
> care this feature?
> If the AAA server neglectsthis feature or does not authorize the use  
> of CoA, does it mean
> mutiple CoA registration will fail or something else?
> If I miss anything, please correct me.
>
> Regards!
> -Qin
> ----- Original Message -----
> From: "jouni korhonen" <jouni.nospam@gmail.com>
> To: <dime@ietf.org>
> Sent: Wednesday, June 10, 2009 5:55 PM
> Subject: [Dime] Fwd: New Version Notification fordraft-korhonen-dime- 
> mip6-feature-bits-01
>
>
>> Hi all,
>>
>> I have updated the additional feature bits draft. I did remove some
>> stuff so that the draft now only reserves MIP6-Feature-Vector flag
>> bits and nothing more. I'll forward the draft soon to RFC editor so  
>> if
>> anyone has comments, please be quick :)
>>
>> Cheers,
>> Jouni
>>
>> Begin forwarded message:
>>
>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>> Date: June 10, 2009 12:26:53 PM GMT+03:00
>>> To: jouni.nospam@gmail.com
>>> Subject: New Version Notification for  draft-korhonen-dime-mip6-
>>> feature-bits-01
>>>
>>>
>>> A new version of I-D, draft-korhonen-dime-mip6-feature-bits-01.txt
>>> has been successfuly submitted by Jouni Korhonen and posted to the
>>> IETF repository.
>>>
>>> Filename: draft-korhonen-dime-mip6-feature-bits
>>> Revision: 01
>>> Title: Diameter MIP6 Feature Vector Additional Bit Allocations
>>> Creation_date: 2009-06-10
>>> WG ID: Independent Submission
>>> Number_of_pages: 5
>>>
>>> Abstract:
>>> During the Mobile IPv6 Split Scenario bootstrapping the Mobile IPv6
>>> Home Agent and the Authentication, Authorization, and Accounting
>>> server may exchange a set of authorized mobility capabilities.  This
>>> document defines new mobility capability flags that are used to
>>> authorize per Mobile Node route optimization, Multiple Care-of
>>> Address and user plane traffic encryption support.  Furthermore,  
>>> this
>>> document also defines a capability flag of indicating whether the
>>> Home Agent is authorized to act as a stand alone Virtual Private
>>> Network gateway.
>>>
>>>
>>>
>>> The IETF Secretariat.
>>>
>>>
>>
>> _______________________________________________
>> DiME mailing list
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime