The Never-Ending Prefix Debate: Revisiting Best Current Practices

Why It Matters

If adopted, the BCP will standardize IPv6 addressing best practices across providers and enterprises, reducing fragmentation, operational surprises, and compliance ambiguity while making future renumbering and routing aggregation simpler. This has direct impact on network design, vendor behavior, and regulatory or contractual references to “best practices.”

Summary

Speakers reviewed a draft BCP that updates long-standing IPv6 prefix practices for operators, arguing many legacy rules of thumb no longer apply. The draft clarifies prefix choices for point-to-point links, site addressing, and numbering strategies—notably downgrading the urgency of special-case sizes (like /127s or other non-/64s) and endorsing more flexible /64-based approaches to avoid needless renumbering. It also addresses how service-provider aggregation and customer allocations interact with those choices and calls for modernizing older RFC guidance that arose from obsolete hardware limitations. The authors emphasize the document’s BCP status, meaning it’s intended as an authoritative operational guideline.

Original Description

Today’s conversation centers around a new Best Current Practices (BCP) RFC draft written by Jordi Martinez. Our hosts explore the document for service providers and enterprises, including prefix sizing for point-to-point links, the pros and cons of numbering choices, and best practices for prefix pool allocation.

Links:

IPv6 Prefix Assignment to End-Sites - RFC Draft - https://datatracker.ietf.org/doc/draft-ietf-v6ops-prefix-to-end-sites/

IPv6 Buzz is part of the Packet Pushers network. Visit our website to find more great networking and technology podcasts, along with tutorial videos, the Human Infrastructure newsletter, and loads more resources for building your IT career. https://packetpushers.net