<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-softwire-4rd" target="https://datatracker.ietf.org/doc/html/draft-ietf-softwire-4rd-00">
   <front>
      <title>IPv4 Residual Deployment via IPv6 - a unified Stateless Solution (4rd)</title>
      <author initials="R." surname="Després" fullname="Rémi Després">
         </author>
      <author initials="R." surname="Penno" fullname="Reinaldo Penno">
         </author>
      <author initials="Y." surname="Lee" fullname="Yiu Lee">
         </author>
      <author initials="G." surname="Chen" fullname="Gang Chen">
         </author>
      <author initials="S." surname="Jiang" fullname="Sheng Jiang">
         </author>
      <date month="May" day="21" year="2012" />
      <abstract>
	 <t>   The 4rd automatic tunneling mechanism makes IPv4 Residual Deployment
   possible via IPv6 networks without maintaining for this per-customer
   states in 4rd-capable nodes (reverse of the IPv6 Rapid Deployment of
   6rd).  To cope with the IPv4 address shortage, customers can be
   assigned IPv4 addresses with restricted port sets.  In some
   scenarios, 4rd-capable customer nodes can exchange packets of their
   IPv4-only applications via stateful NAT64s that are upgraded to
   support 4rd tunnels (in addition to their IP/ICMP translation of
   [RFC6145]).

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-softwire-4rd-00" />
   
</reference>
