draft-ietf-multimob-pmipv6-base-solution-06.txt   draft-ietf-multimob-pmipv6-base-solution-07.txt 
MULTIMOB Group T C. Schmidt MULTIMOB Group T C. Schmidt
Internet-Draft HAW Hamburg Internet-Draft HAW Hamburg
Intended status: BCP M. Waehlisch Intended status: BCP M. Waehlisch
Expires: April 28, 2011 link-lab & FU Berlin Expires: July 2, 2011 link-lab & FU Berlin
S. Krishnan S. Krishnan
Ericsson Ericsson
October 25, 2010 December 29, 2010
Base Deployment for Multicast Listener Support in PMIPv6 Domains Base Deployment for Multicast Listener Support in PMIPv6 Domains
draft-ietf-multimob-pmipv6-base-solution-06 draft-ietf-multimob-pmipv6-base-solution-07
Abstract Abstract
This document describes deployment options for activating multicast This document describes deployment options for activating multicast
listener functions in Proxy Mobile IPv6 domains without modifying listener functions in Proxy Mobile IPv6 domains without modifying
mobility and multicast protocol standards. Similar to Home Agents in mobility and multicast protocol standards. Similar to Home Agents in
Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as
multicast subscription anchor points, while Mobile Access Gateways multicast subscription anchor points, while Mobile Access Gateways
provide MLD proxy functions. In this scenario, Mobile Nodes remain provide MLD proxy functions. In this scenario, Mobile Nodes remain
agnostic of multicast mobility operations. A support for mobile agnostic of multicast mobility operations. A support for mobile
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 28, 2011. This Internet-Draft will expire on July 2, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 3, line 22 skipping to change at page 3, line 22
responsible for managing IP mobility on behalf of the mobile node responsible for managing IP mobility on behalf of the mobile node
(MN). (MN).
With these entities in place, the mobile node experiences an With these entities in place, the mobile node experiences an
exceptional access topology towards the static Internet in the sense exceptional access topology towards the static Internet in the sense
that the MAG introduces a routing hop also in situations, were the that the MAG introduces a routing hop also in situations, were the
LMA architecturally acts as the next hop (or designated) router for LMA architecturally acts as the next hop (or designated) router for
the MN. In the particular case of multicast communication, group the MN. In the particular case of multicast communication, group
membership management as signaled by the Multicast Listener Discovery membership management as signaled by the Multicast Listener Discovery
protocol (MLD) [RFC3810], [RFC2710] requires dedicated treatment at protocol (MLD) [RFC3810], [RFC2710] requires dedicated treatment at
the network side . the network side.
Multicast routing functions need to be placed carefully within the Multicast routing functions need to be placed carefully within the
PMIPv6 domain to augment unicast transmission with group PMIPv6 domain to augment unicast transmission with group
communication services. [RFC5213] does not explicitly address communication services. [RFC5213] does not explicitly address
multicast communication. Bi-directional home tunneling, the minimal multicast communication. Bi-directional home tunneling, the minimal
multicast support arranged by MIPv6, cannot be directly transferred multicast support arranged by MIPv6, cannot be directly transferred
to network-based management scenarios, since a mobility-unaware node to network-based management scenarios, since a mobility-unaware node
will not initiate such a tunnel after movement. Consequently, even a will not initiate such a tunnel after movement. Consequently, even a
minimal multicast listener support in PMIPv6 domains requires an minimal multicast listener support in PMIPv6 domains requires an
explicit deployment of additional functions. explicit deployment of additional functions.
skipping to change at page 9, line 42 skipping to change at page 9, line 42
membership database and this will trigger corresponding Reports membership database and this will trigger corresponding Reports
towards the LMA. Note that the actual observable state depends on towards the LMA. Note that the actual observable state depends on
the access link model in use. the access link model in use.
An MN may be unable to answer MAG multicast membership queries due to An MN may be unable to answer MAG multicast membership queries due to
handover procedures, or its report may arrive before the MAG has handover procedures, or its report may arrive before the MAG has
configured its link as proxy downstream interface. Such occurrences configured its link as proxy downstream interface. Such occurrences
are equivalent to a General Query loss. To prevent erroneous query are equivalent to a General Query loss. To prevent erroneous query
timeouts at the MAG, MLD parameters SHOULD be carefully adjusted to timeouts at the MAG, MLD parameters SHOULD be carefully adjusted to
the mobility regime. In particular, MLD timers and the Robustness the mobility regime. In particular, MLD timers and the Robustness
Variable (see section 9 of [RFC3810]) MUST be chosen to be compliant Variable (see section 9 of [RFC3810]) SHOULD be chosen to be
with the time scale of handover operations and proxy configurations compliant with the time scale of handover operations and proxy
in the PMIPv6 domain. configurations in the PMIPv6 domain.
In proceeding this way, the MAG is able to aggregate multicast In proceeding this way, the MAG is able to aggregate multicast
subscriptions for each of its MLD proxy instances. However, this subscriptions for each of its MLD proxy instances. However, this
deployment approach does not prevent multiple identical streams deployment approach does not prevent multiple identical streams
arriving from different LMA upstream interfaces. Furthermore, a arriving from different LMA upstream interfaces. Furthermore, a
multipoint channel forwarding into the wireless domain is prevented multipoint channel forwarding into the wireless domain is prevented
by the point-to-point link model in use. by the point-to-point link model in use.
4.3. Operations of the Local Mobility Anchor 4.3. Operations of the Local Mobility Anchor
 End of changes. 6 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/