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