From: Aaron Jones <aaronmdjones@gmail.com>
To: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Standardized IPv6 ULA from PublicKey
Date: Mon, 4 Dec 2017 17:14:23 +0000 [thread overview]
Message-ID: <191f960d-1375-10c6-b97f-beedda2b33be@gmail.com> (raw)
In-Reply-To: <372AE79B-69E5-4B18-926C-E402FDFB2E95@lonnie.abelbeck.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 04/12/17 16:52, Lonnie Abelbeck wrote:
> Hi,
>
> Has anyone thought about a standardized WireGuard IPv6 ULA
> generated from the PublicKey ?
>
> WireGuard Unique Identifier (WUI) allowing a host to assign iteslf
> a unique 64-Bit IPv6 interface identifier (WUI-64) ?
>
> Possibly picking off bits of a hash of the PublicKey ?
>
> For mass deployments, could this be a useful standard ?
Mass deployments are likely to use some form of centralised and
automated configuration management/provisioning solution already,
which can take care of performing the calculations and assignments you
are suggesting.
Regards,
Aaron Jones
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJaJYJsAAoJEIrwc3SIqzASaAYP/RJMae43IXsvgtJd33/awnPD
Aam6tUWHgISo2SeM3syrXNr1kIpTTca4PwyLfm5w8sxy/Zw0RF0Ux1lx3PH9NAd4
OT0f+UR9jpzLmncUS1t3I5z2g398kWr3Z5Fud1y8kvWgjbhp1dAjRv1FOwzXeQqM
Zfk9it3qBVNpu3bzuXwNimT13Z3uYXh6BCyI++gyui9glq2eOUoGRQv5Rw1pXnkY
2VthV9pnJVjn5crvSyNw5Y0SZisE5BnDxVvy72sXTO//Hx6Gg7bnPYt/2mNOQTNG
KUL2r7XJ4zm2IdqohOfSmjvCnlkh1KEg9ZPbrrrzSammwPVuMxCxKcy6GG+ETGSn
yGj4gIYAW1x3HjbhG+1j0jTAh3jelayp4iHMf0gaFo2KY8jxbzXnBRAFiGGKJxIk
mdIBI64Nog9lIm/hI3wNxkFGKfqMqDP9qVG3jPj2b4ACFLvsy4B8rySc2PjZIaKv
D+MfSeiB8culswELDgIZH1U4SRks6Kec5qV81wkP/1t1g2t9zspc3rnBahGvMhgs
lNWLfeFADe5bR7wqeBDzx52XvhvrGWqRD/eJney7THLQj05CVTB0cikPJ25AFnNA
FfzThVEDIsGrGbzSMAq82Brj6bAs81F8Vz/Lnrmba8ejLsI0QsOjNfncEzte1VBz
4cbh8sSBh+udO4cItEM3
=Nvi/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-12-04 17:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 16:52 Standardized IPv6 ULA from PublicKey Lonnie Abelbeck
2017-12-04 17:14 ` Aaron Jones [this message]
2017-12-05 2:53 ` Luis Ressel
2017-12-05 3:31 ` Jason A. Donenfeld
2020-06-24 15:37 ` Florian Klink
2020-06-24 17:08 ` Chriztoffer Hansen
2020-06-24 17:30 ` JuniorJPDJ
2020-06-27 21:43 ` Reid Rankin
2020-06-28 10:15 ` Arti Zirk
2020-06-28 15:19 ` Derrick Lyndon Pallas
2020-06-29 10:22 ` Toke Høiland-Jørgensen
2020-06-29 10:31 ` Roman Mamedov
2020-06-29 10:52 ` Justin Kilpatrick
2020-06-29 11:03 ` Toke Høiland-Jørgensen
2020-06-29 11:38 ` Roman Mamedov
2020-06-29 12:15 ` Toke Høiland-Jørgensen
2020-06-29 17:01 ` Arti Zirk
2020-06-29 18:01 ` Jason A. Donenfeld
2020-06-29 19:58 ` Reid Rankin
2020-06-30 1:24 ` Jason A. Donenfeld
2020-06-30 8:01 ` Reid Rankin
2020-06-29 18:49 ` Luiz Angelo Daros de Luca
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=191f960d-1375-10c6-b97f-beedda2b33be@gmail.com \
--to=aaronmdjones@gmail.com \
--cc=lists@lonnie.abelbeck.com \
--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.