RFC 8683: Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise Networks
In plain English — editorial summary, not part of the RFC
This document describes how Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64) (including 464XLAT) can be deployed in an IPv6 network -- whether it's cellular ISP, broadband ISP, or enterprise -- and the possible optimizations. This document also discusses issues to be considered when having IPv6-only connectivity, such as: a) DNS64, b) applications or devices that use literal IPv4 addresses or non-IPv6-compliant APIs, and c) IPv4-only hosts or applications.
Document record
- Document ID
- RFC8683
- Published
- November 2019
- Authors
- J. Palet Martinez
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9872Recommendations for Discovering IPv6 Prefix Used for IPv6 Address SynthesisCurrent
September 2025
- RFC 8219Benchmarking Methodology for IPv6 Transition TechnologiesCurrent
August 2017
- RFC 9313Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)Current
October 2022
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 8880Special Use Domain Name 'ipv4only.arpa'Current
August 2020
- RFC 7051Analysis of Solution Proposals for Hosts to Learn NAT64 PrefixCurrent
November 2013
- RFC 7050Discovery of the IPv6 Prefix Used for IPv6 Address SynthesisUpdated
November 2013
- RFC 8512A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)Current
January 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?