draft-ietf-magma-mld-source-00.txt   draft-ietf-magma-mld-source-01.txt 
MAGMA Working Group B. Haberman MAGMA Working Group B. Haberman
draft-ietf-magma-mld-source-00.txt Consultant draft-ietf-magma-mld-source-01.txt Caspian Networks
Expires March 2003 September 2002 Expires March 2003 September 2002
Source Address Selection for Multicast Source Address Selection for Multicast
Listener Discovery Protocol (RFC 2710) Listener Discovery Protocol (RFC 2710)
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
skipping to change at page 2, line 24 skipping to change at page 2, line 24
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC 2119]. document are to be interpreted as described in [RFC 2119].
MLD Source Address Selection Guidelines MLD Source Address Selection Guidelines
An MLD speaking node is required to choose a suitable IPv6 source An MLD speaking node is required to choose a suitable IPv6 source
address for all MLD messages (Report, Done, and Query). address for all MLD messages (Report, Done, and Query).
MLD Query messages MUST be sent with a valid link-local address as MLD Query messages MUST be sent with a valid link-local address as
the IPv6 source address. If ia router receives a query message with the IPv6 source address. If a router receives a query message with
an IPv6 source address set to the unspecified address (::), it MUST an IPv6 source address set to the unspecified address (::), it MUST
silently discard the message and SHOULD log a warning. silently discard the message and SHOULD log a warning.
MLD Report and Done messages SHOULD be sent with a valid link-local MLD Report and Done messages SHOULD be sent with a valid link-local
address as the IPv6 source address. If a valid link-local address is address as the IPv6 source address. If a valid link-local address is
not available, the Report MAY be sent with the unspecified address not available, the message MAY be sent with the unspecified address
(::) as the IPv6 source address. (::) as the IPv6 source address.
Security Considerations Security Considerations
Security issues related to MLD are discussed in [RFC 2710]. Security issues related to MLD are discussed in [RFC 2710].
References References
[RFC 2710] Deering, S., Fenner, W., Haberman, B., "Multicast Listener [RFC 2710] Deering, S., Fenner, W., Haberman, B., "Multicast Listener
Discovery (MLD) for IPv6", RFC 2710, October 1999. Discovery (MLD) for IPv6", RFC 2710, October 1999.
skipping to change at page 3, line 8 skipping to change at page 3, line 8
[RFC 2462] Thomson, S., Narten, T., "IPv6 Stateless Address [RFC 2462] Thomson, S., Narten, T., "IPv6 Stateless Address
Autoconfiguration", RFC 2462, December 1998. Autoconfiguration", RFC 2462, December 1998.
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
Author's Address Author's Address
Brian Haberman Brian Haberman
Caspian Networks
bkhabs@nc.rr.com bkhabs@nc.rr.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/