[secdir] [new-work] WG Review: Recharter of Mobility Multicast (multimob)

IESG Secretary <iesg-secretary@ietf.org> Tue, 23 November 2010 17:19 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 4B2163A6988; Tue, 23 Nov 2010 09:19:16 -0800 (PST)
X-Original-To: new-work@ietf.org
Delivered-To: new-work@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 2B7743A6985; Tue, 23 Nov 2010 09:19:12 -0800 (PST)
From: IESG Secretary <iesg-secretary@ietf.org>
To: new-work@ietf.org
Mime-Version: 1.0
Message-Id: <20101123171913.2B7743A6985@core3.amsl.com>
Date: Tue, 23 Nov 2010 09:19:12 -0800
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: new-work-bounces@ietf.org
Errors-To: new-work-bounces@ietf.org
X-Mailman-Approved-At: Tue, 23 Nov 2010 11:21:18 -0800
Subject: [secdir] [new-work] WG Review: Recharter of Mobility Multicast (multimob)
X-BeenThere: secdir@ietf.org
Reply-To: iesg@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2010 17:19:16 -0000

A modified charter has been submitted for the Mobility Multicast
(multimob) working group in the Internet Area of the IETF.  The IESG has
not made any determination as yet.  The modified charter is provided below
for informational purposes only.  Please send your comments to the IESG
mailing list (iesg@ietf.org) by Tuesday, November 30, 2010.

Mobility Multicast (multimob)
Current Status: Active Working Group 
Last Modified: 2010-11-09

    Behcet Sarikaya <sarikaya@ieee.org>
    Stig Venaas <stig@venaas.com>
    Behcet Sarikaya <bsarikaya@huawei.com>

Internet Area Directors:
    Ralph Droms <rdroms.ietf@gmail.com>
    Jari Arkko <jari.arkko@piuha.net>

Internet Area Advisor:
    Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:
    General Discussion: multimob@ietf.org
    To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob

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

 - 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

 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 
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, 
           for publication as either Informational or Best Current 
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)
new-work mailing list