RFC 5186: Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction
In plain English — editorial summary, not part of the RFC
The definitions of the Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) require new behavior within the multicast routing protocols. The additional source information contained in IGMPv3 and MLDv2 messages necessitates that multicast routing protocols manage and utilize the information. This document describes how multicast routing protocols will interact with these source-filtering group management protocols. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5186
- Published
- May 2008
- Authors
- B. Haberman; J. Martin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5191Protocol for Carrying Authentication for Network Access (PANA)Updated
May 2008
- RFC 5192DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication AgentsCurrent
May 2008
- RFC 5193Protocol for Carrying Authentication for Network Access (PANA) FrameworkCurrent
May 2008
- RFC 5177Network Mobility (NEMO) Extensions for Mobile IPv4Updated
April 2008
- RFC 5175IPv6 Router Advertisement Flags OptionCurrent
March 2008
- RFC 5172Negotiation for IPv6 Datagram Compression Using IPv6 Control ProtocolCurrent
March 2008
- RFC 5201Host Identity ProtocolObsoleted
April 2008
- RFC 5202Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)Obsoleted
April 2008
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?