IETF Interim: Stub Network Auto Configuration for IPv6 (SNAC) 2026-04-16 13:00
Why It Matters
Clarifying the state machine’s status and closing open issues accelerates SNAC’s standardization, reducing implementation ambiguity for IPv6 networks worldwide.
Key Takeaways
- •State machine should be informative, not normative, to avoid conflicts.
- •Move existing state machine content to appendix before last call.
- •Ensure normative text fully covers functionality after extracting state machine.
- •Resolve open issues on multiple AIL interfaces and reference changes.
- •Review ULA link prefix stability and clarify “should” language.
Summary
The interim SNAC meeting focused on clearing the path to a last‑call for the IPv6 Stub Network Auto‑Configuration draft. Participants debated the role of the state machine, concluding it must remain informative and be relocated to an appendix, thereby preventing normative conflicts that plagued earlier DHCP work. Key discussion points included verifying that the remaining normative text fully describes required behavior once the state machine is removed, and addressing lingering open items such as handling multiple AIL interfaces and updating reference classifications from normative to informative. The group also examined a pull request concerning ULA link‑prefix stability, noting the need to tighten language around "should" statements and provide clearer exception criteria. Consensus emerged that the draft is ready for a final review, provided the state‑machine appendix is added and any residual normative gaps are patched. The team agreed to announce the decision on the mailing list, allowing a brief comment period before proceeding to the formal last‑call. If these steps are followed, the SNAC specification will advance toward publication, offering implementers a clearer, more stable framework for IPv6 stub‑network deployments.
Comments
Want to join the conversation?
Loading comments...