%% You should probably cite draft-irtf-samrg-common-api instead of this I-D. @techreport{waehlisch-sam-common-api-06, number = {draft-waehlisch-sam-common-api-06}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-waehlisch-sam-common-api/06/}, author = {Matthias Wählisch and Thomas C. Schmidt and Stig Venaas}, title = {{A Common API for Transparent Hybrid Multicast}}, pagetotal = 32, year = 2011, month = mar, day = 7, abstract = {Group communication services exist in a large variety of flavors, and technical implementations at different protocol layers. Multicast data distribution is most efficiently performed on the lowest available layer, but a heterogeneous deployment status of multicast technologies throughout the Internet requires an adaptive service binding at runtime. Today, it is difficult to write an application that runs everywhere and at the same time makes use of the most efficient multicast service available in the network. Facing robustness requirements, developers are frequently forced to using a stable, upper layer protocol controlled by the application itself. This document describes a common multicast API that is suitable for transparent communication in underlay and overlay, and grants access to the different multicast flavors. It proposes an abstract naming by multicast URIs and discusses mapping mechanisms between different namespaces and distribution technologies. Additionally, it describes the application of this API for building gateways that interconnect current multicast domains throughout the Internet.}, }