RFC 3678: Socket Interface Extensions for Multicast Source Filters
In plain English — editorial summary, not part of the RFC
The Internet Group Management Protocol (IGMPv3) for IPv4 and the Multicast Listener Discovery (MLDv2) for IPv6 add the capability for applications to express source filters on multicast group memberships, which allows receiver applications to determine the set of senders (sources) from which to accept multicast traffic. This capability also simplifies support of one-to-many type multicast applications. This document specifies new socket options and functions to manage source filters for IP Multicast group memberships. It also defines the socket structures to provide input and output arguments to these new application program interfaces (APIs). These extensions are designed to provide access to the source filtering features, while introducing a minimum of change into the system and providing complete compatibility for existing multicast applications.
Document record
- Document ID
- RFC3678
- Published
- January 2004
- Authors
- D. Thaler; B. Fenner; B. Quinn
- Status
- INFORMATIONAL
- 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 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 2728The Transmission of IP Over the Vertical Blanking Interval of a Television SignalCurrent
November 1999
- RFC 2685Virtual Private Networks IdentifierCurrent
September 1999
- RFC 2625IP and ARP over Fibre ChannelObsoleted
June 1999
- RFC 2529Transmission of IPv6 over IPv4 Domains without Explicit TunnelsCurrent
March 1999
- RFC 2507IP Header CompressionCurrent
February 1999
- RFC 2337Intra-LIS IP multicast among routers over ATM using Sparse Mode PIMCurrent
April 1998
- RFC 2333NHRP Protocol Applicability StatementCurrent
April 1998
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?