Enterprise deployment planning
Build a phased enterprise IPv6 plan covering inventory, training, address plan, security policy and pilot (RFC 7381). Set measurable success metrics for the rollout. Identify blockers such as legacy applications, vendors and security tooling (RFC 9099).
Take the quiz · pass mark 70% · 9 questions
Explanation
Enterprise IPv6 fails when it is treated as a switch to flip rather than a program to run. RFC 7381 (Enterprise IPv6 Deployment Guidelines) frames it as phases; RFC 9099 adds the operational-security lens.
The phases (RFC 7381)
- Inventory and assessment. What hardware, OS, applications, and security tools are in use, and are they IPv6-capable? This is where most blockers are found.
- Training. The team must understand addressing, SLAAC/DHCPv6, ND and first-hop security (Level 5) before they operate IPv6.
- Address plan. Obtain a /48 (or more) from an RIR or the ISP, then design a hierarchical, aggregatable plan: a nibble-aligned split by site, then by function/VLAN, leaving room to grow (Level 4 covered the mechanics).
- Security policy. Translate the IPv4 policy to IPv6 (it is not automatic): ICMPv6 filtering (RFC 4890, L5.02), first-hop security (L5.03), a default-deny perimeter without NAT (L5.05). RFC 9099 is the reference.
- Pilot. Enable IPv6 on a limited, well-instrumented segment; validate; then expand. Dual stack first, draining toward IPv6-only (Level 6) where it makes sense.
Success metrics
Define what "done" means and measure it: percentage of sites/segments dual-stacked, percentage of traffic that is IPv6, number of IPv6-capable vs blocking applications, mean time to resolve IPv6 incidents, and help-desk ticket rate. Without metrics the program stalls invisibly.
Blockers
The common blockers are legacy applications that assume IPv4 (L6.07), vendors/appliances that are IPv4-only or lag on IPv6 features, and security tooling (SIEM, IDS, DDoS, NAC) that does not parse or enforce IPv6 — a dangerous gap because IPv6 may be live and unmonitored (RFC 9099). Procurement must require IPv6 (RFC 6540) so the blocker list shrinks rather than grows.
ictNetworks scenario
ictNetworks ran its own corporate rollout in RFC 7381 phases: a capability inventory (which turned up two IPv4-only line-of-business apps and an IDS that could not parse IPv6), a training week, a /48 address plan aligned to Level 4, an IPv6 security policy per RFC 9099, and a pilot on one floor. Its success metrics are the dual-stack segment percentage and the IPv6 traffic share, reviewed monthly, and procurement now rejects IPv4-only purchases.
Drawing diagram…
Worked examples
Example 1: Subnets from the enterprise /48
A single enterprise /48 yields 2^(64-48) = 65536 /64 subnets — enough for every VLAN across every site with room to spare, so the plan is about hierarchy, not scarcity.
Example 2: Sites within the /48
Splitting the /48 into per-site /56 blocks gives 2^(56-48) = 256 sites, each itself able to hold 256 /64s — a clean two-level hierarchy for a mid-size enterprise.
Example 3: Nibble-aligned building blocks
Carving the /48 at the next nibble boundary, /52, yields 2^(52-48) = 16 large building blocks (e.g. one per region or function) before subdividing further — nibble alignment keeps reverse DNS and reading simple.
Lab
Goal: Write and peer-review a deployment plan for a fictional 2,000-user company.
You need: the fictional company profile (sites, user counts, applications, security stack), the RFC 7381 phase model and the RFC 9099 security checklist. This is a document exercise.
- Produce an inventory/assessment section listing capability and blockers (at least the legacy apps, a vendor gap and a security-tool gap).
- Write the address plan from a /48: a nibble-aligned hierarchy (sites, then functions/VLANs) with a growth reservation.
- Write the security policy mapping (ICMPv6, first-hop security, perimeter) per RFC 9099.
- Define success metrics and the pilot scope with entry/exit criteria.
- Peer-review another learner's plan against the RFC 7381 phases and record the findings.
What to submit: the deployment plan (all phases), the address plan, the metrics, and the peer-review notes.
Summary
- Treat enterprise IPv6 as a phased program: inventory, training, address plan, security policy, pilot (RFC 7381).
- Map the security policy explicitly to IPv6 (RFC 9099); it is not inherited from IPv4.
- Set success metrics (dual-stack coverage, IPv6 traffic share, blocker count) and measure them.
- The usual blockers are legacy apps, IPv4-only vendors and IPv6-blind security tooling; procurement must require IPv6.
- Next lesson (L7.04): campus and Wi-Fi networks.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.