New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request support Semantically Opaque Interface Identifiers with IPv6 (SLAAC) RFC 7217 #4625

Open
cvmiller opened this Issue Nov 8, 2016 · 1 comment

Comments

3 participants
@cvmiller

cvmiller commented Nov 8, 2016

Submission type

  • Bug report
  • Request for enhancement (RFE)

NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!

systemd version the issue has been seen with

systemd 231
+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!

Used distribution

Arch Linux

In case of bug report: Expected behaviour you didn't see

In case of bug report: Unexpected behaviour you saw

In case of bug report: Steps to reproduce the problem

Additional Information

RFC 4862 defines how to create an GUA (Global Unique Address) via SLAAC. But a GUA based on MAC address (EUI64) has limitations as referenced in RFC 7707, and a new unguessable method has been created via RFC 7217. iOS 10, and Mac OSX 10.12 support RFC 7217.

@madman2003

This comment has been minimized.

Show comment
Hide comment
@madman2003

madman2003 Feb 25, 2017

I recently started using IPV6, and i'm wondering why the EUI64 addresses are still used by networkd, when RFC7217 has been around for years. Is this very complicated to implement? Has anyone tried?

madman2003 commented Feb 25, 2017

I recently started using IPV6, and i'm wondering why the EUI64 addresses are still used by networkd, when RFC7217 has been around for years. Is this very complicated to implement? Has anyone tried?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment