Re: [MEXT] [dmm] suggest charter item for distributed mobility work

Just to clarify:
Design teams are defined in RFC 2418 as:

"6.5. Design teams

    It is often useful, and perhaps inevitable, for a sub-group of a
    working group to develop a proposal to solve a particular problem.
    Such a sub-group is called a design team.  In order for a design team
    to remain small and agile, it is acceptable to have closed membership
    and private meetings.  Design teams may range from an informal chat
    between people in a hallway to a formal set of expert volunteers that
    the WG chair or AD appoints to attack a controversial problem.  The
    output of a design team is always subject to approval, rejection or
    modification by the WG as a whole."


This design team that Dapeng is forming falls AFAIK into the first 
category i.e. an informal chat between people and it has NOT been 
appointed by the chairs.
As such, they can form any design team that they feel like, there is 
absolutely no problem with that.

Of course, as any design team, the output needs to be presented to the 
WG and it is subject to the WG acceptance, as any other piece of work.

I hope this clarifies this.

Regards, marcelo


El 05/03/11 0:16, Behcet Sarikaya escribió:
> Folks, I had just expressed my personal opinion.
>
> You should probably wait for the chairs announcement before forming a design
> team.
>
> Regards,
>
> Behcet
>> Dapeng,
>>
>> I would also like to join the work for contribution.
>>
>> Many  thanks,
>>
>> *************************
>> Seok Joo Koh
>> [email protected]
>> http://protocol.knu.ac.kr/
>>
>>
>> -----  Original Message -----
>> From: "Anthony Chan"<[email protected]>
>> To:<[email protected]>;<[email protected]>;
>> <[email protected]>;
>>
>> <[email protected]>
>> Cc:<[email protected]>;<[email protected]>
>> Sent: Friday, March 04,  2011 2:53 AM
>> Subject: Re: [dmm] [MEXT] suggest charter item for distributed  mobility work
>>
>>
>> Dapeng,
>> I also like to contribute.
>> H Anthony  Chan
>>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf Of
>> [email protected]
>> Sent:  Thursday, March 03, 2011 7:36 AM
>> To: [email protected]; [email protected]; [email protected]
>> Cc: [email protected]; [email protected]
>> Subject: Re: [dmm] [MEXT]  suggest charter item for distributed mobility work
>>
>> Hi Dapeng,
>>
>> I'm  also interesting in working on this item. Also agree, and happy, that
>> you  lead the work.
>>
>> Pierrick
>>> -----Message d'origine-----
>>> De : [email protected] [mailto:[email protected]] De la part  de
>>> Demaria Elena
>>> Envoyé : jeudi 3 mars 2011 11:51
>>> À :  'liu dapeng'; 'Behcet Sarikaya'
>>> Cc : '[email protected]'; '[email protected]'
>>> Objet : Re: [dmm] [MEXT]  suggest charter item for distributed mobility
>>> work
>>>
>>> Hi  Dapeng,
>>> I'd like to contribute to this work.
>>>
>>>   Elena
>>>
>>>
>>>> -----Original Message-----
>>>> From: [email protected] [mailto:[email protected]] On Behalf  Of
>>> liu
>>>> dapeng
>>>> Sent: Thursday, March 03, 2011  4:17 AM
>>>> To: Behcet Sarikaya
>>>> Cc: [email protected]; [email protected]
>>>> Subject: Re: [dmm]  [MEXT] suggest charter item for distributed mobility
>>>> work
>>>   >
>>>> Hi Behcet,
>>>>
>>>>
>>>> 2011/2/19,  Behcet Sarikaya<[email protected]>:
>>>   >  >  Hi Dapeng,
>>>>>
>>>>   >
>>>>>> Hello Julien,
>>>>   >>
>>>>>> Thanks for the information. But my question is:  since the  charter is
>>>>>> extended to "work on  operational considerations on setting up  Mobile
>>>>>> IPv6  networks so that traffic is distributed in an optimal way".
>>> Does
>>>   >  >>  it mean that the extended charter include   problem/gap/scenario
>>>>>> analysis of distributing the mobility  anchor  (DMM)?
>>>>>>
>>>>>> I remember it  seem that people agreed to do the analysis work of  DMM
>>>>   >>  as the first step in Beijing meeting?
>>>>   >  My understanding is that the new informational document will be  inline
>>>> with
>>>>> Julien's presentation he had in  Beijing mext additional session we had
>>>> on
>>>>>   dmm
>>>>> and explain how MIPv6 as defined currently can be used to  distribute
>>> the
>>>>> traffic
>>>>> in an optimal  way.
>>>>>
>>>>> I suggest that you take the lead in  this effort.
>>>> ==>
>>>>
>>>> I think  DMM barbof contributors have already done some work in this
>>>> area.  So if people agree I would like to organize writing this draft.
>>>>   Anyone who is interested
>>>> to join the design team could reply this  mail to let me know. thanks.
>>>>
>>>> Best regards,
>>>   >  Dapeng Liu
>>>>> Regards,
>>>>   >
>>>>> Behcet
>>>>>
>>>>>
>>>>   >
>>>>>
>>>>   _______________________________________________
>>>> dmm mailing  list
>>>> [email protected]
>>>> https://www.ietf.org/mailman/listinfo/dmm
>>> Questo messaggio  e i suoi allegati sono indirizzati esclusivamente alle
>>> persone indicate.  La diffusione, copia o qualsiasi altra azione derivante
>>> dalla conoscenza  di queste informazioni sono rigorosamente vietate.
>>> Qualora abbiate  ricevuto questo documento per errore siete cortesemente
>>> pregati di darne  immediata comunicazione al mittente e di provvedere alla
>>> sua  distruzione, Grazie.
>>>
>>> This e-mail and any attachments is  confidential and may contain privileged
>>> information intended for the  addressee(s) only. Dissemination, copying,
>>> printing or use by anybody  else is unauthorised. If you are not the
>>> intended recipient, please  delete this message and any attachments and
>>> advise the sender by return  e-mail, Thanks.
>>>
>>>   _______________________________________________
>>> dmm mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/dmm
>> _______________________________________________
>> dmm  mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/dmm
>>
>> _______________________________________________
>> dmm  mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/dmm
>>
>>
>
>
> _______________________________________________
> MEXT mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/mext
>