IPv6 in Soft Landing

Measurable IPv6 traffic deployment milestones · DRAFT02 adds measurable deployment conditions to the existing requirement for a coherent IPv6 plan. Applicants must identify their network's actual top 25 IPv4 traffic destinations; for destinations that support IPv6, compliance requires at least 25% IPv6 within 12 months, 50% within 24 months and 75% within 48 months. These thresholds concern traffic to IPv6-enabled destinations, not an unconditional percentage of all network traffic.

IPv6 reachability milestones for hosted services · DRAFT02 adds a separate compliance measure for networks hosting services, applications or content: AAAA records must be available and the services reachable over IPv6 from the Internet, with thresholds of 25% within 12 months, 75% within 24 months and 95% within 48 months. The retained DRAFT01 requires a coherent deployment plan but contains none of these hosting percentages.

Staff impact assessment added to the retained page · The newer retained page includes a staff impact assessment where the earlier page says the assessment will be available later. Staff asks for explicit definitions of a coherent deployment plan, retrospective review, milestone evidence, the interaction with CPM 6.4.4, and consequences of partial compliance or justified delay. These are staff recommendations and unresolved implementation questions; they are not additional enacted policy requirements.

DRAFT02 archived after DRAFT03 supersession · The retained DRAFT02 page changes from Under Discussion to Archived and states that DRAFT03 superseded it on 17 September 2026. The page retains the same DRAFT02 proposal wording and staff impact assessment for reference. Its new revision-history entry reports changed criteria in DRAFT03, but this pair of DRAFT02 snapshots does not contain those new criteria and cannot establish their substance or policy adoption.