<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.palet-v6ops-transition-ipv4aas" target="https://datatracker.ietf.org/doc/html/draft-palet-v6ops-transition-ipv4aas-00">
   <front>
      <title>Transition Requirements for IPv6 Customer Edge Routers to support IPv4 as a Service</title>
      <author initials="J. P." surname="Martinez" fullname="Jordi Palet Martinez">
         <organization>The IPv6 Company</organization>
      </author>
      <author initials="H." surname="Liu" fullname="Hans M.-H. Liu">
         <organization>D-Link Systems, Inc.</organization>
      </author>
      <date month="March" day="2" year="2018" />
      <abstract>
	 <t>   This document specifies the transition requirements for an IPv6
   Customer Edge (CE) router, either provided by the service provider or
   thru the retail market.

   Specifically, this document extends the &quot;Basic Requirements for IPv6
   Customer Edge Routers&quot; ([RFC7084]) in order to allow the provisioning
   of IPv6 transition services for the support of IPv4 as a Service
   (IPv4aaS) by means of new transition mechanisms, which where not
   available at the time [RFC7084] was published.  The document only
   covers transition technologies for delivering IPv4 in IPv6-only
   access networks, commonly called IPv4 &quot;as-a-service&quot; (IPv4aaS), as
   required in a world where IPv4 addresses are no longer available, so
   hosts in the customer LANs with IPv4-only or IPv6-only applications
   or devices, requiring to communicate with IPv4-only services at the
   Internet, are still able to do so.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-palet-v6ops-transition-ipv4aas-00" />
   
</reference>
