RFC 10028: Updates to Dynamic IPv6 Multicast Address Group IDs
In plain English — editorial summary, not part of the RFC
This document describes limitations of the existing range of dynamic IPv6 multicast addresses specified in "Allocation Guidelines for IPv6 Multicast Addresses" (RFC 3307). It updates RFC 3307 by replacing these allocations with a new IANA registry in the "IPv6 Multicast Address Space" registry group. The document also defines initial contents of the new registry: a reduced allocation for the Multicast Address Dynamic Client Allocation Protocol (MADCAP) (RFC 2730), a range for Source-Specific Multicast (SSM), a Private Use range, a range for Experimental Use, and Solicited-Node multicast addresses (which were not previously noted in RFC 3307).
Document record
- Document ID
- RFC10028
- Published
- August 2026
- Authors
- N. Karstens; D. Farinacci; M. McBride
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 3307
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9730Interworking of GMPLS Control and Centralized Controller SystemsCurrent
March 2025
- RFC 9299An Architectural Introduction to the Locator/ID Separation Protocol (LISP)Current
October 2022
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 2102Multicast Support for Nimrod : Requirements and Solution ApproachesCurrent
February 1997
- RFC 1665Definitions of Managed Objects for SNA NAUs using SMIv2Obsoleted
July 1994
- RFC 8952Captive Portal ArchitectureCurrent
November 2020
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
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?