%% You should probably cite draft-ietf-v6ops-framework-md-ipv6only-underlay-25 instead of this revision.
@techreport{ietf-v6ops-framework-md-ipv6only-underlay-12,
    number =    {draft-ietf-v6ops-framework-md-ipv6only-underlay-12},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-v6ops-framework-md-ipv6only-underlay/12/},
    author =    {Chongfeng Xie and Chenhao Ma and Xing Li and Gyan Mishra and Thomas Graf},
    title =     {{Framework of Multi-domain IPv6-only Underlay Network and IPv4-as-a-Service}},
    pagetotal = 22,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {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'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.},
}