%% You should probably cite draft-ietf-opsawg-l3sm-l3nm instead of this I-D.
@techreport{aguado-opsawg-l3sm-l3nm-01,
    number =    {draft-aguado-opsawg-l3sm-l3nm-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-aguado-opsawg-l3sm-l3nm/01/},
    author =    {Alejandro Aguado and Oscar Gonzalez de Dios and Victor Lopez and Daniel Voyer and Luis Angel Munoz},
    title =     {{Layer 3 VPN Network Model}},
    pagetotal = 98,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {RFC 8299 {[}RFC8299{]} defines a L3VPN Service Model (L3SM) YANG data model that can be used for communication between customers and network operators. It assumes that there is a monolithic management system with full control of transport resources. This approach (that is valid for the customer to network operator conversation) limits the usage of the model to the role of a Customer Service Model, according to the terminology defined in RFC 8309 {[}RFC8309{]}. There is a need for a YANG model for use between the entity that interacts directly with the customer (service orchestrator) and the entity in charge of network orchestration and control which, according to RFC 8309 {[}RFC8309{]}, can be referred as Service Delivery Model. In some cases, the control of the network is further expanded into per- domain control. This document uses the L3SM model defined in RFC 8299 {[}RFC8299{]}, and extends it to facilitate communication between the service orchestrator and transport orchestrator (MSDC), and an MDSC and domain controllers. The resulting model is called the L3VPN Network Model (L3NM).},
}