icon-1-darkicon-1-darkicon-1-lighticon-2-darkicon-2-lighticon-3-darkicon-3-lighticon-4-darkicon-4-lighticon-5-darkicon-5-lighticon-6-darkicon-6-lighticon-7-darkicon-7-lighticon-8-darkicon-8-lighticon-9-darkISOC-IconISOC-IconISOC-IconShapeISOC-IconISOC-IconISOC-IconPage 1icon-comma-darkicon-comma-lightFill 1ISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconShapeISOC-IconISOC-IconISOC-IconBLOCKSISOC-IconISOC-IconISOC-IconISOC-IconLISTISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconLEFTISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconShapeDOWN ARROWSEARCHISOC-IconISOC-IconISOC-IconISOC-IconISOC-IconISOC-Icon-Dark-RGBISOC-Society-logo
RFC 8215: Local-Use IPv4/IPv6 Translation Prefix published Thumbnail
‹ Back
Deploy360 25 August 2017

RFC 8215: Local-Use IPv4/IPv6 Translation Prefix published

Kevin Meynell
By Kevin MeynellSenior Manager, Technical and Operational Engagement

IPv6 BadgeRFC 8215 “Local-Use IPv4/IPv6 Translation Prefix” was recently published, reserving the IPv6 prefix 64:ff9b:1::/48 for local use within domains enabling IPv4/IPv6 translation mechanisms.

This allows the coexistence of multiple IPv4/IPv6 translation mechanisms in the same network, without requiring the use of a Network-Specific Prefix assigned from an allocated global unicast address space.

The well-known prefix 64:ff9b::/96 was originally reserved by RFC6052 for IPv4/IPv6 translation, but several new translation mechanisms such as those in RFCs 6146 and 7915 have subsequently been defined that target different use cases. It’s therefore possible that a network operator may wish to make use of several of these simultaneously, hence why a larger address space has been defined to accommodate this.

The shortest translation prefix being deployed in a live network was observed as being a /64, hence /48 was chosen as being on a 16-bit boundary whilst being able to accommodate multiple instances of /64.

If you’re interested in finding out more about IPv4/IPv6 translation mechanisms, there’s a few Deploy360 blogs on NAT64 and 464XLAT amongst others.

‹ Back

Disclaimer: Viewpoints expressed in this post are those of the author and may or may not reflect official Internet Society positions.

Related articles

Rough Guide to IETF 97: All About IPv6
IETF8 November 2016

Rough Guide to IETF 97: All About IPv6

In this post for the Internet Society Rough Guide to IETF 97, I’ll take a look at some recent IPv6...

Deploy360@IETF 96, Day 4: SIDR & IPv6
Deploy36021 July 2016

Deploy360@IETF 96, Day 4: SIDR & IPv6

Throughout this week at IETF 96 in Berlin we’re bringing you these daily blog posts that highlight what Deploy360 is focused on during that day....

CGN, IPv6 and fighting online crime...
CGN, IPv6 and fighting online crime...
Improving Technical Security10 March 2018

CGN, IPv6 and fighting online crime…

Carrier Grade NAT (CGN) is commonly used by network operators as a way of ekeing out the limited supply of...

Join the conversation with Internet Society members around the world