RFC 4608: Source-Specific Protocol Independent Multicast in 232/8
In plain English — editorial summary, not part of the RFC
IP Multicast group addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are designated as source-specific multicast destination addresses and are reserved for use by source-specific multicast applications and protocols. This document defines operational recommendations to ensure source-specific behavior within the 232/8 range. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4608
- Published
- August 2006
- Authors
- D. Meyer; R. Rockell; G. Shepherd
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- BCP120
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4570Session Description Protocol (SDP) Source FiltersCurrent
July 2006
- RFC 4609Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and EnhancementsCurrent
October 2006
- RFC 6308Overview of the Internet Multicast Addressing ArchitectureCurrent
June 2011
- RFC 27726Bone Backbone Routing GuidelinesUpdated
February 2000
- RFC 6450Multicast Ping ProtocolCurrent
December 2011
- RFC 6673Round-Trip Packet Loss MetricsCurrent
August 2012
- RFC 7450Automatic Multicast TunnelingUpdated
February 2015
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
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?