10

We started with fec0::/10 for site-local addresses -- but that is now deprecated. Instead, we now have fc00::/7 reserved, with fd00::/8 dedicated to /48 nets for Unique Local Addresses.

What's the best practice for picking the least-sig 40 bits to give you an org-level /48?

...is everyone using the SIXXS voluntary registry? (seems dubious to me)
...just use RFC4193's guidance for picking (via it's algo)?
...anyone have an online implementation of that algo?

Picking our 40 bits doesn't seem hard; I'm just trying to pick them the "right" way, if I can.

10

Its always best to stick to the relevant RFC when possible. In this case, your two options aren't mutually exclusive. SIXXS' generator should actually generate you a prefix based on RFC4193's algorithm.

So you would just generate your prefix using SIXXS' tool (or another one you find), and if you feel like it, register it with SIXXS.

2

The odds of someone picking the same range and then merging or making business with you should be very slim. As you mentioned SIXXS has a registration, not sure how much it is used and since it's really no authority there's no guarantee that someone wouldn't have picked the same range. I guess it's better than nothing though.

These are the tools I could find:

http://www.sixxs.net/tools/grh/ula/
https://www.ultratools.com/tools/rangeGenerator

1

If you do what the RFC says, the chance of an actual collision is very low (even though the birthday paradox applies), and since ULA addresses are only used internally on your own site, a collision doesn't matter in practice unless you merge your network with another one that, amazingly, is using the same ULA prefix.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.