RFC 6224: Base Deployment for Multicast Listener Support in Proxy Mobile IPv6 (PMIPv6) Domains
In plain English — editorial summary, not part of the RFC
This document describes deployment options for activating multicast listener functions in Proxy Mobile IPv6 domains without modifying mobility and multicast protocol standards. Similar to home agents in Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as multicast subscription anchor points, while Mobile Access Gateways provide Multicast Listener Discovery (MLD) proxy functions. In this scenario, mobile nodes remain agnostic of multicast mobility operations. Support for mobile multicast senders is outside the scope of this document. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6224
- Published
- April 2011
- Authors
- T. Schmidt; M. Waehlisch; S. Krishnan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5213Proxy Mobile IPv6Updated
August 2008
- RFC 5796Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local MessagesCurrent
March 2010
- RFC 5060Protocol Independent Multicast MIBCurrent
January 2008
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 9398A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxy DevicesCurrent
May 2023
- RFC 6221Lightweight DHCPv6 Relay AgentCurrent
May 2011
- RFC 6245Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4Current
May 2011
- RFC 6195Domain Name System (DNS) IANA ConsiderationsObsoleted
March 2011
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?