RFC 7028: Multicast Mobility Routing Optimizations for Proxy Mobile IPv6
In plain English — editorial summary, not part of the RFC
This document proposes some experimental enhancements to the base solution to support IP multicasting in a Proxy Mobile IPv6 (PMIPv6) domain. These enhancements include the use of a multicast tree mobility anchor as the topological anchor point for multicast traffic, as well as a direct routing option where the Mobile Access Gateway can provide access to multicast content in the local network. The goal of these enhancements is to provide benefits such as reducing multicast traffic replication and supporting different PMIPv6 deployment scenarios.
Document record
- Document ID
- RFC7028
- Published
- September 2013
- Authors
- JC. Zuniga; LM. Contreras; CJ. Bernardos; S. Jeon; Y. Kim
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 4286Multicast Router DiscoveryCurrent
December 2005
- RFC 3810Multicast Listener Discovery Version 2 (MLDv2) for IPv6Obsoleted
June 2004
- RFC 5790Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) ProtocolsCurrent
February 2010
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 8652A YANG Data Model for the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)Current
November 2019
- RFC 7148Prefix Delegation Support for Proxy Mobile IPv6Current
March 2014
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?