| Internet-Draft | Reclassifying RFC6052 to STD | October 2025 |
| Palet Martinez | Expires 22 April 2026 | [Page] |
This document reclassifies IPv6 Addressing of IPv4/IPv6 Translators ([RFC6052]) to Internet Standard.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 22 April 2026.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document proposes that IPv6 Addressing of IPv4/IPv6 Translators ([RFC6052]) is advanced Internet Standard, following RFC6410 ([RFC6410]).¶
(1) There are at least two independent interoperating implementations with widespread deployment and successful operational experience.¶
IPv6 Addressing of IPv4/IPv6 Translators ([RFC6052]) has been widely implemented by at least a dozen of vendors and its being used in commercial deployments by hundreds of millions of devices.¶
(2) There are no errata against the specification that would cause a new implementation to fail to interoperate with deployed ones.¶
IPv6 Addressing of IPv4/IPv6 Translators ([RFC6052]) has no errata filed.¶
(3) There are no unused features in the specification that greatly increase implementation complexity.¶
There are no unused features.¶
(4) If the technology required to implement the specification requires patented or otherwise controlled technology, then the set of implementations must demonstrate at least two independent, separate and successful uses of the licensing process.¶
None.¶
Note to RFC Editor: If this document needs to be published, please remove this section before publication, as it is only intended for the IESG evaluation.¶
This section summarized the known status of existing and interoperable implementations of the protocol subject of this document, as well as closely related protocols. This is following ([RFC7942]) and intended to assist the relevant WGs, IESG and IETF as a whole, in the evaluation of the document for the document progress through the standardization process.¶
The description of the implementations is does not imply any IETF endorsement and is solely based on public available information, which has not been formally confirmed by specific interoperatbility testing for this document publication; however, it is known to be confirmed by existing commercial working deployments worldwide and without knows interoperability issues.¶
IPv6 Addressing of IPv4/IPv6 Translators ([RFC6052]) was originally published in October 2010.¶
([RFC6052]) needs to be implemented when implementing other related protocols (just to name a few of the most relevant ones) such as:¶
Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers ([RFC6146]).¶
DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers ([RFC6147]).¶
Mapping of Address and Port using Translation (MAP-T) ([RFC7599]).¶
SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments ([RFC7755]).¶
Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation Mode ([RFC7756]).¶
464XLAT: Combination of Stateful and Stateless Translation ([RFC7877]).¶
Follows a list of known implementations by different products/vendors, known to be mature and in production products worlwide:¶
6Wind. Implemented in multiple products as part of NAT64 support. https://www.6wind.com/6wind-cg-nat-vrouter-with-nat64/.¶
A10. Implemented in multiple products as part of the NAT64 support.¶
AlliedTelesis. Implemented in multiple products as part of the NAT64 support.https://www.alliedtelesis.com/sites/default/files/documents/configuration-guides/transitioning_ipv4_to_ipv6_feature_overview_guide.pdf.¶
Amazon. Virtual Private Cloud. https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-nat64-dns64.html.¶
Android (Google). Implemented since earlier CLAT implementation in 2012. https://android.googlesource.com/platform/external/android-clat. Implemented also in Google Cloud. https://cloud.google.com/vpc/docs/ipv6-to-ipv4-overview.¶
Apple. Implemented since 2016. https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html.¶
Arista. Implemented in multiple products as part of the NAT64 implementation. https://www.arista.com/en/support/toi/eos-4-24-0f/14495-map-t-border-relay.¶
BlueCat. Implemented as part of the DNS64 support. https://docs.bluecatnetworks.com/r/Address-Manager-Administration-Guide/DNS64/9.4.0.¶
Bpfnat. Implemented as part of the CLAT support. https://github.com/apalrd/bpfnat.¶
Broadcom. Implemented in VMWare. https://techdocs.broadcom.com/us/en/vmware-cis/nsx/nsxt-dc/3-1/administration-guide/network-address-translation/configure-an-nsx-nat64.html.¶
Cisco. Implemented in multiple series of products since 2010. https://www.cisco.com/c/en/us/td/docs/routers/ios/config/17-x/ip-addressing/b-ip-addressing/m_iadnat-stateless-nat64.html.¶
CLATD. Implemented in Linux, as part of the CLAT implementation. https://github.com/toreanderson/clatd.¶
Ecdysis. Implemented as part of the NAT64 support. http://ecdysis.viagenie.ca/.¶
F5. Implemented in multiple products as part of the NAT64 support. https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/cgn-implementations-11-6-0/2.html.¶
Fortinet. Implemented in multiple products as part of the NAT64 support. https://docs.fortinet.com/document/fortigate/7.4.6/fortinet-carrier-grade-nat-field-reference-architecture-guide/891965/nat64.¶
Huawei. Implemented in multiple series of products. https://support.huawei.com/enterprise/en/doc/EDOC1100278545/fe351de4/nat64-configuration.¶
Infoblox. Implemented as part of the DNS64 support. https://www.a10networks.com/products/thunder-cgn/.¶
Jool. Implmemented since 2014. https://nicmx.github.io/Jool/en/index.html.¶
Juniper. Implemented in multiple series of products as part of the NAT64 support. https://www.juniper.net/documentation/us/en/software/nce/nce-nat64-ipv6-ipv4-depletion/topics/concept/ipv6-nat64-ipv4-depletion-overview.html.¶
Microsoft. Implemented for the CLAT support in 2016. https://techcommunity.microsoft.com/blog/networkingblog/core-network-stack-features-in-the-creators-update-for-windows-10/339676.¶
Nokia. Implemented in multiple products as part of the NAT64 support. https://documentation.nokia.com/html/0_add-h-f/93-0262-HTML/7750_SR_OS_MSISA_Guide/Application-Assurance-NAT.pdf.¶
OpenWRT. Implemented as part of the support of CLAT. https://github.com/openwrt.¶
Palo Alto. Implemented in muliple products as part of the NAT64 support. https://docs.paloaltonetworks.com/ngfw/networking/nat64.¶
Sophos. Implemented in multiple products as part of the NAT64 support. https://news.sophos.com/en-us/2025/04/08/sophos-firewall-v21-5-early-access-is-now-available/.¶
Tayga. Implemented as part of the NAT64 support. https://github.com/openthread/tayga.¶
VPP. Implemented as part of the NAT64 support. https://docs.fd.io/vpp/17.07/nat64_doc.html.¶
ZTE. Implemented in multiple products as part of the NAT64 support. https://www.zte.com.cn/global/product_index/ip_network_en/68e_e/zxr10-6800e/zxr10-6800e.html.¶
Note that even an effort has been done to compile an extensive list (including a relevant URL), there may be many more implementations not publicly known, so this list doesn't pretent to be exclusive, just an indication of a sufficient number of implementations, as required for the evaluation of the current implementation status.¶