MULTIMOB Group D. von Hugo
Internet-Draft Telekom Innovation Laboratories
Intended status: Experimental H. Asaeda
Expires: September 20, 2013 NICT
P. Seite
France Telecom - Orange
March 19, 2013
Context Transfer for Multicast support in Distributed Mobility
Management (DMM)
draft-vonhugo-multimob-dmm-context-02
Abstract
This document describes a context transfer based concept to support
overarching IP multicast services applicable to various existing
approaches for Distributed Mobility Management.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 20, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
von Hugo, et al. Expires September 20, 2013 [Page 1]
Internet-Draft Context Transfer for DMM Multicast March 2013
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
3. Handover Process . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Multicast Context Transfer Data Format . . . . . . . . . . 7
3.2. Multicast Context Transfer with MLD Proxy . . . . . . . . 7
3.3. Multicast Context Transfer with PIM-SM . . . . . . . . . . 10
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7.1. Normative References . . . . . . . . . . . . . . . . . . . 14
7.2. Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
von Hugo, et al. Expires September 20, 2013 [Page 2]
Internet-Draft Context Transfer for DMM Multicast March 2013
1. Introduction
This document describes an application of various existing approaches
for Distributed Mobility Management (DMM) [15] to support overarching
IP multicast services with Proxy Mobile IPv6 (PMIPv6) [3] and Client
Mobile IPv6 (MIPv6) [2], respectively. Key concept of Distributed
Mobility Management (DMM) in a flat network architecture where core
entities and functionalities are deployed in a distributed manner
assumes a mobile node to use the first access router (AR) it attaches
to as principal mobility anchor, i.e. Home Agent (HA) in MIPv6 or