From: Christoph Paasch <christoph.paasch@uclouvain.be>
To: David Miller <davem@davemloft.net>
Cc: hannes@stressinduktion.org, fx.lebail@yahoo.com,
netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next v2] IPv6: enable bind() to assign an anycast address
Date: Mon, 17 Feb 2014 10:32:31 +0100 [thread overview]
Message-ID: <20140217093231.GA4609@cpaasch-mac> (raw)
In-Reply-To: <20140217.001545.981758741332832466.davem@davemloft.net>
On 17/02/14 - 00:15:45, David Miller wrote:
> From: Hannes Frederic Sowa <hannes@stressinduktion.org>
> Date: Thu, 13 Feb 2014 01:16:24 +0100
>
> > [added Cc list from old thread]
> >
> > On Wed, Feb 12, 2014 at 02:38:51PM +0100, Francois-Xavier Le Bail wrote:
> >> - Use ipv6_chk_acast_addr_src() in inet6_bind().
> >>
> >> Signed-off-by: Francois-Xavier Le Bail <fx.lebail@yahoo.com>
> >
> > I would agree with the change but would like to see some people from the old
> > thread about this change to agree with it, too.
>
> I hear crickets... instead of other reviews :-)
I don't have strong opinions for or against this patch.
I was only involved in the original thread because F-X claimed that
draft-iab-anycast-arch-implications (now RFC 7094) allows the use of anycast
addresses for TCP, which is not what RFC 7094 is saying. There is no
recommendation concerning TCP in the RFC and the situation is rather unclear.
Cheers,
Christoph
next prev parent reply other threads:[~2014-02-17 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 13:38 [PATCH net-next v2] IPv6: enable bind() to assign an anycast address Francois-Xavier Le Bail
2014-02-13 0:16 ` Hannes Frederic Sowa
2014-02-17 5:15 ` David Miller
2014-02-17 9:32 ` Christoph Paasch [this message]
2014-02-17 10:02 ` Alexey Kuznetsov
2014-02-17 19:19 ` David Miller
2014-02-17 19:25 ` Hannes Frederic Sowa
2014-02-17 19:42 ` François-Xavier Le Bail
2014-02-17 19:48 ` David Miller
2014-02-17 19:52 ` François-Xavier Le Bail
-- strict thread matches above, loose matches on Subject: below --
2014-01-13 16:59 Francois-Xavier Le Bail
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=20140217093231.GA4609@cpaasch-mac \
--to=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fx.lebail@yahoo.com \
--cc=hannes@stressinduktion.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.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).