Subject: Re: [multimob] multimob Digest, Vol 43, Issue 1

From: "Shuai Gao" <[email-masked]>
Date: Wed, 8 Dec 2010 07:42:12 +0800

Hi, all,
	I found that "source mobility" are still not included in the first paragraph of the new charter.  Is it possbile to 
modify that now?

Best,

Shuai Gao

======= 2010-12-08 01:32:33 您在来信中写道：=======

>If you have received this digest without all the individual message
>attachments you will need to update your digest options in your list
>subscription.  To do so, go to 
>
>https://www.ietf.org/mailman/listinfo/multimob
>
>Click the 'Unsubscribe or edit options' button, log in, and set "Get
>MIME or Plain Text Digests?" to MIME.  You can set this option
>globally for all the list digests you receive at this point.
>
>
>
>Send multimob mailing list submissions to
>	[email-masked]
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://www.ietf.org/mailman/listinfo/multimob
>or, via email, send a message with subject or body 'help' to
>	[email-masked]
>
>You can reach the person managing the list at
>	[email-masked]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of multimob digest..."
>
>
>Today's Topics:
>
>   1.  WG Action: RECHARTER: Multicast Mobility (multimob)
>      (IESG Secretary)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue,  7 Dec 2010 09:30:04 -0800 (PST)
>From: IESG Secretary <[email-masked]>
>Subject: [multimob] WG Action: RECHARTER: Multicast Mobility
>	(multimob)
>To: IETF Announcement list <[email-masked]>
>Cc: [email-masked], [email-masked]
>Message-ID: <[email-masked]>
>Content-Type: text/plain; charset="utf-8"
>
>The Multicast Mobility (multimob) working group in the Internet Area of
>the IETF has been rechartered.  For additional information, please contact
>the Area Directors or the working group Chairs.
>
>Multicast Mobility (multimob)
>---------------------------------------------------
>Current Status: Active Working Group
>
>Chairs:
>    Behcet Sarikaya <[email-masked]>
>    Stig Venaas <[email-masked]>
>    Behcet Sarikaya <[email-masked]>
>
>Internet Area Directors:
>    Ralph Droms <[email-masked]>
>    Jari Arkko <[email-masked]>
>
>Internet Area Advisor:
>    Jari Arkko <[email-masked]>
>
>Mailing Lists:
>    General Discussion: [email-masked]
>    To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
>    Archive:           
>http://www.ietf.org/mail-archive/web/multimob/current/maillist.html
>
>Description of Working Group:
>
> The Multicast mobility (multimob) working group provides guidance
> for supporting multicast in a mobile environment. The scope of work
> will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
> listener mobility. The group will work on extensions of Proxy Mobile
> IPv6 to improve its capability to handle multicast efficiently. Work
> requiring modifications to IGMPv3/MLDv2 is out of scope in this
> stage of this working group, however, as are modifications to
> multicast routing protocols.
>
> Specific goals for the group are: 
>
> - A solution to the tunnel convergence problem by separating
>   multicast routing from a mobility anchor. Possible techniques are
>   using native infrastructure, using a dedicated mobility anchor
>   etc.
>
> - Mechanisms to optimize multicast traffic during a handover. Such
>   mechanisms may include context transfer functionality.
>
> - Mechanisms needed to support multicast source mobility. Both any
>   source multicast and source specific multicast source mobility
>   will be covered.
>
> - Document the configuration of IGMPv3/MLDv2 in mobile environments
>
> The group shall primarily focus on Proxy Mobile IPv6 (PMIPv6) based
> networks when looking at the first three items. It is possible but
> not required that the solutions are applicable also for Mobile IPv6
> (MIPv6) based networks.
>
> For background, the PMIPv6 specification as defined in RFC 5213 does
> not describe how to support multicast. Some forms of multicast
> support can, however, be built in the involved nodes by using
> existing capabilities of multicast protocols and the underlying
> mobility protocols. The working group has already documented how
> existing mechanisms can be used to support multicast, without
> requiring any additions or changes to message types and parameters
> specified in RFC 5213, and assuming an unmodified mobile host. The
> current goals of the working group relate to improving the
> efficiency of this base solution.
>
> IGMPv3/MLDv2 has been specified for wired networks with shared links.
> Mobile nodes have needs that are specific to wireless networks and
> mobility (e.g. entering a dormant mode to conserve battery power,
> minimizing the latency for joining and leaving a group in support of
> movement).
>
> In performing its work, the working group will work closely with
> both the mobility community (NETEXT WG) and the multicast community
> (MBONED WG). The group will consider both source specific multicast
> and any source multicast multicast models.
>
> Future work, subject to rechartering, may study/evaluate extensions
> to IGMPv3/MLDv2 to support better operation in mobile environments.
>
>Goals and Milestones:
>
>Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for
>
>           mobility
>Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, 
>           for publication as either Informational or Best Current 
>           Practice
>Jun 2011 - Initial version of document on PMIPv6 routing optimizations 
>           to avoid tunnel convergence problem
>Nov 2011 - Initial version of document on PMIPv6 handover optimizations
>Nov 2011 - Initial version of document on PMIPv6 multicast source 
>           mobility solution
>Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for 
>           publication as Internet Standard
>Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for 
>           publication as Internet Standard
>Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for 
>           publication as Internet Standard
>Dec 2012 - Decision to include additional optimization work involving 
>           extensions to IGMPv3 or MLDv2
>Dec 2012 - Recharter based on the above decisions (or close the group if 
>           no new work is needed)
>
>
>
>------------------------------
>
>_______________________________________________
>multimob mailing list
>[email-masked]
>https://www.ietf.org/mailman/listinfo/multimob
>
>
>End of multimob Digest, Vol 43, Issue 1
>***************************************
>.

= = = = = = = = = = = = = = = = = = = =

　　　　　　　　致
礼！

Shuai Gao
National Engineering Lab for Next Generation Internet Interconnection Devices
Beijing Jiaotong University
Beijing, China, 100044
[email-masked]
2010-12-08