Parent folderOpen Confluence

RWS Architecture article

Logius overheidsbreed IPv6-nummerplankader (Summary)

Summary of the Dutch government-wide IPv6 numbering framework managed by Logius for allocation, categorization, and governance of government IPv6 address space.

  1. Typesource
  2. Statusactive
  3. Domainnetwork
On this page
  1. Source - Logius overheidsbreed IPv6-nummerplankader
  2. Overview
  3. Context
  4. Decisions
  5. Current State
  6. References
  7. Future Work
  8. Related

Source - Logius overheidsbreed IPv6-nummerplankader

Overview

Summary of the Dutch government-wide IPv6 numbering framework managed by Logius for allocation, categorization, and governance of government IPv6 address space.

Context

This source is used to align network architecture with Dutch public-sector IPv6 policy, especially for category-based usage on internet and inter-government networks and for long-term address planning.

Decisions

  • Architecture usage in this vault: informs category-aligned IPv6 planning in adr-023-ipv6-numberplan-and-cluster-scale-strategy.
  • Architecture usage in this vault: informs category semantics (NC1, NC2, NC3, NC5) in addressing guardrails and review evidence.
  • Architecture usage in this vault: informs RPKI and reverse-DNS evidence checks for internet-facing allocations.
  • Policy adoption remains owned by ADR and architecture notes, not by this source summary.

Current State

  • Logius manages government allocations from two RIPE-registered prefixes: 2a04:9a00::/29 and 2a07:3500::/29.
  • On common government interconnects, category usage is required with explicit mandatory mappings for internet (NC1) and Diginetwerk (NC2).
  • NC3 is reserved for other shared government-network scenarios under additional agreements.
  • NC5 is intended for internal use and is recommended for internal implementation patterns.
  • In this vault, NC mapping statements are interpreted from the framework category model text and should be rechecked against the source page during policy-promotion reviews.
  • Standard issuance model gives organizations category-specific ranges (typically /46 blocks) with internet publication via /48 assignment and staged expansion.
  • The framework recommends use of global unicast addressing for external and internal planning to avoid future conflicts.
  • RPKI usage is mandatory in Dutch government policy context for internet-routed prefixes; ROA handling is coordinated through Logius as LIR for the government blocks.
  • Reverse DNS delegation is expected for operationally managed IPv6 ranges.

References

Future Work

  • Pin release-governed implementation profiles for cluster and tenant addressing against this source in architecture ADRs.
  • Add explicit control checks for NC usage, RPKI ROA state, and reverse-DNS delegation in evidence bundles.

Related