Folks, MLD also requires link-local IPv6 source addresses, RFC 3810, Sec. 5:
All MLDv2 messages described in this document MUST be sent with a link-local IPv6 Source Address, an IPv6 Hop Limit of 1, and an IPv6 Router Alert option [RFC2711] in a Hop-by-Hop Options header.. So no escape from the link-locals. Regards, Behcet ----- Original Message ---- From: Hemant Singh (shemant) <shem...@cisco.com> To: Erik Nordmark <erik.nordm...@sun.com>; Prabhu Hariharan <prab...@gmail.com> Cc: ipv6@ietf.org Sent: Wednesday, June 10, 2009 9:14:53 PM Subject: RE: Is Link-Local address mandatory for a host device? Erik Nordmark wrote: >I suspect that you also can't use DHCPv6 for non-addresses (finding the >DNS servers etc) since DHCPv6 might assume that some communication uses >the link-local address. But I haven't checked in the RFC. Snipped from RFC 3315, section 1.1 is: [Clients and servers exchange DHCP messages using UDP [15]. The client uses a link-local address or addresses determined through other mechanisms for transmitting and receiving DHCP messages.] Using link-local for DHCPv6 has the advantage that well-known mcast addresses can be used for clients to communicate with the server or relay agents. RFC 3315 also mentions such an advantage in section 3. Of course, even IPv6 mcast uses link-local address. So really, it is not wise for a host to not use a link-local address at all. Hemant -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
