Hi Chad,
On 10-12-17 03:02 PM, Chad Kissinger wrote:
Hello,
We are deploying IPV6 to our customers and are carefully planning the
architecture of how we are going to deploy prefixes, assign customer
gateways and how we are going to number our own infrastructure in a
meaningful way. Although I think Stateless Autoconfiguration will be
used quite a deal for nodes that are “clients”, most of my customers
have large server farms and our infrastructure, of course, has many
routers. I would think it would be preferable to be able to either use
a DHCPV6 pool or to use manual configuration so that the resulting
Interface Identifier is either bounded within a known range (tighter
than 64 bits wide) or is a specific predictable address (like ::ABC/128
for all customer Gateways, etc.) or to have patterns like :AAAA: within
an Identifier for all Edge Routers for easier “on sight” identification
by SysAdmins…
However, after many days of reading, I cannot find any place that
specifically details the method one would use to identify suitable
ranges to choose from for a manually configured Interface ID or a pool
of such IDs. Is it as simple as setting the 71^st and 72^nd bit and
avoiding Anycast addresses?
RFC 5453 seems to be written to address this, but seems to have all the
relevant detail missing…
The goal of RFC5453 was to list the addresses not suitable for stateless
auto-configuration, and not exactly to list those that are suitable for
manual configuration. I think you have the right idea though. As long as
the bits 6 and 7 (counting from 0) of the interface identifier are set
to 0 in your manually configured address, you should have no issues.
Cheers
Suresh
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
