[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140107.183305.1907441201345858474.davem@davemloft.net>
Date: Tue, 07 Jan 2014 18:33:05 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: billfink@...dspring.com
Cc: fx.lebail@...oo.com, netdev@...r.kernel.org,
hannes@...essinduktion.org, kuznet@....inr.ac.ru,
jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net
Subject: Re: [PATCH net-next v5] IPv6: add the option to use anycast
addresses as source addresses in echo reply
From: Bill Fink <billfink@...dspring.com>
Date: Tue, 7 Jan 2014 17:55:07 -0500
> Why is ICMPV6 Echo Reply special? Can't the internal structure
> of the network be divined from other ICMPv6 responses such as
> Destination Unreachable, Time Exceeded (Hop Limit), and Parameter
> Problem.
Right, this RFC is talking about source address selection in general,
so this anycast handling should be in a generic place too.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists