<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-v6ops-transition-ipv4aas" target="https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-transition-ipv4aas-15">
   <front>
      <title>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>
      <author initials="M." surname="Kawashima" fullname="Masanobu Kawashima">
         <organization>NEC Platforms, Ltd.</organization>
      </author>
      <date month="January" day="28" year="2019" />
      <abstract>
	 <t>This document specifies the IPv4 service continuity requirements for IPv6 Customer Edge (CE) routers that are provided either by the service provider or by vendors who sell through the retail market.

 Specifically, this document extends the basic requirements for IPv6 CE routers as described in RFC 7084 to allow the provisioning of IPv6 transition services for the support of IPv4-as-a-Service (IPv4aaS) by means of new transition mechanisms. The document only covers IPv4aaS, i.e., transition technologies for delivering IPv4 in IPv6-only access networks. IPv4aaS is necessary because there aren&#x27;t sufficient IPv4 addresses available for every possible customer/ device. However, devices or applications in the customer Local Area Networks (LANs) may be IPv4-only or IPv6-only and still need to communicate with IPv4-only services on the Internet.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-v6ops-transition-ipv4aas-15" />
   
</reference>
