%% You should probably cite draft-ietf-v6ops-framework-md-ipv6only-underlay-07 instead of this revision.
@techreport{ietf-v6ops-framework-md-ipv6only-underlay-06,
    number =    {draft-ietf-v6ops-framework-md-ipv6only-underlay-06},
    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/06/},
    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 Network and IPv4-as-a-Service}},
    pagetotal = 23,
    year =      ,
    month =     ,
    day =       ,
    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 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. The document also discusses related security considerations.},
}