From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: jch@irif.fr
Received: from krantz.zx2c4.com (localhost [127.0.0.1])
 by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 2d0edc8d
 for <wireguard@lists.zx2c4.com>;
 Fri, 20 Apr 2018 09:48:15 +0000 (UTC)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [194.254.61.138])
 by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id e39d0b27
 for <wireguard@lists.zx2c4.com>;
 Fri, 20 Apr 2018 09:48:14 +0000 (UTC)
Date: Fri, 20 Apr 2018 11:48:22 +0200
Message-ID: <87y3hinr89.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= <toke@toke.dk>
Subject: Re: The case for anycast (contra move semantics for unicast
 AllowedIPs).
In-Reply-To: <87wox2xlp1.fsf@toke.dk>
References: <CAC92Z13zi6Gsq2CGwohZSEcF04Sa+m+WO3yCzWjXvn4DZuy-Rg@mail.gmail.com>
 <87wox2xlp1.fsf@toke.dk>
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
List-Id: Development discussion of WireGuard <wireguard.lists.zx2c4.com>
List-Unsubscribe: <https://lists.zx2c4.com/mailman/options/wireguard>,
 <mailto:wireguard-request@lists.zx2c4.com?subject=unsubscribe>
List-Archive: <http://lists.zx2c4.com/pipermail/wireguard/>
List-Post: <mailto:wireguard@lists.zx2c4.com>
List-Help: <mailto:wireguard-request@lists.zx2c4.com?subject=help>
List-Subscribe: <https://lists.zx2c4.com/mailman/listinfo/wireguard>,
 <mailto:wireguard-request@lists.zx2c4.com?subject=subscribe>

>> Recently, I've been mulling over move semantics and their
>> implication for WireGuard's support for anycast addressing.

Perhaps you could explain the purpose of having anycast support in a VPN
implementation?