%% You should probably cite draft-ietf-bess-evpn-ac-aware-bundling instead of this I-D. @techreport{sajassi-bess-evpn-ac-aware-bundling-05, number = {draft-sajassi-bess-evpn-ac-aware-bundling-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-sajassi-bess-evpn-ac-aware-bundling/05/}, author = {Ali Sajassi and Patrice Brissette and Mankamana Prasad Mishra and Samir Thoria and Jorge Rabadan and John Drake}, title = {{AC-Aware Bundling Service Interface in EVPN}}, pagetotal = 13, year = 2022, month = feb, day = 3, abstract = {EVPN provides an extensible and flexible multi-homing 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 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.}, }