<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.despres-intarea-4rd" target="https://datatracker.ietf.org/doc/html/draft-despres-intarea-4rd-01">
   <front>
      <title>IPv4 Residual Deployment across IPv6-Service networks (4rd) ISP-NAT&#x27;s made optional</title>
      <author initials="R." surname="Després" fullname="Rémi Després">
         <organization>RD-IPtech</organization>
      </author>
      <author initials="S." surname="Matsushima" fullname="Satoru Matsushima">
         <organization>SoftBank</organization>
      </author>
      <author initials="T." surname="Murakami" fullname="Tetsuya Murakami">
         <organization>IP Infusion</organization>
      </author>
      <author initials="O." surname="Trøan" fullname="Ole Trøan">
         <organization>Cisco</organization>
      </author>
      <date month="March" day="14" year="2011" />
      <abstract>
	 <t>This document specifies an automatic tunneling mechanism for
providing IPv4 connectivity service to end users over a service
provider&#x27;s IPv6 network.  During the long transition period from IPv4
to IPv6-only, a service provider&#x27;s network will have to support IPv6,
but will also have to maintain some IPv4 connectivity for a number of
customers, for both outgoing and incoming connections, and for both
exclusive and shared IPv4 addresses.  The 4rd solution (IPv4 Residual
Deployment) is designed as a lightweight solution for this.

In some scenarios, 4rd can dispense ISPs from supporting any NAT in
their networks.  In some others it can be used in parallel with NAT-
based solutions such as DS-lite and/or NAT64/DNS4.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-despres-intarea-4rd-01" />
   
</reference>
