netdev - Re: [PATCH net-next v2] IPv6: enable bind() to assign an anycast address

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140217093231.GA4609@cpaasch-mac>
Date:	Mon, 17 Feb 2014 10:32:31 +0100
From:	Christoph Paasch <christoph.paasch@...ouvain.be>
To:	David Miller <davem@...emloft.net>
Cc:	hannes@...essinduktion.org, fx.lebail@...oo.com,
	netdev@...r.kernel.org, kuznet@....inr.ac.ru,
	eric.dumazet@...il.com
Subject: Re: [PATCH net-next v2] IPv6: enable bind() to assign an anycast
 address

On 17/02/14 - 00:15:45, David Miller wrote:
> From: Hannes Frederic Sowa <hannes@...essinduktion.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@...oo.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

--
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