%% You should probably cite draft-liu-teas-transport-network-slice-yang-09 instead of this revision.
@techreport{liu-teas-transport-network-slice-yang-06,
    number =    {draft-liu-teas-transport-network-slice-yang-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-liu-teas-transport-network-slice-yang/06/},
    author =    {Xufeng Liu and Jeff Tantsura and Igor Bryskin and Luis M. Contreras and Qin Wu and Sergio Belotti and Reza Rokui and Aihua Guo and Italo Busi},
    title =     {{IETF Network Slice Topology YANG Data Model}},
    pagetotal = 27,
    year =      2023,
    month =     mar,
    day =       13,
    abstract =  {An IETF network slice may use an abstract topology to describe intended underlay for connectivities between slice endpoints. Abstract topologies help the customer to request network slices with shared resources amongst connections, and connections can be activated within the slice as needed. This document describes a YANG data model for managing and controlling abstract topologies for IETF network slices defined in RFC YYYY. {[}RFC EDITOR NOTE: Please replace RFC YYYY with the RFC number of draft-ietf-teas-ietf-network-slices once it has been published.},
}