%% You should probably cite draft-ietf-bess-evpn-ac-aware-bundling-04 instead of this revision.
@techreport{ietf-bess-evpn-ac-aware-bundling-03,
    number =    {draft-ietf-bess-evpn-ac-aware-bundling-03},
    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-bess-evpn-ac-aware-bundling/03/},
    author =    {Ali Sajassi and Mankamana Prasad Mishra and Samir Thoria and Jorge Rabadan and John Drake},
    title =     {{AC-Aware Bundling Service Interface in EVPN}},
    pagetotal = 13,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {EVPN (Ethernet VPNs) provides an extensible and flexible multihoming VPN solution over an MPLS/IP network for intra-subnet connectivity among Tenant Systems and End Devices that can be physical or virtual. EVPN multihoming with Integrated Routing and Bridging (IRB) is one of the common deployment scenarios. There are deployments which requires capability to have multiple subnets designated with multiple VLAN IDs in single broadcast domain. EVPN technology defines three different types of service interface which serve different requirements but none of them address the requirement of supporting multiple subnets within single broadcast domain. In this draft we define new service interface type to support multiple subnets in single broadcast domain. Service interface proposed in this draft will be applicable to multihoming case only.},
}