Capstone: design, build and defend an IPv6 network
Produce a complete IPv6 design for the ictNetworks reference scenario. Build and validate it in the lab. Defend the design choices against the course's standards.
Take the quiz · pass mark 70% · 9 questions
Explanation
The capstone pulls the whole course together: take the ictNetworks reference scenario (built on the base IPv6 specification, RFC 8200) and deliver a complete, working, defensible IPv6 network — an address plan, routing, security, services and transition, built in the lab and justified against the standards you have learned. There is no new protocol here; the skill is integration and judgement.
The scenario
ictNetworks (AS65550) is a regional provider and enterprise operator. It holds a provider block from the documentation range (3fff:a00::/32) to allocate to customers and sites, uses 2001:db8::/32 for additional documentation examples, the course ULA fdf1:a861:26b6::/48 internally where appropriate, and peers with ISP-A (AS64496), ISP-B (AS64497), an enterprise customer (AS64498) and an IXP (AS64511). IPv4 appears only as documentation space (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24).
What the capstone must deliver
- Address plan (RFC 4291 architecture): a nibble-aligned hierarchy from the /32 — per-customer and per-site /48s, per-VLAN /64s, consistent and aggregatable, documented in an IPAM. Reverse DNS designed alongside.
- Routing: an IGP inside, BGP to the two ISPs and the IXP, with filtering so only intended prefixes are announced and no ULA or documentation space leaks (Levels 4, 7).
- Security (RFC 9099, RFC 4890): a correct ICMPv6 policy (permit what PMTUD/ND need, drop the rest), first-hop security on access (RA Guard, DHCPv6 Shield, SAVI), and control-plane protection — the Level 5 policy applied end to end.
- Services: dual-stack DNS (AAAA/PTR), and transition mechanisms where needed — NAT64/DNS64 (RFC 6146) for IPv6-only segments reaching IPv4-only destinations, chosen deliberately (Level 6).
- Operations (RFC 7011): flow monitoring (IPFIX), reachability tests per family, and an automation/CI loop (L8.06) so the build is reproducible.
- Advanced choices: justify where (or whether) to use SRv6, multicast, anycast or NPTv6 from this level.
Defending the design
The deliverable is not just a config but a defence: for every choice, cite the standard and the reason, show the trade-off considered, and prove it in the lab. Where guidance is a best current practice rather than a hard rule (enterprise deployment per RFC 7381, operational security per RFC 9099), say so and explain the local decision. Where vendor behaviour matters, note that syntax and defaults are version-dependent.
Drawing diagram…
Worked examples
Example 1: Customer /32 to /29 block sizing
If ictNetworks were allocated a /29 and sub-divided it into /32 regional blocks, that is 2^(32-29) = 8 regional /32 blocks to assign — a reminder to leave room at the top of the hierarchy.
Example 2: Site /48s from a /44
A large customer given a /44 can be sub-allocated 2^(48-44) = 16 site /48s, each a full site allocation, keeping the plan nibble-aligned.
Example 3: /64 subnets under a /44
That same /44 contains 2^(64-44) = 1048576 /64 subnets — effectively unlimited for the customer, so the plan optimises for clean aggregation, not conservation.
Lab
Goal: Build and defend the complete ictNetworks IPv6 design in the lab.
You need: a containerlab topology covering ictNetworks, two ISPs, an IXP and an enterprise customer; FRR (and any vendor nodes); DNS, NAT64 and monitoring components; and the automation/CI from L8.06. (All tool syntax is version-dependent — check the docs.)
- Address plan: allocate from 3fff:a00::/32 (and 2001:db8::/32 for examples) — nibble-aligned /48s and /64s in an IPAM, with reverse DNS. Validate no overlaps and documentation space only.
- Routing: bring up the IGP and BGP to ISP-A, ISP-B and the IXP; filter so only intended prefixes are announced and no ULA/documentation space leaks.
- Security: apply the ICMPv6 policy (RFC 4890), first-hop security on access, and control-plane protection (RFC 9099); prove PMTUD works and rogue RAs are blocked.
- Services + transition: stand up dual-stack DNS (AAAA/PTR) and NAT64/DNS64 (RFC 6146) for an IPv6-only segment; demonstrate an IPv6-only host reaching an IPv4-only destination.
- Operations: enable flow monitoring (IPFIX, RFC 7011) and run the CI reachability/policy suite from L8.06; make the whole build reproducible from the source of truth.
- Defend: write up every major choice with its standard, trade-off and lab evidence, including a justified decision on each advanced topic (SRv6, multicast, anycast, NPTv6).
What to submit: the IPAM plan and reverse DNS, the routing/security/service configs, the NAT64 and monitoring evidence, the CI run, and the written design defence citing the standards.
Summary
- The capstone integrates the whole course into a complete, working, defensible ictNetworks IPv6 design.
- Deliver an aggregatable address plan (RFC 4291), filtered routing, the Level 5 security policy (RFC 4890/9099), dual-stack DNS with NAT64/DNS64 (RFC 6146), and monitored, CI-tested operations (RFC 7011).
- Justify every choice against the standards, show the trade-offs, and prove it in the lab.
- Best-practice guidance (RFC 7381, RFC 9099) is explained and adapted locally; vendor syntax is version-dependent.
- This completes Level 8 and the taught content; the certification exam follows.
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.