From: Juliusz Chroboczek <jch@irif.fr>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: The case for anycast (contra move semantics for unicast AllowedIPs).
Date: Fri, 20 Apr 2018 11:48:22 +0200 [thread overview]
Message-ID: <87y3hinr89.wl-jch@irif.fr> (raw)
In-Reply-To: <87wox2xlp1.fsf@toke.dk>
>> 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?
prev parent reply other threads:[~2018-04-20 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 19:44 The case for anycast (contra move semantics for unicast AllowedIPs) George Walker
2018-04-20 9:37 ` Toke Høiland-Jørgensen
2018-04-20 9:48 ` Juliusz Chroboczek [this message]
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=87y3hinr89.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=toke@toke.dk \
--cc=wireguard@lists.zx2c4.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.