<?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-12">
   <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="July" day="22" year="2025" />
      <abstract>
	 <t>   For the IPv6 transition, IPv6-only is considered as the final stage,
   where only IPv6 protocol is used for transport while maintaining
   global reachability for both IPv6 and IPv4 services.  This document
   illustrates a framework of multi-domain IPv6-only underlay network
   from an operator&#x27;s perspective.  In particular, it proposes stateless
   address mapping as the base for enabling IPv4 service data
   transmission in an multi-domain IPv6-only environment(i.e.,IPv4-as-
   a-Service).  It describes the methodology of stateless IPv4/IPv6
   mapping, illustrates the behaviors of network devices, analyzes the
   options of IPv6 mapping prefix allocation, examines the utilization
   of SRv6, and discusses the security considerations.

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