<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.xie-v6ops-framework-md-ipv6only-underlay" target="https://datatracker.ietf.org/doc/html/draft-xie-v6ops-framework-md-ipv6only-underlay-05">
   <front>
      <title>Framework of Multi-domain IPv6-only Underlay Networks and IPv4 as a Service</title>
      <author initials="C." surname="Xie" fullname="Chongfeng Xie">
         <organization>China Telecom</organization>
      </author>
      <author initials="C." surname="Ma" fullname="Chenhao Ma">
         <organization>China Telecom</organization>
      </author>
      <author initials="X." surname="Li" fullname="Xing Li">
         <organization>CERNET Center/Tsinghua University</organization>
      </author>
      <author initials="G. S." surname="Mishra" fullname="Gyan Mishra">
         <organization>Verizon Inc</organization>
      </author>
      <author initials="M." surname="Boucadair" fullname="Mohamed Boucadair">
         <organization>Orange</organization>
      </author>
      <author initials="T." surname="Graf" fullname="Thomas Graf">
         <organization>Swisscom</organization>
      </author>
      <date month="October" day="21" year="2022" />
      <abstract>
	 <t>   For the IPv6 transition, dual-stack deployments require both IPv4 and
   IPv6 forwarding capabilities to be deployed in parallel.  IPv6-only
   is considered as the ultimate stage where only IPv6 transfer
   capabilities are used while ensuring global reachability for both
   IPv6 and IPv4 (usually known as IPv4aaS).  This document specifies
   requirements and proposes a framework for deploying IPv6-only as the
   underlay in multi-domain networks, discusses the requirements of
   service traffic, major components and interfaces, IPv6 mapping prefix
   allocation, typical procedures for service delivery.  The document
   also discusses related considerations with security.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-xie-v6ops-framework-md-ipv6only-underlay-05" />
   
</reference>
