<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.liu-behave-nat46" target="https://datatracker.ietf.org/doc/html/draft-liu-behave-nat46-02">
   <front>
      <title>NAT46 considerations</title>
      <author initials="D." surname="Liu" fullname="Dapeng Liu">
         </author>
      <author initials="H." surname="Deng" fullname="DENG Hui">
         <organization>China Mobile</organization>
      </author>
      <date month="March" day="8" year="2010" />
      <abstract>
	 <t>The period of IPv4/IPv6 transisation will last for a long time.
Different phases of IPv4/IPv6 transisation have different scenarioes
and requirements thus need different solutions.  In the early stage
of IPv4/IPv6 transisation, sicne the majority of the Internet
resources locate in the IPv4 Internet, the main communication type of
the IPv4/IPv6 transition is v6 to v4 which is the IPv6 clients iniate
communication to the IPv4 servers.  At the later stage of the IPv4/
IPv6 transisation, the servers may locate in the IPv6 network/
Internet, in this scenario, there is a need for the legacy IPv4
client to iniate communication to the IPv6 servers.  This document
analyses the problems of v4 to v6 communication and discusses a
solution called PNAT-Lite.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-liu-behave-nat46-02" />
   
</reference>
