[188060] in North American Network Operators' Group
Re: IPV6 planning
daemon@ATHENA.MIT.EDU (Baldur Norddahl)
Mon Mar 7 23:23:05 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <20160308000126.GF5234@drscott.swordarmor.fr>
Date: Tue, 8 Mar 2016 05:23:01 +0100
From: Baldur Norddahl <baldur.norddahl@gmail.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On 8 March 2016 at 01:01, Alarig Le Lay <alarig@swordarmor.fr> wrote:
> It=E2=80=99s not exactly specific to Windows, dhcpcd use a something like=
that
> (my IPv6 is 2a00:5884:8316:2653:fd40:d47d:556f:c426). And at least,
> there is a RFC related to that, https://tools.ietf.org/html/rfc7217.
>
It appears that RFC 7217 does not actually demand a 64 bit interface
identifier. One could therefore do a non-64 bit RFC 7217 SLAAC on operating
systems that support that.
"We note that [RFC4291] requires that the Interface IDs of all
unicast addresses (except those that start with the binary
value 000) be 64 bits long. However, the method discussed in
this document could be employed for generating Interface IDs
of any arbitrary length, albeit at the expense of reduced
entropy (when employing Interface IDs smaller than 64 bits)."
Regards,
Baldur
