%% You should probably cite draft-ietf-lisp-group-mapping instead of this I-D. @techreport{vdas-lisp-group-mapping-03, number = {draft-vdas-lisp-group-mapping-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-vdas-lisp-group-mapping/03/}, author = {Vengada Prasad Govindan and Dino Farinacci and Aswin Kuppusami and Stig Venaas}, title = {{LISP Multicast Overlay Group to Underlay RLOC Mappings}}, pagetotal = 10, year = 2024, month = may, day = 3, abstract = {This draft augments LISP {[}RFC9300{]} multicast functionality described in {[}I-D.farinacci-lisp-rfc6831bis{]} and {[}I-D.farinacci-lisp-rfc8378bis{]} to support the mapping of overlay group addresses to underlay RLOC addresses. This draft defines a many-to-1, 1-to-many, and many-to-many relationship between multicast EIDs and the Replication List Entries (RLEs) RLOC records they map to. The mechanisms in this draft allow a multicast LISP overlay to run over a mixed underlay of unicast and/or multicast packet forwarding functionality.}, }