RFC 4286: Multicast Router Discovery
In plain English — editorial summary, not part of the RFC
The concept of Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) snooping requires the ability to identify the location of multicast routers. Since snooping is not standardized, there are many mechanisms in use to identify the multicast routers. However, this can lead to interoperability issues between multicast routers and snooping switches from different vendors. This document introduces a general mechanism that allows for the discovery of multicast routers. This new mechanism, Multicast Router Discovery (MRD), introduces a standardized means of identifying multicast routers without a dependency on particular multicast routing protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4286
- Published
- December 2005
- Authors
- B. Haberman; J. Martin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3810Multicast Listener Discovery Version 2 (MLDv2) for IPv6Obsoleted
June 2004
- RFC 5519Multicast Group Membership Discovery MIBCurrent
April 2009
- RFC 7028Multicast Mobility Routing Optimizations for Proxy Mobile IPv6Current
September 2013
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 2933Internet Group Management Protocol MIBObsoleted
October 2000
- RFC 5790Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) ProtocolsCurrent
February 2010
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?