One document matched: draft-ietf-v6ops-464xlat-07.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC6052 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6052.xml">
<!ENTITY RFC6144 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6144.xml">
<!ENTITY RFC6145 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6145.xml">
<!ENTITY RFC6146 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6146.xml">
<!ENTITY I-D.hazeyama-widecamp-ipv6-only-experience SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.hazeyama-widecamp-ipv6-only-experience.xml">
<!ENTITY I-D.ietf-behave-nat64-discovery-heuristic SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-behave-nat64-discovery-heuristic.xml">
<!ENTITY RFC1918 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1918.xml">
<!ENTITY RFC3123 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3123.xml">
<!ENTITY RFC3633 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3633.xml">
<!ENTITY RFC4389 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4389.xml">
<!ENTITY RFC5342 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5342.xml">
<!ENTITY RFC5625 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5625.xml">
<!ENTITY RFC6092 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6092.xml">
<!ENTITY RFC6147 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6147.xml">
<!ENTITY RFC6459 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6459.xml">
<!ENTITY RFC6535 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6535.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="bcp" docName="draft-ietf-v6ops-464xlat-07" ipr="trust200902">
<!-- category values: std, bcp, info, exp, and historic
ipr values: full3667, noModification3667, noDerivatives3667
you can add the attributes updates="NNNN" and obsoletes="NNNN"
they will automatically be output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the
full title is longer than 39 characters -->
<title abbrev="464XLAT">464XLAT: Combination of Stateful and Stateless Translation</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author fullname="Masataka Mawatari" initials="M.M."
surname="Mawatari">
<organization>Japan Internet Exchange Co.,Ltd.</organization>
<address>
<postal>
<street>KDDI Otemachi Building 19F, 1-8-1 Otemachi,</street>
<!-- Reorder these if your country does things differently -->
<city>Chiyoda-ku</city>
<region>Tokyo</region>
<code>100-0004</code>
<country>JAPAN</country>
</postal>
<phone>+81 3 3243 9579</phone>
<email>mawatari@jpix.ad.jp</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Masanobu Kawashima" initials="M.K."
surname="Kawashima">
<organization>NEC AccessTechnica, Ltd.</organization>
<address>
<postal>
<street>800, Shimomata</street>
<!-- Reorder these if your country does things differently -->
<city>Kakegawa-shi</city>
<region>Shizuoka</region>
<code>436-8501</code>
<country>JAPAN</country>
</postal>
<phone>+81 537 23 9655</phone>
<email>kawashimam@vx.jp.nec.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<author fullname="Cameron Byrne" initials="C.B."
surname="Byrne">
<organization>T-Mobile USA</organization>
<address>
<postal>
<street> </street>
<!-- Reorder these if your country does things differently -->
<city>Bellevue, Washington</city>
<code>98006</code>
<country>USA</country>
</postal>
<email>cameron.byrne@t-mobile.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<date month="August" year="2012" />
<!-- Meta-data Declarations -->
<area>General</area>
<workgroup>Internet Engineering Task Force</workgroup>
<!-- WG name at the upperleft corner of the doc,
IETF is fine for individual submissions.
If this element is not present, the default is "Network Working Group",
which is used by the RFC Editor as a nod to the history of the IETF. -->
<keyword>XLAT</keyword>
<keyword>Stateful Translation</keyword>
<keyword>Stateless Translation</keyword>
<!-- Keywords will be incorporated into HTML output
files in a meta tag but they have no effect on text or nroff
output. If you submit your draft to the RFC Editor, the
keywords will be used for the search engine. -->
<abstract>
<t>This document describes an architecture (464XLAT) for providing limited IPv4 connectivity across an IPv6-only network by combining existing and well-known stateful protocol translation RFC 6146 in the core and stateless protocol translation RFC 6145 at the edge. 464XLAT is a simple and scalable technique to quickly deploy limited IPv4 access service to IPv6-only edge networks without encapsulation.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>With the exhaustion of the unallocated IPv4 address pools, it will be difficult for many networks to assign IPv4 addresses to end users.</t>
<t>This document describes an IPv4 over IPv6 solution as one of the techniques for IPv4 service extension and encouragement of IPv6 deployment. 464XLAT is not a one-for-one replacement of full IPv4 functionality. The 464XLAT architecture only supports IPv4 in the client server model, where the server has a global IPv4 address. This means it is not fit for IPv4 peer-to-peer communication or inbound IPv4 connections. 464XLAT builds on IPv6 transport and includes full any-to-any IPv6 communication.</t>
<t>The 464XLAT architecture described in this document uses IPv4/IPv6 translation standardized in <xref target="RFC6145"></xref> and <xref target="RFC6146"></xref>. It does not require DNS64 [RFC6147] since an IPv4 host may simply send IPv4 packets, including packets to an IPv4 DNS server, which will be translated on the customer side translator(CLAT) to IPv6 and back to IPv4 on the provider side translator(PLAT). 464XLAT networks may use DNS64 <xref target="RFC6147"></xref> to enable single stateful translation <xref target="RFC6146"></xref> instead of 464XLAT double translation where possible. The 464XLAT architecture encourages the IPv6 transition by making IPv4 services reachable across IPv6-only networks and providing IPv6 and IPv4 connectivity to single-stack IPv4 or IPv6 servers and peers.</t>
<t>By combining 464XLAT with BIH <xref target="RFC6535"></xref>, it is also possible to provide single IPv4 to IPv6 translation service, which will be needed in the future case of IPv6-only servers and peers to be reached from IPv4-only hosts across IPv6-only networks.</t>
</section>
<section title="BCP Scenario">
<t>This BCP only applies when the following two criteria are present:
<list hangIndent="4" style="hanging">
<t hangText="1.">There is an IPv6-only network that uses stateful translation <xref target="RFC6146"></xref> as the only mechanism for providing IPv4 access.</t>
<t hangText="2.">There are IPv4-only applications or hosts that must communicate across the IPv6-only network to reach the IPv4 Internet.</t>
</list></t>
</section>
<section title="Requirements Language">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref
target="RFC2119"></xref>.</t>
</section>
<section title="Terminology">
<t><list hangIndent="8" style="hanging">
<t hangText="PLAT:">PLAT is Provider side translator(XLAT) that complies with <xref target="RFC6146"></xref>. It translates N:1 global IPv6 addresses to global IPv4 addresses, and vice versa.</t>
<t hangText="CLAT:">CLAT is Customer side translator(XLAT) that complies with <xref target="RFC6145"></xref>. It algorithmically translates 1:1 private IPv4 addresses to global IPv6 addresses, and vice versa. The CLAT function is applicable to a router or an end-node such as a mobile phone. The CLAT SHOULD perform router function to facilitate packets forwarding through the stateless translation even if it is an end-node. In the case where the access network does not allow for a dedicated IPv6 prefix for translation, a NAT44 SHOULD be used between the router function and the stateless translator function. The CLAT as a common home router or wireless 3GPP router is expected to perform gateway functions such as DHCP server and DNS proxy for local clients. The CLAT does not comply with the sentence "Both IPv4-translatable IPv6 addresses and IPv4-converted IPv6 addresses SHOULD use the same prefix." that is described on Section 3.3 in <xref target="RFC6052"></xref> due to using different IPv6 prefixes for CLAT-side and PLAT-side IPv4 addresses.</t>
</list></t>
</section>
<section title="Motivation and Uniqueness of 464XLAT">
<t><list hangIndent="4" style="hanging">
<t hangText="1.">Minimal IPv4 resource requirements, maximum IPv4 efficiency through statistical multiplexing.</t>
<t hangText="2.">No new protocols required, quick deployment.</t>
<t hangText="3.">IPv6-only networks are simpler and therefore less expensive to operate.</t>
</list></t>
</section>
<section title="Network Architecture">
<t>Examples of 464XLAT architectures are show in the figures in the following sections.</t>
<t>Wireline Network Architecture can fit in the situations that there are the clients behind the CLAT in the same way regardless of the type of access service, for example FTTH, Cable, or WiFi.</t>
<t>Wireless 3GPP Network Architecture can fit in the situations that client and node that terminate access network is same host in the same way.</t>
<section title="Wireline Network Architecture">
<t>The private IPv4 host on this diagram can reach global IPv4 hosts via translation on both CLAT and PLAT. On the other hand, the IPv6 host can reach other IPv6 hosts on the Internet directly without translation. This means that the CPE/CLAT can not only have the function of a CLAT but also the function of an IPv6 native router for native IPv6 traffic. The v4p host behind the CLAT on this diagram with the private IPv4 addresses.</t>
<figure align="center" anchor="Wireline_topology" title="Wireline Network Topology">
<preamble></preamble>
<artwork align="center"><![CDATA[
+------+
| v6 |
| host |
+--+---+
|
.---+---.
/ \
/ IPv6 \
| Internet |
\ /
`----+----'
|
+------+ | .---+---. .------.
| v6 +---+ +------+ / \ +------+ / \
| host | | | | / IPv6 \ | | / IPv4 \
+------+ +---+ CLAT +---+ Network +---+ PLAT +---+ Internet |
+--------+ | | | \ / | | \ /
| v4p/v6 +-+ +------+ `---------' +------+ `----+----'
| host | | |
+--------+ | +--+---+
+------+ | | v4g |
| v4p +---+ | host |
| host | | +------+
+------+ |
<- v4p -> XLAT <--------- v6 --------> XLAT <- v4g ->
v6 : Global IPv6
v4p : Private IPv4
v4g : Global IPv4
]]></artwork>
</figure>
</section>
<section title="Wireless 3GPP Network Architecture">
<t>The CLAT function on the User Equipment (UE) provides an <xref target="RFC1918"></xref> address and IPv4 default route. The applications on the UE can use the private IPv4 address for reaching global IPv4 hosts via translation on both CLAT and PLAT. On the other hand, reaching IPv6 hosts (including host presented via DNS64 <xref target="RFC6147"></xref>) does not require the CLAT function on the UE.</t>
<figure align="center" anchor="Wireless_topology" title="Wireless 3GPP Network Topology">
<preamble></preamble>
<artwork align="center"><![CDATA[
+------+
| v6 |
| host |
+--+---+
|
.---+---.
/ \
/ IPv6 \
| Internet |
\ /
UE / Mobile Phone `---------'
+----------------------+ |
| +----+ | | .---+---. .------.
| | v6 +----+ +------+ / \ +------+ / \
| +----+ | | | / IPv6 PDP \ | | / IPv4 \
| +---+ CLAT +---+ Mobile Core +---+ PLAT +--+ Internet |
| | | | \ GGSN / | | \ /
| | +------+ \ ' +------+ `----+---'
| +-----+ | | `-------' |
| | v4p +---+ | +--+---+
| +-----+ | | | v4g |
+----------------------+ | host |
+------+
<- v4p -> XLAT <--------- v6 --------> XLAT <- v4g ->
v6 : Global IPv6
v4p : Private IPv4
v4g : Global IPv4
]]></artwork>
</figure>
</section>
</section>
<section title="Applicability">
<section title="Wireline Network Applicability">
<t>When an ISP has IPv6 access service and provides 464XLAT, the ISP can provide outgoing IPv4 service to end users across an IPv6 access network. The result is that edge network growth is no longer tightly coupled to the availability of scarce IPv4 addresses.</t>
<t>If another ISP operates the PLAT, the edge ISP is only required to deploy an IPv6 access network. All ISPs do not need IPv4 access networks. They can migrate their access network to a simple and highly scalable IPv6-only environment.</t>
<t>Incidentally, the effectiveness of 464XLAT was confirmed in the WIDE camp Spring 2012. The result is described in <xref target="I-D.hazeyama-widecamp-ipv6-only-experience"></xref>.</t>
</section>
<section title="Wireless 3GPP Network Applicability">
<t>The vast majority of mobile networks are compliant to Pre-Release 9 3GPP standards. In Pre-Release 9 3GPP networks, GSM and UMTS networks must signal and support both IPv4 and IPv6 Packet Data Protocol (PDP) attachments to access IPv4 and IPv6 network destinations <xref target="RFC6459"></xref>. Since there are two PDPs required to support two address families, this is double the number of PDPs required to support the status quo of one address family, which is IPv4.</t>
<t>For the IPv4 literal or IPv4 socket applications that require IPv4 connectivity, the CLAT function on the UE provides a private IPv4 address and IPv4 default route on the host for the applications to reference and bind to. Connections sourced from the IPv4 interface are immediately routed to the CLAT function and passed to the IPv6-only mobile network, destined for the PLAT. In summary, the UE has the CLAT function that does a stateless translation <xref target="RFC6145"></xref>, but only when required. The mobile network has a PLAT that does stateful translation <xref target="RFC6146"></xref>.</t>
<t>464XLAT works with today's existing systems as much as possible. 464XLAT is compatible with existing network based deep packet inspection solutions like 3GPP standardized Policy and Charging Control (PCC) <xref target="TS.23203"></xref>.</t>
</section>
</section>
<section title="Implementation Considerations">
<section title="IPv6 Address Format">
<t>The IPv6 address format in 464XLAT is defined in Section 2.2 of <xref target="RFC6052"></xref>.</t>
</section>
<section title="IPv4/IPv6 Address Translation Chart">
<section title="Case of enabling only stateless XLATE on CLAT">
<t>This case should be used when a prefix delegation mechanism such as DHCPv6-PD <xref target="RFC3633"></xref> is available to assign a dedicated translation prefix to the CLAT.</t>
<figure align="center" title="Case of enabling only stateless XLATE on CLAT">
<preamble></preamble>
<artwork align="center"><![CDATA[
Destination IPv4 address
+----------------------------+
| Global IPv4 address |
| assigned to IPv4 server |
+--------+ +----------------------------+
| IPv4 | Source IPv4 address
| server | +----------------------------+
+--------+ | Global IPv4 address |
^ | assigned to IPv4 PLAT pool |
| +----------------------------+
+--------+
| PLAT | Stateful XLATE(IPv4:IPv6=1:n)
+--------+
^
|
(IPv6 cloud)
Destination IPv6 address
+--------------------------------------------------------------+
| IPv4-Embedded IPv6 address |
| defined in Section 2.2 of RFC6052 |
+--------------------------------------------------------------+
Source IPv6 address
+--------------------------------------------------------------+
| IPv4-Embedded IPv6 address |
| defined in Section 2.2 of RFC6052 |
+--------------------------------------------------------------+
(IPv6 cloud)
^
|
+--------+
| | In the case the CLAT has a
| | dedicated IPv6 prefix for
| CLAT | translation, the CLAT can
| | perform with only Stateless
| | XLATE (IPv4:IPv6=1:1).
+--------+
^ Destination IPv4 address
| +----------------------------+
+--------+ | Global IPv4 address |
| IPv4 | | assigned to IPv4 server |
| client | +----------------------------+
+--------+ Source IPv4 address
+----------------------------+
| Private IPv4 address |
| assigned to IPv4 client |
+----------------------------+
]]></artwork>
</figure>
</section>
<section title="Case of enabling NAT44 and stateless XLATE on CLAT">
<t>This case should be used when a prefix delegation mechanism is not available to assign a dedicated translation prefix to the CLAT. In this case, NAT44 SHOULD be used so that all IPv4 source addresses are mapped to a single IPv6 address.</t>
<figure align="center" title="Case of enabling NAT44 and stateless XLATE on CLAT">
<preamble></preamble>
<artwork align="center"><![CDATA[
Destination IPv4 address
+----------------------------+
| Global IPv4 address |
| assigned to IPv4 server |
+--------+ +----------------------------+
| IPv4 | Source IPv4 address
| server | +----------------------------+
+--------+ | Global IPv4 address |
^ | assigned to IPv4 PLAT pool |
| +----------------------------+
+--------+
| PLAT | Stateful XLATE(IPv4:IPv6=1:n)
+--------+
^
|
(IPv6 cloud)
Destination IPv6 address
+--------------------------------------------------------------+
| IPv4-Embedded IPv6 address |
| defined in Section 2.2 of RFC6052 |
+--------------------------------------------------------------+
Source IPv6 address
+--------------------------------------------------------------+
| IPv4-Embedded IPv6 address |
| defined in Section 2.2 of RFC6052 |
+--------------------------------------------------------------+
(IPv6 cloud)
^
|
+--------+
| | In the case the CLAT does not
| | have a dedicated IPv6 prefix
| CLAT | for translation, the CLAT can
| | perform with NAT44 and
| | Stateless XLATE
| | (IPv4:IPv6=1:1).
+--------+
^ Destination IPv4 address
| +----------------------------+
+--------+ | Global IPv4 address |
| IPv4 | | assigned to IPv4 server |
| client | +----------------------------+
+--------+ Source IPv4 address
+----------------------------+
| Private IPv4 address |
| assigned to IPv4 client |
+----------------------------+
]]></artwork>
</figure>
</section>
</section>
<section title="IPv6 Prefix Handling">
<section title="Case of enabling only stateless XLATE on CLAT">
<t>From the delegated DHCPv6 <xref target="RFC3633"></xref> prefix, a /64 is dedicated to source and receive IPv6 packets associated with the stateless translation <xref target="RFC6145"></xref>.</t>
<t>The CLAT MAY discover the Pref64::/n of the PLAT via some method such as DHCPv6 option, TR-069, DNS APL RR <xref target="RFC3123"></xref> or <xref target="I-D.ietf-behave-nat64-discovery-heuristic"></xref>.</t>
</section>
<section title="Case of enabling NAT44 and stateless XLATE on CLAT">
<t>In the case that DHCPv6-PD <xref target="RFC3633"></xref> is not available, the CLAT may not have a dedicated IPv6 prefix for translation. If the CLAT does not have a dedicated IPv6 prefix for translation, the CLAT can perform NAT44 and stateless translation <xref target="RFC6145"></xref>.</t>
<t>IPv4 packets from the LAN are NAT44 to the private IPv4 host address of the CLAT that is not included in LAN segment of CLAT. Then, the CLAT will do a stateless translation <xref target="RFC6145"></xref> so that the IPv4 packets from the CLAT IPv4 host address are translated to the CLAT WAN IPv6 address as described in <xref target="RFC6145"></xref>.</t>
<t>If the CLAT cannot perform ND Proxy <xref target="RFC4389"></xref> due to the restriction of the implementation, the CLAT may use a dedicated IANA assigned EUI-64 ID for creating a translated IPv6 address to be used in stateless translation <xref target="RFC6145"></xref>. This will allow the CLAT to avoid possible IPv6 address duplication issues between an IPv6 address for stateless translation <xref target="RFC6145"></xref> in the CLAT and an IPv6 address assigned to native IPv6 nodes behind the CLAT. This document describes an example for this case in Example 2. of the Appendix A.</t>
<t>The CLAT MAY discover the Pref64::/n of the PLAT via some method such as TR-069, DNS APL RR <xref target="RFC3123"></xref> or <xref target="I-D.ietf-behave-nat64-discovery-heuristic"></xref>.</t>
</section>
</section>
<section title="DNS Proxy Implementation">
<t>The CLAT SHOULD implement a DNS proxy as defined in <xref target="RFC5625"></xref>. The case of an IPv4-only node behind the CLAT querying an IPv4 DNS server is undesirable since it requires both stateful and stateless translation for each DNS lookup. The CLAT SHOULD set itself as the DNS server via DHCP or other means and proxy DNS queries for IPv4 and IPv6 LAN clients. Using the CLAT enabled home router or UE as a DNS proxy is a normal consumer gateway function and simplifies the traffic flow so that only IPv6 native queries are made across the access network. The CLAT SHOULD allow for a client to query any DNS server of its choice and bypass the proxy.</t>
</section>
<section title="CLAT in a Gateway">
<t>The CLAT is a stateless translation feature which can be implemented in a common home router or mobile phone that has a tethering feature. The router with CLAT function SHOULD provide common router services such as DHCP of <xref target="RFC1918"></xref> addresses, DHCPv6, and DNS service.</t>
</section>
<section title="CLAT to CLAT communications">
<t>While CLAT to CLAT IPv4 communication may work when the client IPv4 subnets do not overlap, this traffic flow is out of scope. 464XLAT is a hub and spoke architecture focused on enabling IPv4-only services over IPv6-only networks.</t>
</section>
</section>
<section title="Deployment Considerations">
<section title="Traffic Engineering">
<t>Even if the ISP for end users is different from the PLAT provider (e.g. another ISP), it can implement traffic engineering independently from the PLAT provider. Detailed reasons are below:</t>
<t><list hangIndent="4" style="hanging">
<t hangText="1.">The ISP for end users can figure out IPv4 destination address from translated IPv6 packet header, so it can implement traffic engineering based on IPv4 destination address (e.g. traffic monitoring for each IPv4 destination address, packet filtering for each IPv4 destination address, etc.). The tunneling methods do not have such an advantage, without any deep packet inspection for processing the inner IPv4 packet of the tunnel packet.</t>
<t hangText="2.">If the ISP for end users can assign an IPv6 prefix greater than /64 to each subscriber, this 464XLAT architecture can separate IPv6 prefix for native IPv6 packets and the XLAT prefixes for IPv4/IPv6 translation packets. Accordingly, it can identify the type of packets ("native IPv6 packets" and "IPv4/IPv6 translation packets"), and implement traffic engineering based on the IPv6 prefix.</t>
</list></t>
</section>
<section title="Traffic Treatment Scenarios">
<t>This 464XLAT architecture has capabilities. One is a IPv4 -> IPv6 -> IPv4 translation for sharing global IPv4 addresses as a basic function, another, if combined with BIH <xref target="RFC6535"></xref>, is a IPv4 -> IPv6 translation for reaching IPv6-only servers from IPv4-only clients that can not support IPv6. IPv4-only clients must be support through the long period of global transition to IPv6.</t>
<figure align="center" title="Traffic Treatment Scenarios">
<preamble></preamble>
<artwork align="center"><![CDATA[
+--------+-------------+-----------------------+-------------+
| Server | Application | Traffic Treatment | Location of |
| | and Host | | Translation |
+--------+-------------+-----------------------+-------------+
| IPv6 | IPv6 | End-to-end IPv6 | None |
+--------+-------------+-----------------------+-------------+
| IPv4 | IPv6 | Stateful Translation | PLAT |
+--------+-------------+-----------------------+-------------+
| IPv4 | IPv4 | 464XLAT | PLAT/CLAT |
+--------+-------------+-----------------------+-------------+
| IPv6 | IPv4 | BIH | CLAT |
+--------+-------------+-----------------------+-------------+
]]></artwork>
</figure>
<t>The above chart shows most common traffic types and traffic treatment.</t>
</section>
</section>
<section anchor="Security" title="Security Considerations">
<t>To implement a PLAT, see security considerations presented in Section 5 of <xref target="RFC6146"></xref>.</t>
<t>To implement a CLAT, see security considerations presented in Section 7 of <xref target="RFC6145"></xref>. The CLAT MAY comply with <xref target="RFC6092"></xref>.</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>IANA is requested to reserve a Modified EUI-64 identifier for 464XLAT according to section 2.2.2 of <xref target="RFC5342"></xref>. Its suggested value is 02-00-5E-00-00-00-00-00 to 02-00-5E-0F-FF-FF-FF-FF or 02-00-5E-10-00-00-00-00 to 02-00-5E-EF-FF-FF-FF-FF, depending on whether it should be taken in reserved or available values.</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>The authors would like to thank JPIX NOC members, JPIX 464XLAT trial service members, Seiichi Kawamura, Dan Drown, Brian Carpenter, Rajiv Asati, Washam Fan, Behcet Sarikaya, Jan Zorz, Tatsuya Oishi, Lorenzo Colitti, Erik Kline, Ole Troan, Maoke Chen, Gang Chen, Tom Petch, Jouni Korhonen, and Bjoern A. Zeeb for their helpful comments. Special acknowledgments go to Remi Despres for his plentiful supports and suggestions, especially about using NAT44 with IANA's EUI-64 ID. We also would like to thank Fred Baker and Joel Jaeggli for their support.</t>
</section>
<!-- Possibly a 'Contributors' section ... -->
</middle>
<!-- *****BACK MATTER ***** -->
<back>
<references title="Normative References">
&RFC2119;
&RFC6052;
&RFC6144;
&RFC6145;
&RFC6146;
</references>
<references title="Informative References">
&RFC1918;
&RFC3123;
&RFC3633;
&RFC4389;
&RFC5342;
&RFC5625;
&RFC6092;
&RFC6147;
&RFC6459;
&RFC6535;
&I-D.ietf-behave-nat64-discovery-heuristic;
&I-D.hazeyama-widecamp-ipv6-only-experience;
<reference anchor="TS.23203">
<front>
<title>Policy and charging control architecture</title>
<author><organization>3GPP</organization></author>
<date day="22" month="June" year="2012"/>
</front>
<seriesInfo name="3GPP TS" value="23.203 10.7.0"/>
<format type="HTML" target="http://www.3gpp.org/ftp/Specs/html-info/23203.htm"/>
</reference>
</references>
<section anchor="app-additional-1" title="Examples of IPv4/IPv6 Address Translation">
<t>The following are examples of IPv4/IPv6 Address Translation on the 464XLAT architecture.</t>
<t>Example 1. (Case of enabling only stateless XLATE on CLAT)</t>
<t>In the case that an IPv6 prefix greater than /64 is assigned to an end user by such as DHCPv6-PD <xref target="RFC3633"></xref>, only the Stateless XLATE functionality should be enabled on the CLAT as the CLAT can use a dedicated /64 from the assigned IPv6 prefix.</t>
<figure align="center">
<preamble></preamble>
<artwork align="center"><![CDATA[
Host & configuration value
+------------------------------+
| IPv4 server |
| [198.51.100.1] | IP packet header
+------------------------------+ +--------------------------------+
^ | Destination IP address |
| | [198.51.100.1] |
| | Source IP address |
| | [192.0.2.1] |
+------------------------------+ +--------------------------------+
| PLAT | ^
| IPv4 pool address | |
| [192.0.2.1 - 192.0.2.100] | |
| PLAT-side XLATE IPv6 prefix | |
| [2001:db8:1234::/96] | |
+------------------------------+ +--------------------------------+
^ | Destination IP address |
| | [2001:db8:1234::198.51.100.1] |
| | Source IP address |
| | [2001:db8:aaaa::192.168.1.2] |
+------------------------------+ +--------------------------------+
| CLAT | ^
| PLAT-side XLATE IPv6 prefix | |
| [2001:db8:1234::/96] | |
| CLAT-side XLATE IPv6 prefix | |
| [2001:db8:aaaa::/96] | |
+------------------------------+ +--------------------------------+
^ | Destination IP address |
| | [198.51.100.1] |
| | Source IP address |
| | [192.168.1.2] |
+------------------------------+ +--------------------------------+
| IPv4 client |
| [192.168.1.2/24] |
+------------------------------+
Delegated IPv6 prefix for client: 2001:db8:aaaa::/56
]]></artwork>
</figure>
<t>Example 2. (Case of enabling NAT44 and stateless XLATE on CLAT)</t>
<t>In the case that IPv6 prefix /64 is assigned to end users, the function of NAT44 and Stateless XLATE should be enabled on CLAT. Because the CLAT does not have dedicated IPv6 prefix for translation.</t>
<figure align="center">
<preamble></preamble>
<artwork align="center"><![CDATA[
Host & configuration value
+-------------------------------+
| IPv4 server |
| [198.51.100.1] | IP packet header
+-------------------------------+ +-------------------------------+
^ | Destination IP address |
| | [198.51.100.1] |
| | Source IP address |
| | [192.0.2.1] |
+-------------------------------+ +-------------------------------+
| PLAT | ^
| IPv4 pool address | |
| [192.0.2.1 - 192.0.2.100] | |
| PLAT-side XLATE IPv6 prefix | |
| [2001:db8:1234::/96] | |
+-------------------------------+ +-------------------------------+
^ | Destination IP address |
| | [2001:db8:1234::198.51.100.1] |
| | Source IP address |
| | [2001:db8:aaaa:0:200:5e10::] |
+-------------------------------+ +-------------------------------+
| CLAT Stateless XLATE function | ^
| - - - - - - - - - - - - - - - | |
| PLAT-side XLATE IPv6 prefix | |
| [2001:db8:1234::/96] | |
| CLAT-side XLATE IPv6 prefix | |
| [2001:db8:aaaa::/64] | |
| CLAT-side XLATE IPv6 EUI-64 ID| |
| [02-00-5E-10-00-00-00-00] | |
+ - - - - - - - - - - - - - - - + +-------------------------------+
| ^ | | Destination IP address |
| | | | [198.51.100.1] |
| | | | Source IP address |
| | | | [10.255.255.1] |
+ - - - - - - - - - - - - - - - + +-------------------------------+
| CLAT NAT44 function | ^
| - - - - - - - - - - - - - - - | |
| NAT44 NATed address | |
| [10.255.255.1/32] | |
+-------------------------------+ +-------------------------------+
^ | Destination IP address |
| | [198.51.100.1] |
| | Source IP address |
| | [192.168.1.2] |
+-------------------------------+ +-------------------------------+
| IPv4 client |
| [192.168.1.2/24] |
+-------------------------------+
Delegated IPv6 prefix for client: 2001:db8:aaaa::/64
]]></artwork>
</figure>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 12:41:42 |