%% You should probably cite draft-ietf-bess-evpn-irb-mcast-11 instead of this revision.
@techreport{ietf-bess-evpn-irb-mcast-08,
    number =    {draft-ietf-bess-evpn-irb-mcast-08},
    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-irb-mcast/08/},
    author =    {Wen Lin and Zhaohui (Jeffrey) Zhang and John Drake and Eric C. Rosen and Jorge Rabadan and Ali Sajassi},
    title =     {{EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding}},
    pagetotal = 78,
    year =      2022,
    month =     nov,
    day =       28,
    abstract =  {Ethernet VPN (EVPN) provides a service that allows a single Local Area Network (LAN), comprising a single IP subnet, to be divided into multiple "segments". Each segment may be located at a different site, and the segments are interconnected by an IP or MPLS backbone. Intra-subnet traffic (either unicast or multicast) always appears to the end users to be bridged, even when it is actually carried over the IP or MPLS backbone. When a single "tenant" owns multiple such LANs, EVPN also allows IP unicast traffic to be routed between those LANs. This document specifies new procedures that allow inter-subnet IP multicast traffic to be routed among the LANs of a given tenant, while still making intra-subnet IP multicast traffic appear to be bridged. These procedures can provide optimal routing of the inter- subnet multicast traffic, and do not require any such traffic to egress a given router and then ingress that same router. These procedures also accommodate IP multicast traffic that originates or is destined external to the EVPN domain.},
}