From: David Miller <davem@davemloft.net>
To: billfink@mindspring.com
Cc: fx.lebail@yahoo.com, netdev@vger.kernel.org,
hannes@stressinduktion.org, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net
Subject: Re: [PATCH net-next v5] IPv6: add the option to use anycast addresses as source addresses in echo reply
Date: Tue, 07 Jan 2014 18:33:05 -0500 (EST) [thread overview]
Message-ID: <20140107.183305.1907441201345858474.davem@davemloft.net> (raw)
In-Reply-To: <20140107175507.fb543c70.billfink@mindspring.com>
From: Bill Fink <billfink@mindspring.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.
next prev parent reply other threads:[~2014-01-07 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 13:57 [PATCH net-next v5] IPv6: add the option to use anycast addresses as source addresses in echo reply Francois-Xavier Le Bail
2014-01-07 19:14 ` Hannes Frederic Sowa
2014-01-08 8:06 ` François-Xavier Le Bail
2014-01-07 20:51 ` Hannes Frederic Sowa
2014-01-08 8:17 ` François-Xavier Le Bail
2014-01-08 8:22 ` Hannes Frederic Sowa
2014-01-07 20:52 ` David Miller
2014-01-07 22:55 ` Bill Fink
2014-01-07 23:01 ` Hannes Frederic Sowa
2014-01-07 23:17 ` Hannes Frederic Sowa
2014-01-08 9:56 ` François-Xavier Le Bail
2014-01-07 23:33 ` David Miller [this message]
2014-01-07 23:39 ` Hannes Frederic Sowa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140107.183305.1907441201345858474.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=billfink@mindspring.com \
--cc=fx.lebail@yahoo.com \
--cc=hannes@stressinduktion.org \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).