From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Dave Täht" <dave@taht.net>, "Juliusz Chroboczek" <jch@irif.fr>,
"WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: Re: [RFC] Multicast and IPv6 Link Local Addresses
Date: Sat, 08 Apr 2017 14:43:56 +0200 [thread overview]
Message-ID: <87wpavt6gj.fsf@alrua-karlstad> (raw)
In-Reply-To: <CAHmME9oxt=x3tJ5wHitGGjD1yLGweQ4ed3aNv+0Cv9bvPUXDDg@mail.gmail.com> (Jason A. Donenfeld's message of "Fri, 7 Apr 2017 22:42:22 +0200")
"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> Hey George,
>
> More excellent feedback, thanks. Be sure to CC the list next time though.
>
> If I understand correctly, your suggestion is to not clutter
> everything with a horrible "multi:" prefix, but instead allow
> multicast addressees, which are well defined, to be added to multiple
> peers, and only allow unicast addresses to be added to one peer at a
> time keeping the current behavior. I find that a very nice UI
> solution. Wonderful.
I'd be fine with this, as long as it's on the subnet level (which I
believe is the case, just making sure). I.e., if I want behaviour
corresponding to full link-local multicast, I can just add fe02::/16 to
every peer in my config and be done with it.
-Toke
next prev parent reply other threads:[~2017-04-08 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 14:02 Jason A. Donenfeld
2017-04-07 14:31 ` Jason A. Donenfeld
[not found] ` <03B23E99-75C4-4598-AC0A-3C65F346675F@gmail.com>
2017-04-07 20:42 ` Jason A. Donenfeld
2017-04-08 12:43 ` Toke Høiland-Jørgensen [this message]
2017-04-08 15:44 ` George Walker
2017-04-08 9:39 ` Dan Lüdtke
2017-04-08 17:15 ` Juliusz Chroboczek
2017-04-08 19:05 ` Juliusz Chroboczek
2017-04-17 14:11 ` Baptiste Jonglez
2017-04-17 16:55 ` Toke Høiland-Jørgensen
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=87wpavt6gj.fsf@alrua-karlstad \
--to=toke@toke.dk \
--cc=Jason@zx2c4.com \
--cc=dave@taht.net \
--cc=jch@irif.fr \
--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 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).