RFC 3590: Source Address Selection for the Multicast Listener Discovery (MLD) Protocol
In plain English — editorial summary, not part of the RFC
It has come to light that there is an issue with the selection of a suitable IPv6 source address for Multicast Listener Discovery (MLD) messages when a node is performing stateless address autoconfiguration. This document is intended to clarify the rules on selecting an IPv6 address to use for MLD messages. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3590
- Published
- September 2003
- Authors
- B. Haberman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 2710
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2711IPv6 Router Alert OptionUpdated
October 1999
- RFC 3596DNS Extensions to Support IP Version 6Current
October 2003
- RFC 3543Registration Revocation in Mobile IPv4Current
August 2003
- RFC 3531A Flexible Method for Managing the Assignment of Bits of an IPv6 Address BlockCurrent
April 2003
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 3678Socket Interface Extensions for Multicast Source FiltersCurrent
January 2004
- RFC 3697IPv6 Flow Label SpecificationObsoleted
March 2004
- RFC 3775Mobility Support in IPv6Obsoleted
June 2004
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?