netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fx.lebail@yahoo.com
Cc: 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 15:52:03 -0500 (EST)	[thread overview]
Message-ID: <20140107.155203.1722933383519867782.davem@davemloft.net> (raw)
In-Reply-To: <1389103047-3380-1-git-send-email-fx.lebail@yahoo.com>

From: Francois-Xavier Le Bail <fx.lebail@yahoo.com>
Date: Tue,  7 Jan 2014 14:57:27 +0100

> This change allows to follow a recommandation of RFC4942.
> 
> - Add "anycast_src_echo_reply" sysctl to control the use of anycast addresses
>   as source addresses for ICMPv6 echo reply. This sysctl is false by default
>   to preserve existing behavior.
> - Add inline check ipv6_anycast_destination().
> - Use them in icmpv6_echo_reply().
> 
> Reference:
> RFC4942 - IPv6 Transition/Coexistence Security Considerations
>    (http://tools.ietf.org/html/rfc4942#section-2.1.6)
> 
> 2.1.6. Anycast Traffic Identification and Security
> 
>    [...]
>    To avoid exposing knowledge about the internal structure of the
>    network, it is recommended that anycast servers now take advantage of
>    the ability to return responses with the anycast address as the
>    source address if possible.
> 
> Signed-off-by: Francois-Xavier Le Bail <fx.lebail@yahoo.com>

Looks good, applied, thanks.

  parent reply	other threads:[~2014-01-07 20:52 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 [this message]
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
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.155203.1722933383519867782.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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).