<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-v6ops-framework-md-ipv6only-underlay" target="https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-framework-md-ipv6only-underlay-09">
   <front>
      <title>Framework of Multi-domain IPv6-only Underlay Network 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="T." surname="Graf" fullname="Thomas Graf">
         <organization>Swisscom</organization>
      </author>
      <date month="March" day="20" year="2025" />
      <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 bearer
   capabilities are used while ensuring global reachability for both
   IPv6 and IPv4 services(usually known as IPv4aaS).  This document
   proposes a general framework for deploying IPv6-only in one multi-
   domain underlay network.  It lists the requirements of service
   traffic, illustrates major components and interfaces, IPv6 mapping
   prefix allocation, typical procedures for service delivery from the
   perspective of network operation.  The document also discusses
   related security considerations.

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