Re: [Dime] Fwd: New Version Notification for draft-korhonen-dime-mip6-feature-bits-01
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Hi Jouni,

I have a comment on the "VPN Gateway feature". There is no document
that describes what it means for a Mobile IPv6 home agent to act as a
VPN gateway. The IKEv2 exchange between the MN and the HA [RFC 4877
and 5026] already supports mutual authentication, address assignment
and setting up of tunnel mode ESP SAs. Are you referring to this as
VPN mode? But isn't this regular Home agent functionality?

Or is there a separate IPsec VPN that is first setup and then Mobile
IPv6 is run on top of the IPsec tunnels?

Vijay

On Wed, Jun 10, 2009 at 2:55 AM, jouni korhonen<jouni.nospam at gmail.com> wrote:
> 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 at ietf.org>
>> Date: June 10, 2009 12:26:53 PM GMT+03:00
>> To: jouni.nospam at 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 at ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.