--- On Mon, 10/3/11, Thomas Narten <[email protected]> wrote: > <[email protected]> writes: > > > If the source address of reply differs from destination address of > > the request, some applications are broken. > > If you are saying that applications should ignore the src > address (in case it is anycast) when accpting replies, I very > strongly disagree.
I don't say that. > The norm is (and has been forever) to require that the > source address in a response (whether TCP or UDP) match the destination > address in the original query. And for good reason. But the RFC 3484, as I understand it, exclude anycast address from the source replies. Section 4 of RFC 3484 states: (http://tools.ietf.org/html/rfc3484#section-4) 4. Candidate Source Addresses [. . .] In any case, anycast addresses, multicast addresses, and the unspecified address MUST NOT be included in a candidate set. It might be useful to reassess this restriction, at least for the replies. Thanks, François-Xavier -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
