Re: draft charter text updates in github..

Weixinpeng <[email protected]>
Newsgroups gmane.ietf.nemo
Message-ID <C5C3BB522B1DDF478AA09545169155B46D80BA15@nkgeml507-mbx.china.huawei.com>
Hi Jouni, all,
"
      .....The protocol solutions
      should be based on existing IP mobility protocols, either host- or
      network-based, such as Mobile IPv6 [RFC6275, 5555], Proxy Mobile IPv6
      [RFC5213, 5844] and NEMO [RFC3963]. However, mobility management in a
      limited area, such as within an autonomous system, is not strictly
      limited to mentioned IP mobility protocols but can be any existing or
      a new protocol solution enabling the movement of a mobile node such
      as routing protocols....."
As my understanding for this text, DMM work group aims to realize mobility management by using/extending the existing host- or network-based protocols
for all the scenarios except for the limited area (relatively small network as my understanding).  Right?
Thanks.
BR
Xinpeng

>-----Original Message-----
>From: dmm [mailto:[email protected]] On Behalf Of Jouni Korhonen
>Sent: Friday, June 06, 2014 7:47 PM
>To: [email protected]
>Subject: [DMM] draft charter text updates in github..
>
>Folks,
>
>Minor changes..
>
>https://github.com/jounikor/dmm-re-charter/blob/master/recharter_draft.tx
>t
>
>IMHO..the charter as it is today, would allow pretty much any solution from
>legacy anchoring to herd of pigeons carrying IP.. ;-)
>
>I have put in editorial changes of my own and clear text proposals received
>from others.
>
>- Jouni
>
>_______________________________________________
>dmm mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/dmm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.