# New IPv6 Documentation Prefix

DevFeed: [New IPv6 Documentation Prefix](<https://devfeed.tech/articles/new-ipv6-documentation-prefix-11127.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/01/rfc9637-ipv6-documentation-prefix/>)

Published: 2025-01-11T06:51:00Z

Content type: article

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Internet Engineering Task Force (IETF)](<https://devfeed.tech/topics/ietf.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [documentation](<https://devfeed.tech/tags/documentation.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>)

## AI overview

The article discusses RFC 9637, which defines the larger 3fff::/20 IPv6 documentation prefix after discussions in the IETF v6ops working group. It argues that examples should use documentation address space instead of public IPv6 addresses.

## Source excerpt

After three and a half years of haggling (the IETF draft that became the RFC was written in May 2021; the original discussions go back to 2013), Nick Buraglio & co managed to persuade pontificators bikeshedding in the v6ops working group that we might need an IPv6 documentation prefix larger than the existing 2001:db8::/32. With the new documentation prefix (3fff::/20) (defined in RFC 9637), there's absolutely no excuse to use public IPv6 address space in examples anymore.