Putting IPv6 Addresses into Context
Because IPv6 is so much larger than IPv4, the IETF has been able to structure the address space more neatly. Consequently, it is easier to distinguish between different address types based on the first few characters in the address, rather than having to refer to registry, as is often the case with IPv4.
Nonetheless, there are a lot of addresses and lots of new things to learn if you are only familiar with an IPv4 environment. But as we implement IPv6 across our networks we will see IPv6 addresses popping up in mail headers, system logs, traceroutes and all sorts of other places where IPv4 used to be used exclusively. Knowing quickly whether an address is part of your own network or someone else’s; whether an address is intended for private use or Internet use; and knowing whether an address is used by a transition mechanism or a native connection will help save lots of time.
Last year, ICANN staff worked with the staff at APNIC and the RIPE NCC to produce a single sheet that identified the key address groups, explained what they were and gave IPv4 examples of IPv4 equivalents where they existed. This year we have updated the sheet and you can grab a copy of the updated reference from here.
This reference will be useful for anyone working on an abuse desk, in a Network Operations Centre or a corporate IT department. Even if you don’t plan to roll out IPv6 on your own network in the next few months, you are likely to see it appearing on other networks. Using our cheat sheet can help bring you up to speed quickly and identify where to look for an address faster than by just consulting the on-line registries.
We want this reference guide to be as useful and current as possible, so as things change in the future we will produce further updates for you to use.