| Internet-Draft | Reclassifying NAT64 (RFC6146) to STD | July 2025 |
| Palet Martinez | Expires 8 January 2026 | [Page] |
This document reclassifies Stateful NAT64 ([RFC6146]) 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 8 January 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 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers ([RFC6146]) is advanced Internet Standard, following RFC6410 ([RFC6410]).¶
(1) There are at least two independent interoperating implementations with widespread deployment and successful operational experience.¶
Stateful NAT64 ([RFC6146]) 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.¶
Stateful NAT64 ([RFC6146]) has 2 errata, none of which would cause new interoperability problems.¶
(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.¶
There is a pending Patent that offers Reasonable and Non-Discriminatory License to All Implementers with Possible Royalty/Fee, however it hasn't constituted an issue for multiple independent implementations.¶