RFC 4489: A Method for Generating Link-Scoped IPv6 Multicast Addresses
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the multicast addressing architecture of the IPv6 protocol. The extension allows the use of Interface Identifiers (IIDs) to allocate multicast addresses. When a link-local unicast address is configured at each interface of a node, an IID is uniquely determined. After that, each node can generate its unique multicast addresses automatically without conflicts. The alternative method for creating link-local multicast addresses proposed in this document is better than known methods like unicast-prefix-based IPv6 multicast addresses. This memo updates RFC 3306. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4489
- Published
- April 2006
- Authors
- J-S. Park; M-K. Shin; H-J. Kim
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 3306
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4487Mobile IPv6 and Firewalls: Problem StatementCurrent
May 2006
- RFC 4477Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack IssuesCurrent
May 2006
- RFC 4471Derivation of DNS Name Predecessor and SuccessorCurrent
September 2006
- RFC 4470Minimally Covering NSEC Records and DNSSEC On-line SigningCurrent
April 2006
- RFC 4509Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)Current
May 2006
- RFC 4449Securing Mobile IPv6 Route Optimization Using a Static Shared KeyCurrent
June 2006
- RFC 4443Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationUpdated
March 2006
- RFC 4541Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping SwitchesCurrent
May 2006
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?