[MEXT] Mobile IPv6 operation with Firewalls (was Re: [Recharter.2])
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MEXT] Mobile IPv6 operation with Firewalls (was Re: [Recharter.2])



Gerardo, George,

Mobile IPv6 operation with firewalls is already there in the current 
mext charter.

Vijay

Giaretta, Gerardo wrote:
> Hi Julien,
> 
> Please find below my list:
> 
> 1) Binding Revocation [CR]
> 2) 4283bis [R]
> 3) Virtual Home Link configuration for Mobile IPv6 [CR]
> 4) Generic Notification Message for Mobile IPv6 [R]
> 5) MIPv6 Firewall [R]
> 
> Thanks
> Gerardo
> 
>> -----Original Message-----
>> From: mext-bounces at ietf.org [mailto:mext-bounces at ietf.org] On Behalf
> Of
>> Julien Laganier
>> Sent: Tuesday, February 12, 2008 7:32 AM
>> To: mext at ietf.org
>> Subject: [MEXT] [Recharter.2]
>>
>> Folks,
>>
>> This is the next step in the recharter process. We'd like to get input
>> from WG participants on what should be the items included in
>> rechartering, what are their priorities, and who is willing to
>> sustain the effort. When that step is completed we will take the WG
>> input and discuss with our AD to move forward with deciding what to
>> include or not in the charter. Your input should be sent to the list
>> during the following two weeks, by 2008-02-26.
>>
>> Please pick from the list of items below the items you think the WG
>> should work on, and order them in decreasing priority (just to make
>> sure, first priority items goes first in the list you're making :).
>>
>> List of items:
>>
>> Binding Revocation for IP Mobility
>> MIPv6 home link operation in various SDOs
>> IP Tunneling Optimization in a Mobile Environment
>> Generic Notification Message for Mobile IPv6
>> GRE requirements for IPv6 mobility
>> 4283bis to extend MN identifier to other identifiers
>> Mobile IPv6 Bootstrapping for the Authentication Option Protocol
>> Interaction between Mobile IPv6 and IPsec/IKE by PF_KEY extensions
>> Virtual Home Link configuration for Mobile IPv6
>> Extend DSMIPv6 Home Network Support
>>
>> Also, please prefix each of the items in your list with the letters E,
> C
>> and/or R if you're willing to:
>>
>> - [E]dit: Are you willing to edit the draft corresponding to the
>>   item.
>>
>> - [C]ontribute: Are you willing to propose text for the draft.
>>
>> - [R]eview: Are you willing to review new revisions of the draft when
>>   being asked by the chairs.
>>
>> As an example, that could be one input list:
>>
>> E MIPv6 home link operation in various SDOs
>> CR Binding Revocation for IP Mobility
>> R IP Tunneling Optimization in a Mobile Environment
>>
>> meaning that the MIPv6 home link is first priority and you volunteer
> to
>> edit, Binding revocation is second priority and you're willing to
>> contribute and review, while IP tunneling optimization is third
>> priority and you're willing to review.
>>
>> Hope this is understandable :)
>>
>> Thanks.
>>
>> -- julien and marcello, MEXT chairs
>> _______________________________________________
>> MEXT mailing list
>> MEXT at ietf.org
>> http://www.ietf.org/mailman/listinfo/mext
> _______________________________________________
> MEXT mailing list
> MEXT at ietf.org
> http://www.ietf.org/mailman/listinfo/mext

_______________________________________________
MEXT mailing list
MEXT at ietf.org
http://www.ietf.org/mailman/listinfo/mext



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