Frequently asked questions and references

The prefix remains part of its holder's PI allocation. The holder has deliberately removed this /48 from production use, applied routing controls, and publicly documented an internal-use convention. No ownership or exclusive right is transferred to users.

ULA is the conventional and standards-defined answer. The alternative exists for deployments that specifically want ordinary GUA classification and source-selection semantics internally without host-policy changes.

A random selection may hide a legitimate routed destination from the local network. This /48 has a documented non-production intent and routing posture under the current holder's control.

Technically, yes: no registration or exclusive subdivision mechanism exists. Operationally, most networks should select only the internal blocks they require and build a deliberate hierarchy.

The model does not impose a technical distinction between personal and commercial networks. Voluntary support is encouraged when the project provides material value, but support does not create exclusivity, service obligations, or warranties.

No. Public advertisement is contrary to the documented purpose and may conflict with routing policy, registry agreements, and the safeguards applied to the prefix. Adopting networks should filter it explicitly.

They may overlap. Plan as you would with any shared internal address convention: reserve structure early and expect renumbering, translation, or segmentation when separately administered networks merge.

There is no perpetual guarantee. The page describing project status and caveats should be part of every adopter's risk assessment.