RFC 3180: GLOP Addressing in 233/8
In plain English — editorial summary, not part of the RFC
This document defines the policy for the use of 233/8 for statically e assigned multicast addresses. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3180
- Published
- September 2001
- Authors
- D. Meyer; P. Lothberg
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- BCP53
- Obsoletes:
- RFC 2770
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5790Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) ProtocolsCurrent
February 2010
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- RFC 8487Mtrace Version 2: Traceroute Facility for IP MulticastCurrent
October 2018
- RFC 8777DNS Reverse IP Automatic Multicast Tunneling (AMT) DiscoveryCurrent
April 2020
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
- RFC 9119Multicast Considerations over IEEE 802 Wireless MediaCurrent
October 2021
- RFC 9630Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM)Current
August 2024
- RFC 9706TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass AudiencesCurrent
January 2025
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?